Spec Workflow
For non-trivial work, CodeForge is designed around a spec-first workflow.
The Three Commands
Section titled “The Three Commands”| Command | Use It For |
|---|---|
/spec <feature> | Create, refine, and approve a spec package |
/build <feature> | Implement from an approved spec |
/specs | Check spec health across the project |
Recommended Flow
Section titled “Recommended Flow”- Start with
/spec <feature>. - Review the generated spec summary and decisions.
- Approve the spec.
- Run
/build <feature>. - Review the completion summary and any AI decisions.
Why This Exists
Section titled “Why This Exists”Specs separate the human review surface from the AI implementation detail.
- Humans review the short
index.mdsummary. - AI agents use the full spec package, including context and group files.
That keeps the review path short without starving implementation of detail.
What /spec Produces
Section titled “What /spec Produces”Specs live in .specs/ and typically include:
index.mdfor human reviewcontext.mdfor AI-facing implementation context- group files in
groups/for acceptance criteria and decomposition
What /build Does
Section titled “What /build Does”/build reads the Constitution and the approved spec, plans the work, implements it, verifies it, and closes the loop with a completion summary.
When to Use It
Section titled “When to Use It”Use the spec workflow when the change is:
- multi-file
- design-sensitive
- collaborative
- large enough that you want explicit acceptance criteria