メニュー
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.
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 contracted implementation planning, executable TDD bindings, IaC, Docker, devcontainer, local environment, or Codespaces tools after an APPROVE analysis gate.
Use when starting or resuming Specky work, selecting lifecycle/workload/mode/capabilities, diagnosing config/state, or choosing an agent/tool.
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-design-architect |
| description | 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. |
Read the signed feature contract, Constitution, and Specification. The selected workload controls workload_design and required_diagrams.
sdd_write_design requires all of the following; no section is inferred:
architecture_overview, system_context, container_architecturecomponent_design, code_level_designdata_models, infrastructure, security_architectureerror_handling, cross_cuttingmermaid_diagrams entry and one ADRworkload_design whose type exactly matches persisted workloadapi_contracts: required and non-empty for API; explicit empty array for non-API workloads with no network APIspec_dir, feature_number, and force| Workload | Required fields |
|---|---|
| API | versioning strategy, error model, authentication, rate limits |
| Web application | user journeys, UI states, accessibility, responsive behavior, API integration |
| Service | protocols, dependencies, failure modes, operability, observability |
| CLI | command grammar, arguments, exit codes, standard streams, shell compatibility |
| Library | public API, compatibility, versioning, error surface, consumer examples |
| Infrastructure | topology, provider, state management, identity, network security |
Every design must contain real REQ-ID references. Missing Specification IDs or incomplete architecture evidence blocks writing.
Use required_diagrams from signed state. For each required type, provide Mermaid code and source evidence_refs. sdd_generate_all_diagrams requires the exact set: no missing, extra, or duplicate types. Sources are contract-defined; the tool does not infer nodes from headings.
Present DESIGN.md, ADR decisions, API contracts when applicable, and every grounded diagram. Do not present placeholders, skeletons, or generic C4 content.