spec-driven-planning
Advanced tools
Spec-Driven Planning (SDP) CLI tool for Claude Code, GitHub Copilot, Windsurf, and Codex
A structured workflow system for transforming natural-language requirements into refined specifications, task decompositions, estimates, and GitHub Issues using Claude Code custom commands.
Use npx to initialize SDP in your project:
# Initialize for Claude Code (default)
npx spec-driven-planning init
# Initialize for GitHub Copilot
npx spec-driven-planning init --github-copilot
# Initialize for Windsurf
npx spec-driven-planning init --windsurf
# Initialize for Codex
npx spec-driven-planning init --codex
# Initialize with Japanese
npx spec-driven-planning init --lang ja
# Initialize for GitHub Copilot with Japanese
npx spec-driven-planning init --github-copilot --lang ja
This will create:
.claude/commands/sdp/ - Custom slash commands (Claude Code).github/prompts/ - Prompt files (GitHub Copilot).windsurf/workflows/ - Workflow files (Windsurf).codex/prompts/ - Prompt files (Codex).sdp/config/ - Configuration files (including language settings).sdp/templates/en/ - English document templates.sdp/templates/ja/ - Japanese document templates.sdp/specs/ - Requirements directory (created on demand).sdp/out/ - Output directory for exportsSet the output language in .sdp/config/language.yml:
# Supported languages: en (English), ja (Japanese)
language: en # or ja
All generated documents (requirement.md, design.md, plan.md, etc.) will be created in the specified language.
Update export settings in .sdp/config/export.yml:
destination: github # "github", "jira", "backlog", or "local"
github:
repo: your-org/your-repo
issue_mode: sub_issues # sub_issues, linked_issues, or single_issue
labels:
- sdp
- enhancement
jira:
url: https://your-domain.atlassian.net
project: PROJ
email: your-email@example.com
issue_mode: sub_tasks
backlog:
space_key: myspace
domain: backlog.com
project_key: PROJ
issue_mode: sub_tasks
local:
out_dir: out
Adjust estimation parameters in .sdp/config/estimate.yml:
default_buffers:
schedule: 0.15 # 15% buffer
pert:
clamp:
min_h: 1
max_h: 40
Generate project context documents:
/sdp:steering
This creates:
.sdp/product.md - Business goals and KPIs.sdp/tech.md - Technology stack and constraints.sdp/structure.md - Code organizationRefine a natural-language requirement:
/sdp:requirement "Add user authentication feature"
Creates .sdp/specs/add-user-authentication/requirement.md with:
Compare design options (lightweight, 200-400 lines):
/sdp:pre-design add-user-authentication
Creates .sdp/specs/add-user-authentication/pre-design.md with:
Benefits: Make direction decisions with lightweight comparisons instead of 1000+ line documents.
Elaborate the selected option to implementation-ready level (500-800 lines):
# To proceed with recommended option
/sdp:design add-user-authentication
# To select a different option (e.g., Option 2)
/sdp:design add-user-authentication 2
Creates .sdp/specs/add-user-authentication/design.md with:
Benefits: Detail only the selected approach, avoiding unnecessary design work.
About /sdp:design-legacy command: For backward compatibility, the /sdp:design-legacy command is still available (performs pre-design and detailed design in one step). However, the new two-stage flow (pre-design → design) is recommended for iterative design.
Create task decomposition with PERT estimates:
/sdp:estimate add-user-authentication
Creates .sdp/specs/add-user-authentication/tasks.yml with:
Generate human-readable project plan:
/sdp:show-plan add-user-authentication
Creates .sdp/specs/add-user-authentication/plan.md with:
Export tasks to your preferred issue tracker:
/sdp:export-issues add-user-authentication
SDP supports multiple export destinations (configured in .sdp/config/export.yml):
gh)
# Install GitHub CLI (macOS)
brew install gh
# Authenticate
gh auth login
# Optional: Install sub-issue extension for sub_issues mode
gh extension install yahsan2/gh-sub-issue
sub_issues or linked_issues mode)export JIRA_API_TOKEN=your-tokenexport BACKLOG_API_KEY=your-key.sdp/out/add-user-authentication-issues.md.sdp/out/add-user-authentication-import.sh (Bash script for macOS/Linux/Git Bash).sdp/out/add-user-authentication-import.ps1 (PowerShell script for Windows)Once plans and issues are finalized, you can optionally execute the implementation:
/sdp:implement add-user-authentication
tasks.yml are executed sequentially./sdp:implement add-user-authentication T-002 T-004).Creates or updates .sdp/specs/add-user-authentication/implementation.md while applying the required code changes and recording test evidence.
When exporting to issue trackers, SDP creates a hierarchical structure:
📌 Main Issue: [add-user-authentication] User Authentication Feature
├─ 🎫 Sub-Issue: [T-001] Setup authentication module
├─ 🎫 Sub-Issue: [T-002] Implement JWT token service
├─ 🎫 Sub-Issue: [T-003] Create login/logout endpoints
└─ 🎫 Sub-Issue: [T-004] Add authentication tests
SDP supports three issue organization modes:
Sub-Issues / Sub-Tasks Mode (sub_issues / sub_tasks)
Linked Issues Mode (linked_issues)
Single Issue Mode (single_issue)
Each sub-issue includes:
All commands are located in .claude/commands/sdp/:
| Command | Description |
|---|---|
/sdp:steering | Generate project context (product, tech, structure) |
/sdp:requirement <text-or-path> | Refine and normalize requirements |
/sdp:pre-design <slug> | Generate lightweight pre-design (2-4 design options) |
/sdp:design <slug> [option-num] | Generate detailed design from selected option |
/sdp:design-legacy <slug> | (Legacy) Generate pre-design and design in one step |
/sdp:estimate <slug> | Generate task breakdown with PERT estimates |
/sdp:show-plan <slug> | Create visual project plan with Gantt chart |
/sdp:export-issues <slug> | Export to GitHub Issues, Jira, Backlog, or local files |
/sdp:implement <slug> [task-id ...] | (Optional) Execute implementation tasks and capture logs |
All templates are in .sdp/templates/:
product.md - Product overview templatetech.md - Technical stack templatestructure.md - Code structure templaterequirement.md - Requirement specification templatedesign.md - Design document templateimplementation.md - Implementation log templatetasks.schema.yml - Task YAML schemaEach template includes detailed examples and guidance.
.claude/
└── commands/sdp/ # Custom slash commands (Claude Code)
.github/
└── prompts/ # Prompt files (GitHub Copilot)
.windsurf/
└── workflows/ # Workflow files (Windsurf)
.codex/
└── prompts/ # Prompt files (Codex)
.sdp/ # SDP working directory (gitignored)
├── config/ # Configuration files
│ ├── estimate.yml # Estimation parameters
│ └── export.yml # Export destination settings
├── templates/ # Document templates
├── product.md # Business context
├── tech.md # Technical context
├── structure.md # Code structure
├── specs/ # Requirements directory
│ └── <slug>/ # Requirement folder (e.g., add-user-authentication/)
│ ├── requirement.md # Requirement spec
│ ├── design.md # Design document
│ ├── tasks.yml # Task breakdown
│ ├── implementation.md # Implementation log and test evidence
│ └── plan.md # Project plan
└── out/ # Issue drafts and import scripts
SDP supports multiple languages for generated content:
.sdp/config/language.ymlTo change the output language after initialization, edit .sdp/config/language.yml:
language: ja # Change to 'en' for English or 'ja' for Japanese
All subsequent commands will generate content in the specified language.
SDP supports multiple AI coding assistants! Use the platform-specific flag during initialization.
npx spec-driven-planning init
Custom slash commands in .claude/commands/sdp/
npx spec-driven-planning init --github-copilot
Setup steps:
chat.promptFiles and enable itPrompt files in .github/prompts/
npx spec-driven-planning init --windsurf
Setup steps:
Workflow files in .windsurf/workflows/
npx spec-driven-planning init --codex
Setup steps:
Prompt files in .codex/prompts/
| Claude Code | GitHub Copilot / Windsurf / Codex | Description |
|---|---|---|
/sdp:steering | /sdp-steering | Generate project context |
/sdp:requirement | /sdp-requirement | Refine requirement specification |
/sdp:pre-design | /sdp-pre-design | Generate pre-design |
/sdp:design | /sdp-design | Generate detailed design |
/sdp:design-legacy | /sdp-design-legacy | (Legacy) Pre-design and design in one step |
/sdp:estimate | /sdp-estimate | Generate task breakdown |
/sdp:show-plan | /sdp-show-plan | Create visual project plan |
/sdp:implement | /sdp-implement | Execute implementation tasks |
/sdp:export-issues | /sdp-export-issues | Export to issue trackers |
In GitHub Copilot / Windsurf / Codex:
/ followed by the command name/sdp-requirement Add user authentication)All platforms generate the same structured outputs!
npx installation).claude/commands/sdp/ custom commands.github/prompts/ prompt files (requires VS Code with chat.promptFiles setting enabled).windsurf/workflows/ workflow files.codex/prompts/ prompt filesgh): For GitHub Issues export
JIRA_API_TOKENBACKLOG_API_KEYSDP works on all major platforms:
All commands use Claude Code's native file operations instead of platform-specific shell commands, ensuring consistent behavior across all platforms.
Apache-2.0
Contributions are welcome! Please feel free to submit issues or pull requests.
Made with ❤️ for Claude Code
FAQs
Spec-Driven Planning (SDP) CLI tool for Claude Code, GitHub Copilot, Windsurf, and Codex
The npm package spec-driven-planning receives a total of 2 weekly downloads. As such, spec-driven-planning popularity was classified as not popular.
We found that spec-driven-planning demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Open source is under attack because of how much value it creates. It has been the foundation of every major software innovation for the last three decades. This is not the time to walk away from it.
Security News
Socket CEO Feross Aboukhadijeh breaks down how North Korea hijacked Axios and what it means for the future of software supply chain security.
Security News
OpenSSF has issued a high-severity advisory warning open source developers of an active Slack-based campaign using impersonation to deliver malware.