メニュー
Initialize a new SDD spec directory with templates. Creates specs/KNOW-{NNN}-{description}/ with requirements.md, design.md, and tasks.md populated from templates. Auto-assigns the next available ticket number.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | sdd-init |
| description | Initialize a new SDD spec directory with templates. Creates specs/KNOW-{NNN}-{description}/ with requirements.md, design.md, and tasks.md populated from templates. Auto-assigns the next available ticket number. |
Create a new spec directory for a feature, following the SDD naming convention and populating it with template files. This is the entry point to the SDD workflow.
/sdd-spec to refine it)Read specs/README.md to get the next available KNOW number from the "Next Available Number" section
Ask the user (if not provided as argument):
Create the spec directory:
specs/KNOW-{NNN}-{kebab-case-title}/
Copy and populate templates from specs/_templates/:
requirements.template.md → requirements.md (replace {TITLE} and {NNN})design.template.md → design.md (replace {TITLE} and {NNN})tasks.template.md → tasks.md (replace {TITLE} and {NNN})Update specs/README.md:
draftReport to the user:
/sdd-spec KNOW-{NNN} to write the spec content$ARGUMENTS (optional): Feature title. If not provided, ask the user.User: /sdd-init push-based capture
Result:
Created: specs/KNOW-001-push-based-capture/
├── requirements.md (template)
├── design.md (template)
└── tasks.md (template)
Updated: specs/README.md (index + next number)
Next step: /sdd-spec KNOW-001
specs/README.md — Naming conventions, next available numberspecs/_templates/ — Template files to copydocs/workflows/sdd-overview.md — Full SDD workflow contextCreate Conventional Commits with type prefix, breaking change detection, dry-run preview, and strict rules against ticket IDs in messages. **AUTOMATICALLY USE** when: (1) Creating git commits ("commit", "git commit") (2) Suggesting commit messages ("commit message") (3) Splitting commits ("split commits") (4) Fixing commit messages ("fix commit") (5) Any git commit related request
Orchestrate the full release process: push to develop, generate release summary, propose version bump, update package.json files, generate CHANGELOG, create release PR, and monitor CI. Supports dry-run preview mode. **AUTOMATICALLY USE** when: (1) Releasing a new version ("release", "cut a release", "prepare release") (2) Bumping version ("version bump", "bump version") (3) Creating release PRs ("release PR") (4) Generating changelogs ("changelog", "release notes") (5) Any release-related request
Record knowledge to the local knowledge base after solving problems, making design decisions, or discovering reusable patterns. Invoke whenever you have just fixed a bug, made an architectural choice, found a reusable pattern, learned something from external sources, or completed a refactoring. Capturing while context is fresh prevents knowledge loss across sessions.
Search the local knowledge base for past solutions, design decisions, and patterns before starting work. Invoke when facing an error or exception, when approaching an unfamiliar area of the codebase, or when considering implementation approaches. Prevents re-solving already-solved problems and surfaces relevant context proactively.
Get contextual knowledge suggestions based on the current work context — the file being edited, the task being performed, or the error being investigated. Invoke at the start of a work session, when opening a new file, or when beginning a feature. Surfaces relevant past knowledge proactively without requiring a specific query.
Analyze existing codebase to inform spec design. Scans specified packages or directories to extract architecture patterns, public APIs, dependency relationships, and test coverage. Output feeds directly into design.md.