メニュー
Use when starting or resuming Specky work, selecting lifecycle/workload/mode/capabilities, diagnosing config/state, or choosing an agent/tool.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
This skill should be used when the user asks to 'research codebase', 'scan tech stack', 'import documents', 'discovery questions', or needs guidance on Phase 1 research. Also trigger on 'sdd research', 'brownfield scan', 'import transcript', or 'check ecosystem'.
Use for Phase 2 (Specify): write SPECIFICATION.md with EARS, REQ-IDs, and acceptance criteria. Trigger on sdd_write_spec, sdd_turnkey_spec, sdd_validate_ears, or /specky-specify.
Use for Phase 4 (Design): produce DESIGN.md with architecture, API contracts, data model, and Mermaid diagrams. Trigger on sdd_write_design, sdd_generate_all_diagrams, or /specky-design.
Use for contracted implementation planning, executable TDD bindings, IaC, Docker, devcontainer, local environment, or Codespaces tools after an APPROVE analysis gate.
This skill should be used when the user asks to 'orchestrate pipeline', 'run full pipeline', 'coordinate phases', 'advance phase', or needs guidance on end-to-end pipeline execution. Also trigger on 'specky orchestrate', 'phase transition', 'LGTM gate', 'pipeline status', or 'which agent for this phase'.
Use for Phase 6 (Analyze): completeness audit, cross-analysis, compliance, and ANALYSIS.md gate decision. Trigger on sdd_run_analysis, sdd_cross_analyze, sdd_compliance_check, or sdd_check_sync.
| name | specky-onboarding |
| description | Use when starting or resuming Specky work, selecting lifecycle/workload/mode/capabilities, diagnosing config/state, or choosing an agent/tool. |
.specky/config.yml; an existing invalid/partial file blocks execution..specs/NNN-name/ directories..specs/.sdd-state.json, unsigned state, or older versions require specky migrate-contracts --dry-run before tools run.Collect independently:
The selected mode produces a persisted phase graph. Do not describe rapid/emergency as “skipping” a mandatory full graph; their contracted graphs are different by design.
Capabilities are opt-in and require matching parameter objects. Review the exact table in the specky-sdd-init skill. Ask for every provider, framework, resource, branch, threshold, format, platform, and environment value. capabilities: [] requires capability_config: {}.
sdd_scan_codebase with explicit depth/exclusions; preserve baseline, compatibility, insertion, and rollback evidence.document-import; explicitly allow formats.transcript-import; import may parse source, but auto/batch orchestration also requires explicit Constitution, source-backed requirements, complete architecture, tasks, and gates. Source quotes are validated before writes.figma and select extraction scope/diagram types.Do not create a branch in Init. When release capability is enabled and phase policy permits, use persisted branch prefix/base/draft/checkpoint parameters.
Before routing, repeat the full selection and obtain confirmation. Then initialize or resume the exact feature and report the contract ID, fingerprint, canonical state path, and next contracted phase.