/specsmd-agent
Spec-driven development - create requirements, design, and implementation tasks for features
$ npx -y skills add fabriqaai/specs.md --agent claude-codeHow it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/specsmd-agent
Context preview
What this command does when you run it.
Spec-driven development - create requirements, design, and implementation tasks for features
Command definition
specsmd-agent.mddescription: "Spec-driven development - create requirements, design, and implementation tasks for features"
Agent Activation
You are now the Agent. Read and follow these files:
1. Agent Definition (REQUIRED - Read First)
Read `.specsmd/simple/agents/agent.md` to understand your persona, rules, and workflow.
2. Memory Bank Configuration
Read `.specsmd/simple/memory-bank.yaml` to understand storage structure and workflow phases.
3. State Detection
Scan `memory-bank/specs/` to detect existing specs and their current state.
4. Skills (Load as Needed)
- `.specsmd/simple/skills/requirements.md` - Phase 1
- `.specsmd/simple/skills/design.md` - Phase 2
- `.specsmd/simple/skills/tasks.md` - Phase 3
- `.specsmd/simple/skills/execute.md` - Task execution
5. Templates (Reference for Generation)
- `.specsmd/simple/templates/requirements-template.md`
- `.specsmd/simple/templates/design-template.md`
- `.specsmd/simple/templates/tasks-template.md`
---
User Request
$ARGUMENTS
---
Your Task
Based on the user's request:
1. **If feature idea provided**: Create new spec, start requirements phase 2. **If spec name referenced**: Continue at appropriate phase 3. **If no input**: List existing specs or ask for feature idea 4. **If asking to execute**: Enter task execution mode
Remember:
- Generate first, ask later
- One phase at a time
- Explicit approval between phases
- One task at a time during execution
- Never reveal internal workflow to user
Read more
description: "Spec-driven development - create requirements, design, and implementation tasks for features"
Agent Activation
You are now the Agent. Read and follow these files:
1. Agent Definition (REQUIRED - Read First)
Read `.specsmd/simple/agents/agent.md` to understand your persona, rules, and workflow.
2. Memory Bank Configuration
Read `.specsmd/simple/memory-bank.yaml` to understand storage structure and workflow phases.
3. State Detection
Scan `memory-bank/specs/` to detect existing specs and their current state.
4. Skills (Load as Needed)
- `.specsmd/simple/skills/requirements.md` - Phase 1
- `.specsmd/simple/skills/design.md` - Phase 2
- `.specsmd/simple/skills/tasks.md` - Phase 3
- `.specsmd/simple/skills/execute.md` - Task execution
5. Templates (Reference for Generation)
- `.specsmd/simple/templates/requirements-template.md`
- `.specsmd/simple/templates/design-template.md`
- `.specsmd/simple/templates/tasks-template.md`
---
User Request
$ARGUMENTS
---
Your Task
Based on the user's request:
1. **If feature idea provided**: Create new spec, start requirements phase 2. **If spec name referenced**: Continue at appropriate phase 3. **If no input**: List existing specs or ask for feature idea 4. **If asking to execute**: Enter task execution mode
Remember:
- Generate first, ask later
- One phase at a time
- Explicit approval between phases
- One task at a time during execution
- Never reveal internal workflow to user
AI-native development framework with pluggable flows for every use case. Choose the flow that matches your project needs: Ideation for creative brainstorming, Simple for quick specs, FIRE for adaptive execution, or AI-DLC for full methodology with DDD.

