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.
78
83%
Does it follow best practices?
Impact
94%
1.70x2 of 3 eval scenarios. Add 1 more for a full score.
Passed
No findings from the security scan
No security issues found
Scanned
- Repository
addyosmani/agent-skills
- Revision
aeac41d
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.