| name | forgemyspec-implement |
| description | Implements work strictly from an existing ForgeMySpec bundle (spec.yaml, CLAUDE.md, acceptance checklist). Use when the spec is already written and the user wants coding execution without re-compiling the requirement. Combines well with MCP tools for reading tests, CI, and repo structure during implementation. |
Implement from ForgeMySpec bundle
Preconditions
spec.yaml exists and is the source of truth.- Supporting files present as generated by ForgeMySpec:
CLAUDE.md, acceptance-checklist.md, and optionally .claude/commands/implement-from-spec.md.
Steps
- Read
spec.yaml (objective, constraints, hypotheses, actions, success criteria, required evidence).
- Follow actions in a sensible order; honor
supports links to hypotheses.
- Satisfy
required_evidence with concrete artifacts (test runs, command output).
- Complete
acceptance-checklist.md honestly.
- Update
CLAUDE.md only with stable decisions and pitfalls—not scratch logs.
MCPs
Use MCPs to verify integrations, run tests, or fetch live data needed for evidence. Do not expand product scope beyond the spec unless the user explicitly revises spec.yaml.
Reference
See ../forgemyspec/references/implement-from-spec-workflow.md in this repository for the full handoff narrative.
