Spec-Driven Development Engine

When your request leaves edge cases unwritten, Mind Code has to guess.

You define the expected outcome in a spec. Mind Code keeps its requirements, design, and tasks in your repository so you can review them alongside the code.

Run mind spec new with a title. Mind Code creates three files under .mind/specs for you to complete:

• requirements.md describes what must hold, using structured requirement patterns and references such as REQ-001.
• design.md records the approach and failure recovery.
• tasks.md breaks the work into steps linked to those requirements.

Mind Code runs tasks in dependency order and assigns independent work to parallel agents in separate worktrees.

When you run mind spec verify, Mind Code checks requirement syntax, looks for requirement tags such as [REQ-###] or @req in test files, and checks task completion. It reports missing tags and incomplete tasks; it does not run the tests or prove that they pass.

Run mind spec validate to ask Mind Code to check requirement syntax and whether the design is complete enough for the current phase.

From your repository, create a spec with a title, then fill in its requirements, design, and tasks. Verify the active spec when the work is ready:

mind spec new "User authentication"
mind spec verify

To check another spec, use mind spec verify <id>.

You can add mind spec verify to your CI checks. The command returns a failure status when verification fails; your team configures whether that check blocks merging in your source-control platform.

When you open a pull request, include the spec files alongside the code.