| namespace | aiwg |
| platforms | ["all"] |
| name | contract-manifest |
| description | Generate a human-readable manifest for an AIWG skill chain — agent assignments, requires/ensures contracts, data flow, and parallelization opportunities. |
| requires | ["skills: ordered list of AIWG skill names or file paths to include in the manifest","if workflow-file: path to a YAML/JSON workflow definition listing the skill chain"] |
| ensures | ["manifest: human-readable manifest with per-skill contracts, wiring table, and execution order","data-flow: table showing which ensures: output from each skill satisfies which requires: input of the next","warnings: list of semantic-only matches (matched by meaning not exact name) and unresolved requires","if mermaid: Mermaid LR diagram of the skill chain"] |
| errors | ["skill-not-found: one or more skill names cannot be resolved to a SKILL.md file","no-contracts: none of the specified skills have requires:/ensures: fields — nothing to manifest"] |
| invariants | ["manifest generation never executes skills — static analysis only","semantic matches are flagged as warnings, never silently accepted as definite wires"] |
| commandHint | {"argumentHint":"<skill1> <skill2> ... | --workflow <file.yaml> [--mermaid] [--json]","allowedTools":"Read, Glob, Grep","model":"haiku","category":"planning","modelRole":"efficiency","modelTier":"economy"} |
Contract Manifest Skill
Generate a manifest showing how a chain of AIWG skills connects — mapping each skill's ensures: outputs to the next skill's requires: inputs.
Triggers
- "show the contract manifest for [skill1] → [skill2] → [skill3]"
- "how does [workflow] wire together?"
- "generate manifest for this skill chain"
- "show data flow for [issue-planner] → [address-issues]"
- "what does [skill] produce and what does [skill] need?"
Parameters
Skills list (positional)
Ordered list of skill names or paths:
/contract-manifest issue-planner address-issues
/contract-manifest prose-detect prose-run forme-manifest
--workflow <file> (optional)
Path to a YAML workflow definition:
name: Issue Planning Pipeline
steps:
- skill: issue-planner
- skill: address-issues
- skill: issue-sync
--mermaid (optional)
Include a Mermaid LR diagram of the skill chain.
--json (optional)
Output the manifest as machine-readable JSON instead of Markdown.
Behavior
Step 1: Resolve Skills
For each skill name, find the canonical SKILL.md:
- Check
agentic/code/frameworks/sdlc-complete/skills/{name}/SKILL.md
- Check
agentic/code/addons/*/skills/{name}/SKILL.md
- Check
.claude/skills/{name}/SKILL.md
- If path given directly: read that file
Step 2: Extract Contracts
From each skill's YAML frontmatter, extract:
requires: — inputs the skill needs
ensures: — outputs the skill commits to deliver