Skip to main content
A spec connects the project’s goals to a proposed implementation. It supplies context for planning, coding, and review; it should be checked against the actual requirements and current codebase. A useful reading order is goal → architecture → milestone → story → acceptance criteria. Deep specifications can add implementation subtasks to a story.

​
Read the artifacts

Human-oriented output can include roles, personas, and effort estimates. Coding-agent output emphasizes implementation and omits human staffing detail. The API exposes Markdown, structured JSON, and available graphs; see inputs and outputs for exact fields.

​
Refine before building

Ask the agent to resolve missing requirements, adjust constraints, or refine acceptance criteria. Use the available plan and story editing controls for the project. Confirm the updated artifact before launching work that depends on it. Changing a plan does not retroactively update shipped code. Request the corresponding implementation change, and check that an active task is using the intended requirements.

​
Example acceptance criteria

Track planned work in the roadmap and inspect implementation evidence in verification.