spec-driven-development
#10 in Software Architecture & DesignCreates specs before coding.
Overview
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.From the project's GitHub description
Our editorial assessment of spec-driven-development is still in review. Facts below come from the repository and our catalogue.
Technical specifications
Each attribute is labelled with where it came from.
Install
A skill is a set of instructions your agent loads. Install it into the agent you use; there is nothing to host.
$ npx skills add https://github.com/addyosmani/agent-skills --skill spec-driven-development- Listing
- skills.shInstall counts come from skills.sh.
Alternatives
Also in Software Architecture & Design
Same category, not necessarily equivalent.
setup-ts-deep-modules
Wire dependency-cruiser into a TypeScript repo so each package is a deep module, with implementation hidden in subfolders and reachable only through its entry-point files.
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
Reviews
Community ratings are kept separate from Beav Scout rankings.
No reviews yet. Community reviews and comments are opening soon; you'll be able to rate spec-driven-development once signed in.