jmagly/contract-manifest
agentic/code/frameworks/sdlc-complete/skills/contract-manifest/SKILL.md
Generate a human-readable manifest for an AIWG skill chain — agent assignments, requires/ensures contracts, data flow, and parallelization opportunities.
$ install --global
skillsauthnpx skillsauth add jmagly/aiwg contract-manifestInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 8, 2026, 6:09 AM143.5s1 file scanned
SKILL.md
- 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.
- - "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
- - "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
- - "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
- argumentHint:
- <skill1> <skill2> ... | --workflow <file.yaml> [--mermaid] [--json]
- allowedTools:
- Read, Glob, Grep
- model:
- sonnet
- category:
- planning
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:
# workflow.yaml
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 needsensures:— outputs the skill commits to delivererrors:— failure conditionsinvariants:— always-true properties
If a skill has no contract fields, note it as "contract not yet defined."
Step 3: Build Wiring Table
For each skill's requires: entry, find the upstream source:
- Exact match: Another skill's
ensures:entry with the same name → direct wire ✓ - Semantic match: Another skill's
ensures:entry that means the same thing (e.g.,issues-filed↔issues) → semantic wire ⚠️ (flag as warning) - External input: The workflow's own
requires:(user provides it) → external → - No match: Nothing upstream provides it → unresolved ❌
Step 4: Determine Execution Order
- Skills with only external inputs can execute first
- Skills depending on upstream
ensures:must wait for that skill - Skills with no dependencies between them can execute in parallel
Step 5: Output Manifest
## Contract Manifest: {workflow name or skill list}
### Skills
| Skill | Requires | Ensures | Errors |
|-------|----------|---------|--------|
| issue-planner | objective, tracker | issues-filed, research-brief | no-tracker-access, research-failed |
| address-issues | issues, tracker | cycle-comments, aggregate-report | tracker-unavailable |
### Data Flow
| Source Skill | Output | → | Target Skill | Input | Match |
|-------------|--------|---|-------------|-------|-------|
| (external) | objective | → | issue-planner | objective | ✓ exact |
| issue-planner | issues-filed | → | address-issues | issues | ⚠️ semantic |
| issue-planner | tracker | → | address-issues | tracker | ✓ exact |
### Execution Order
1. issue-planner (requires: external inputs only)
2. address-issues (requires: issue-planner.issues-filed, issue-planner.tracker)
**Parallel groups**: [issue-planner] → [address-issues]
### Warnings
- `issue-planner.issues-filed` → `address-issues.issues`: semantic match only (names differ; verify intent)
### Issues
- None
Optional: Mermaid Diagram (--mermaid)
graph LR
Input[External Input] --> A[issue-planner]
A -->|issues-filed| B[address-issues]
A -->|tracker| B
B --> Output[Aggregate Report]
Output Formats
| Flag | Format | Use Case |
|------|--------|----------|
| (default) | Markdown | Human review |
| --json | JSON | Tooling, CI integration |
| --mermaid | Markdown + embedded Mermaid | Documentation |
Model
Runs on Sonnet — contract extraction and matching is structural analysis.
References
- @$AIWG_ROOT/agentic/code/frameworks/sdlc-complete/README.md — SDLC framework context and skill catalog
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/research-before-decision.md — Research-first approach for contract resolution
- @$AIWG_ROOT/agentic/code/addons/aiwg-utils/rules/diagram-generation.md — Mermaid diagram generation standards
- @$AIWG_ROOT/docs/extensions/overview.md — Extension system and skill architecture
- @$AIWG_ROOT/docs/cli-reference.md — CLI reference
Related Skills
jmagly/radar-status
data-ai
VerifiedTrustedCommunity
Report which research-corpus radar sidecars are overdue for refresh. Computes staleness (days since last refresh vs the cadence window) for every radar, sorted most-overdue-first. Runs via `aiwg corpus radar-status`.
140SKILL.mdUpdated May 28, 2026
jmagly/radar-report
data-ai
VerifiedTrustedCommunity
Aggregate research-corpus radar sidecars into a corpus or per-cluster freshness report — totals, overdue count, per-cluster / per-GRADE / per-trajectory breakdowns, an overdue table, and per-radar rationale snippets. Runs via `aiwg corpus radar-report`.
140SKILL.mdUpdated May 28, 2026
jmagly/radar-init
testing
VerifiedTrustedCommunity
Scaffold radar/freshness sidecars for research-corpus REFs. Pulls title/authors from the citation sidecar and GRADE from the analysis doc, defaults the refresh cadence from GRADE and the cluster from a corpus-local map, and stamps documentation/radar/REF-XXX-radar.md. Runs via `aiwg corpus radar-init`.
140SKILL.mdUpdated May 28, 2026
jmagly/profile-temporal
data-ai
VerifiedTrustedCommunity
Compute an entity's publication trajectory — per-year paper counts, topic drift, hot-streak detection (≥3 consecutive A-grade years), and career phase. Runs via `aiwg corpus profile-temporal`.
140SKILL.mdUpdated May 28, 2026