spec-driven-development
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when drafting a PRD or requirements document with objectives and scope, or when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying. Use when evolving a shipped spec — scoping a V1, deferring ideas to a V2 backlog, or writing a follow-up spec for a change to an existing feature.
Listed from its GitHub repository. Reports from people who tried it will appear here.
- Source
- addyosmani/agent-skills
- GitHub stars
- 119,561
- License
- MIT
No reports yet
Nobody has written down how spec-driven-development works with their agent. Tried it? Say whether it worked, and with which agent and model.
Write the first report