spec-driven-development
Creates a specification before coding when starting a project or significant change.
🛡️ AgentReady threat assessment
MAESTRO 7-layer threat model + OWASP AIVSS risk score for spec-driven-development, derived from its capabilities.
These scores are auto-generated from public information (the agent's own listing, docs, and repository) using the canonical OWASP AIVSS formula and the MAESTRO framework — an estimate for guidance, not a penetration test, audit, or certification. See the scoring methodology — every score is re-derived by the same automated method as an agent's public evidence changes.
Overview
An addyosmani skill that produces a spec before implementation when requirements are unclear or exist only as a vague idea. Instruction surface that gates coding behind an explicit specification the agent authors.
Key features and capabilities
- Spec-before-code gate
- Requirement clarification
- Handles vague ideas
Use cases
- Starting a new feature with unclear requirements
- Turning a vague idea into a spec