Spec-first feature work: requirements, design, then tasks
The agent writes requirements and a design doc for review, then breaks them into tasks it implements one by one.
The use case
Prompting an agent straight into code works for small fixes but drifts on larger features. Kiro and GitHub's open-source Spec Kit push a spec-first flow: the agent drafts requirements, then a technical design, then a task list, and only then writes code task by task. Each document is a checkpoint a developer can edit. This makes it clearer what the agent is about to build and gives reviewers something to compare the code against. The developer still approves the requirements and design before coding starts, and reviews each task's diff.
Example workflow
- Describe the feature in a short prompt
- Review and edit the generated requirements
- Review and edit the technical design
- Approve the task list
- Agent implements tasks one by one for review
Tools
- Kiro
- Spec Kit
Risks and guardrails
- Specs can look complete while missing edge cases
- Long specs slow small changes; use for features, not fixes
- Keep specs updated or they mislead later work
Sources
Written by Agents Lookup. Credits and official pages for the tools this use case names:
- Kiro docs: specs: kiro.dev/docs/specs
- GitHub on GitHub: Spec Kit: github.com/github/spec-kit
- Kiro (official page): kiro.dev (checked 2026-11-19)