Spec-driven development
Use Assumer's spec-driven workflow to go from principles and a written spec to a plan, a task list and an implementation you can verify step by step.
For larger features, writing the spec first gives the agent, and your team, a clear target. Assumer has a built-in spec-driven development workflow with one step per phase.
The phases
- Constitution: record the project principles every feature must respect, such as testing rules and architectural limits.
- Specify: describe what to build and why, in plain language.
- Clarify: answer the open questions the agent raises about the spec.
- Plan: turn the spec into a technical plan: files, data, interfaces.
- Tasks: break the plan into small, ordered tasks.
- Analyze: check that spec, plan and tasks are consistent.
- Implement: let the build agent work through the tasks.
- Converge: compare the result with the spec and close the gaps.
The documents live in your project under .assumer/, so they are reviewed and versioned like code.
When to use it
- Features that touch many files or several teams.
- Work you want reviewed before any code is written.
- Long tasks where you want the agent to keep a written source of truth.
For quick fixes, the plain plan → build flow is faster. See Agents.