skills/sdd-init/SKILL.md
# Skill: sdd-init ## Invocation ``` /sdd-init <slug> [notion-url] [--mode standard|auto] ``` **Arguments:** - `<slug>` — kebab-case identifier for the feature (e.g. `user-invitation`, `supplier-csv-import`) - `[notion-url]` — optional Notion page URL to fetch and archive as source material - `[--mode standard|auto]` — workflow mode (default: `standard`) - `standard`: engineer-led — AI assists, human drives decisions - `auto`: AI-led — suitable for non-engineers; AI asks questions and mak
npx skillsauth add sc30gsw/claude-code-customes skills/sdd-initInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
/sdd-init <slug> [notion-url] [--mode standard|auto]
Arguments:
<slug> — kebab-case identifier for the feature (e.g. user-invitation, supplier-csv-import)[notion-url] — optional Notion page URL to fetch and archive as source material[--mode standard|auto] — workflow mode (default: standard)
standard: engineer-led — AI assists, human drives decisionsauto: AI-led — suitable for non-engineers; AI asks questions and makes decisions autonomouslyInitialize a spec directory for a new feature under .claude/specs/<slug>/. This is always the first step in the SDD workflow. It creates the directory structure, optionally fetches a Notion page as source material, and records the chosen mode in progress.md.
<slug> is kebab-case (lowercase letters, digits, hyphens only).--mode is not provided, default to standard.<slug> in --mode <mode>."Create the following empty directories and files under .claude/specs/<slug>/:
.claude/specs/<slug>/
├── review-results/ ← subdirectory for review output files
├── progress.md ← created in this step
├── change-log.md ← created in this step
├── requirements.md ← placeholder (created by sdd-requirements)
├── design.md ← placeholder (created by sdd-design)
└── tasks.md ← placeholder (created by sdd-tasks)
Run:
mkdir -p .claude/specs/<slug>/review-results/
Write placeholder files with a single comment line:
<!-- Artifact not yet generated. Run the corresponding sdd-* skill. -->
If a Notion URL is given:
mcp__claude_ai_Notion__notion-fetch with the page ID..claude/specs/<slug>/source-notion.md.If no Notion URL is given, skip this step.
Write .claude/specs/<slug>/progress.md with the following structure:
# Spec Progress: <slug>
**Mode**: <standard|auto>
**Initialized**: <YYYY-MM-DD>
**Notion source**: <notion-url or "none">
## Phase Status
| Phase | Skill | Status |
| ----- | ----------------------- | -------------- |
| 1 | sdd-requirements | ⬜ not started |
| 2 | sdd-review-requirements | ⬜ not started |
| 3 | sdd-design | ⬜ not started |
| 4 | sdd-tasks | ⬜ not started |
| 5 | sdd-review-plan | ⬜ not started |
| 6 | sdd-impl | ⬜ not started |
| 7 | sdd-review | ⬜ not started |
| 8 | sdd-pr | ⬜ not started |
## Files
| File | Description |
| -------------------------------------------- | ----------------------------------------------------- |
| `requirements.md` | EARS-format requirements |
| `design.md` | Architecture and design decisions |
| `tasks.md` | Task breakdown (TASK-xxx) |
| `review-results/requirement-review.md` | Requirements Review findings |
| `review-results/plan-review.md` | Plan Review + Traceability findings |
| `review-results/code-review.md` | Code Review + Security Review findings |
| `change-log.md` | Phase completion event log |
Write .claude/specs/<slug>/change-log.md with the following structure:
# Change Log: <slug>
| Date | Skill | Event |
|------|-------|-------|
| <YYYY-MM-DD> | sdd-init | スペック初期化 |
Print a summary of what was created, including:
change-log.md initialized with first row| Aspect | --mode standard | --mode auto |
| ------------ | -------------------------- | -------------------------- |
| Who drives | Engineer | AI |
| AI role | Assist + review | Ask + decide |
| Notion fetch | Optional | Optional |
| Next skill | /sdd-requirements <slug> | /sdd-requirements <slug> |
progress.md file is the single source of truth for the mode. Subsequent skills MUST read mode from progress.md rather than accepting a --mode flag themselves..claude/specs/<slug>/ already exists, warn the user and ask whether to overwrite or abort. Do NOT silently overwrite.slug is used as-is in all file paths. Choose descriptive, stable slugs.== PHASE COMPLETE: sdd-init == Artifact: .claude/specs/<slug>/progress.md Summary:
⏸ WAITING FOR CONFIRMATION
Type CONFIRM sdd-requirements to proceed. Or describe changes needed.
tools
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
testing
# sdd-workflow — Workflow Status Dashboard ## Slash Command ``` /sdd-workflow [slug] ``` ## Purpose Read-only meta skill. Displays the current state of the SDD workflow — which phases are complete, which is next, and any blockers. Does NOT modify any files. --- ## This Skill is Read-Only `sdd-workflow` never writes to or modifies any file. It only reads spec files and git history to report status. There is no approval gate for this skill. --- ## Usage: Specific Feature ``` /sdd-workflo
content-media
# sdd-tasks **Slash command**: `/sdd-tasks <slug>` **Purpose**: Generate `tasks.md` (TASK-001..N) and `progress.md` from `requirements.md` and `design.md`. --- ## Prerequisites - `.claude/specs/<slug>/requirements.md` must exist - `.claude/specs/<slug>/design.md` must exist (run `/sdd-design` first) --- ## Steps ### 1. Read spec inputs ``` .claude/specs/<slug>/requirements.md .claude/specs/<slug>/design.md ``` Extract: - Every REQ-XXX ID with its acceptance criteria - Every design sect
development
# sdd-review — Post-Implementation Code Review ## Slash Command ``` /sdd-review <slug> ``` ## Purpose Run code review and security review on all changes introduced by the feature branch. Append structured findings to `review.md`. Does NOT auto-apply fixes — only proposes them. --- ## Prerequisites - `sdd-impl` has completed: all tasks in `progress.md` are `done` (or at least one is `done`; partial reviews are allowed). - The feature branch must have at least one commit ahead of `main`. -