Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
From agent-skills
Starts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.
How this command is triggered — by the user, by Claude, or both
Slash command
/agent-skills:speccommands/The summary Claude sees in its command listing — used to decide when to auto-load this command
Invoke the agent-skills:spec-driven-development skill. Begin by understanding what the user wants to build. Ask clarifying questions about: 1. The objective and target users 2. Core features and acceptance criteria 3. Tech stack preferences and constraints 4. Known boundaries (what to always do, ask first about, and never do) Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries. Save the spec as SPEC.md in the project root and confirm with the user before proceeding.
Invoke the agent-skills:spec-driven-development skill.
Begin by understanding what the user wants to build. Ask clarifying questions about:
Then generate a structured spec covering all six core areas: objective, commands, project structure, code style, testing strategy, and boundaries.
Save the spec as SPEC.md in the project root and confirm with the user before proceeding.
16plugins reuse this command
First indexed Mar 22, 2026
Showing the 6 earliest of 16 plugins
npx claudepluginhub sky2464/agent-skills/specStarts spec-driven development: asks clarifying questions on objectives, features, tech stack, and boundaries; generates structured SPEC.md covering six core areas; confirms before proceeding.
/specGenerates feature specs via step-by-step dialogue: requirements.md (EARS notation), design.md (diagrams/TS interfaces), tasks.md (tasks/best practices).
/forge-specCreates a detailed specification for a development GOAL through guided clarification questions after gathering project rules, codebase structure, and related code. Supports --no-clarify to skip questions.
/specGenerates spec-driven development docs from a feature description: requirements.md (EARS user stories), design.md (Mermaid diagrams, TypeScript interfaces), tasks.md (implementation plan).
/specGenerates spec docs from feature description: requirements.md (EARS notation), design.md (Mermaid diagrams, TS interfaces), tasks.md (implementation plan).
/specGenerates structured specs from minimal feature description using Kiro method: requirements.md (EARS notation), design.md (Mermaid diagrams, TS interfaces), tasks.md (impl plan).