How do I install the Spec Driven skill?

Run npx skillmds@latest add tuyv/spec-driven in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Spec Driven safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec Driven?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Spec Driven free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Spec Driven?

tuyv (@tuyv) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec Driven by tuyv — Agent Skill

Name: Spec Driven
Author: tuyv

Spec Driven

Drive a spec-driven workflow for a larger feature: specify requirements and acceptance criteria, research decisions, plan numbered slices, implement, then verify. Use for multi-step features that need a reviewable paper trail. Skip it for small, obvious changes.

tuyv 4f219bd 4 files · 6.7 KB Updated Sep 17, 2026

File contents

Spec-driven development

A structured workflow for features big enough to warrant a paper trail. Each feature gets its own folder plans/<feature>/. Blank templates live in plans/templates/, and the /spec, /plan, and /verify commands copy them in. For small, obvious changes, use the lightweight plan output style instead (a single inline plan, no files).

Phases

Specify (plans/<feature>/spec.md): capture requirements (FR-N) and acceptance criteria (AC-N). Describe behavior and outcomes, not code. Run /spec <feature>.
Research (plans/<feature>/research.md): record decisions with their reasoning, open questions, and operating constraints.
Plan (plans/<feature>/plan.md): the architecture and a breakdown into numbered slices, each demonstrable on its own. Run /plan <feature>. Scaffold each slice from plans/templates/slice.md into plans/<feature>/NNN-<slug>.md.
Execute (plans/<feature>/NNN-<slug>.md): implement one slice at a time, ticking each slice's Done criteria as its verification passes, and keep each slice runnable. Run /implement <feature>.
Verify (plans/<feature>/verification.md): walk end-to-end scenarios, each mapped back to an AC-N. Run /verify <feature>.

Rules

Write the spec before the plan, and the plan before code.
Every acceptance criterion (AC-N) must have a matching verification scenario.
Keep slices small and independently demonstrable, one concern each.
See plans/README.md for the file roles and the per-feature layout.

Frequently asked questions