spec-driven
Spec-driven feature work with traceable requirements, design, tasks, and user acceptance testing (UAT). Use when planning, designing, implementing, or validating a feature from a story, feature PRD, or feature RFC. Not for unknown-bug diagnosis, standalone product or technical documents, PR or commit mechanics, or backlog tracking.
How do I install this agent skill?
npx skills add https://github.com/adeonir/agent-skills --skill spec-drivenIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill provides a structured development workflow using local scripts and markdown artifacts. It includes explicit security instructions to handle untrusted content safely, preventing indirect prompt injection.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
6/27 files flagged
- ZeroLeakspass
Score: 93/100 · 2 sections analyzed
What does this agent skill do?
Spec-Driven Development
Feature development in phases. Light by default; weight only where the change pays for it.
Triggers
- Specify ("plan feature", "spec this", "from PRD", "modify feature", "discuss how to build") → specify.md
- Design ("design this feature", "technical design", "plan the build") → design.md
- Tasks ("create tasks", "break into tasks", "task breakdown") → tasks.md
- Implement ("implement task T-1", "implement T-1 to T-4", "implement slice S-1", "execute tasks", "implement everything") → implement.md
- Validate / UAT ("run UAT", "manual testing", "validate flows") → validate.md
- Archive ("archive feature", "archive this spec") → archive.md
Workflow
specify → design → tasks → implement → [validate] → [archive]
└────────┴────────┴──────────┴──────────┴ a mechanical change skips all of this: one-liner → branch → implement inline
Specify's triage decides the path: a mechanical change with zero load-bearing decisions becomes a one-liner straight to inline implement on its own branch, and a prompt carrying outcomes that ship separately becomes one feature per outcome. Everything else produces the artifacts and runs the phases in turn. Verify is mental, per task, inside implement — never a user phase. Validate is optional UAT on the running application. Archive is manual housekeeping for a feature in any state, never automatic or suggested.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/adeonir/agent-skills/spec-driven">View spec-driven on skillZs</a>