Menu
SDDワークフロー全体のガイド。SDD コマンドを実行する時に、全てのコマンドで読み込む必要がある。
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | workflow |
| disable-model-invocation | true |
| description | SDDワークフロー全体のガイド。SDD コマンドを実行する時に、全てのコマンドで読み込む必要がある。 |
| hooks | {"Stop":[{"matcher":".*","hooks":[{"type":"prompt","prompt":"セッション終了前に `sdd:quality-check` スキルを実行して品質チェックを行ってください。\n","once":true}]}]} |
SDDは 仕様書に基づいて段階的に実装を進める 開発手法。 各スキルを実行する際は、常に 内部品質チェック の基準に従うこと。
1. 初回のみ: sdd:steering スキルでプロジェクト方針定義
2. タスク作成: sdd:spec init <説明>
3. 各スキル完了時に次のアクションが案内される
全Stepの一覧・依存関係・図解: See workflow-diagram.md
詳細: See directory-structure.md
sdd:spec init ユーザー認証機能を追加
# → 完了時に次のアクションが案内される
# → sdd:research conduct で技術調査（調査項目がある場合）
# → sdd:spec requirements で要件定義
sdd:status # 現在の進捗を確認
sdd:next # 次に何をすべきか確認
# sdd-webappで全タスクの進捗を可視化
# MCPツール: sdd_webapp_get_status
sdd:sync # 実装状況をドキュメントに反映
sdd:autopilot # 自動進行モードで実行
sdd:help # SDDの使い方を確認
Auto-activate CCS CLI delegation for deterministic tasks. Parses user input, auto-selects optimal profile (glm/kimi/custom) from ~/.ccs/config.json, enhances prompts with context, executes via `ccs {profile} -p "task"` or `ccs {profile}:continue`, and reports results. Triggers on "use ccs [task]" patterns, typo/test/refactor keywords. Excludes complex architecture, security-critical code, performance optimization, breaking changes.
Internal project-context placement and consistency reference used by context refactoring and verification workflows.
This skill should be used when the user asks to "audit project standards", "check standards compliance", "devkit audit", "find standards violations", "are we following devkit standards", "what's not following standards", "compliance report", "規約チェック", "スタンダード監査", or "規約違反を探して". It actively scans code and reports violations. Do NOT use for project scaffolding (use init-project), single-CLI-tool checks (use cli-compliance), or looking up what the standards are (use standards).
This skill should be used when the user asks to "set up a project", "choose a tech stack", "establish coding standards", "configure linting", "set up tests", "pick a framework", "review code quality", "set up logging", "configure observability", "choose an ORM", "set up auth", "set up Storybook", "write stories", "visual testing", "CSF", "coverage threshold", or discusses any technology choices for a TypeScript project. Also use when starting a new project, setting up CI/CD, choosing between tools (oxlint vs ESLint, pnpm vs npm), configuring environment variables, or when any other devkit skill needs to reference project conventions. This is the central reference for all devkit technology decisions and coding principles.
Review whether the current code satisfies a GitHub issue, then update the issue status to match. Use when the user asks to 'review an issue', 'check if an issue is done', 'is this issue resolved', 'update issue status', 'issueの対応状況を確認', 'issueが完了しているかレビュー', or 'issueのステータスを更新'.
This skill should be used when the user asks to 'create a skill', 'add a new skill', 'make a skill', 'scaffold a skill', 'new skill', 'スキル化して', 'スキルを作成', 'スキルを追加', or wants to create a new Claude Code skill for a plugin or project. Provides a guided workflow with automated scaffolding, validation, and dynamic context injection.