By kotaroyamame
Formal methods toolkit for multi-agent development: define agent contracts in VDM-SL, generate Phase 2 design documents (PROTOCOL.md, API-SIGNATURES.md), verify specifications, auto-prove with Z3, generate code scaffolds with runtime contract checks, auto-generate contract tests from specs and design documents, run end-to-end integrated workflows, reverse-engineer specifications from existing code, import natural language specs to VDM-SL, and export human-readable specification documents. Includes evaluation framework with comparative benchmarks.
Based on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
形式的エージェント契約を定義し、VDM-SL仕様と設計文書(プロトコル仕様)を生成するスキル
Generate a human-readable natural language specification document (Markdown) from a VDM-SL formal specification. Translates types, invariants, pre/post-conditions, and operations into clear prose that domain experts, project managers, and non-technical stakeholders can understand and review — without needing to learn VDM-SL. Use this skill whenever the user wants to: generate documentation from a VDM-SL spec, create a readable specification, export a spec for human review, convert VDM-SL to natural language, create a requirements document from formal specs, or produce a specification that non-engineers can read. Japanese triggers: 「VDM仕様から自然言語仕様を作りたい」「人間が読める仕様書を生成して」 「VDM-SLをドキュメントにして」「仕様書をエクスポートして」「形式仕様を読みやすくして」 「非エンジニア向けの仕様書を作って」「仕様のドキュメントを生成して」
Extract a provisional VDM-SL specification from existing source code. This is NOT the true spec — it is a scaffold for dialogue to uncover the user's real intent. Triggered by: "extract spec from code", "reverse engineer the specification", "extract-spec", "code to spec", "formalize the existing code". Japanese: 「既存のコードから仕様を抽出して」「コードの仕様を形式化して」 「コードベースを分析して」「コードをリバースエンジニアリングして」
Provide reference knowledge on VDM-SL and formal methods. Triggered by "VDM-SL syntax", "how to write types", "what is a pre-condition", "what is an invariant", "meaning of proof obligations", "what are formal methods", or "formal specification". Also responds to Japanese: 「VDM-SLの文法」「事前条件とは」「形式手法とは」等。 Referenced as background knowledge by other skills (define-contract, verify-spec).
Generate TypeScript/Python code scaffolds from VDM-SL specifications. Triggered by "generate code from the spec", "convert to TypeScript", "generate Python code", "create a scaffold", "generate implementation template", "create type definitions from VDM", or "generate agent code". Also responds to Japanese: 「仕様からコードを生成して」「TypeScriptに変換して」等。 Generates runtime verification code for pre-conditions, post-conditions, and invariants.
マルチエージェント開発における形式手法ツールキット。エージェント間の契約をVDM-SLで定義し、自動検証する。
Phase 2 設計文書の生成支援
契約テストの自動生成(新スキル: generate-tests)
設計文書の完全性チェック(verify-spec拡張)
形式手法の知識がない開発者でも、Claudeの支援により:
自然言語でエージェントの役割・入出力を説明すると、VDM-SLの形式仕様に変換する。v0.2.0: Phase 2設計文書(PROTOCOL.md、API-SIGNATURES.md)の生成もガイドする。
VDMJによる構文チェック・型チェック・PO生成。v0.2.0: 設計文書の完全性チェック、VDM-SL仕様との一貫性確認を追加。
VDM-SL仕様と設計文書の両方から実行可能な契約テスト(Jest/Vitest)を自動生成。
VDM-SLの文法、型システム、PO種別の背景知識を提供。
IID Systems (https://iid.systems)
MIT
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimnpx claudepluginhub kotaroyamame/formal-agent-contracts --plugin formal-agent-contractsPlan-first contract engineering for Claude Code and Codex.
Verifiable AI-Augmented Engineering framework with traceable requirements, independent verification, and compliance-ready artifacts
A single-skill package for generating harness blueprints for agentic systems.
AI/ML specialist agents — architects, prompt engineers, RAG designers
Verified Coherence Spec-Driven Development — adversarial quality gates for AI-assisted development
Formal methods and specification languages: UML/SysML modeling, TLA+ specifications, OpenAPI/AsyncAPI contract-first design, state machines, and Use Case 2.0 methodology.