菜单
Explicit command-style skill for inspecting .ai/sdd state and recommending the next safe action. Use only when the user explicitly asks for SDD status, progress, blockers, readiness, or next action. Do not auto-load for general SDD work; do not create specs or implement code.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | sdd-status |
| description | Explicit command-style skill for inspecting .ai/sdd state and recommending the next safe action. Use only when the user explicitly asks for SDD status, progress, blockers, readiness, or next action. Do not auto-load for general SDD work; do not create specs or implement code. |
Inspect the SDD workspace and report current progress, blockers, and next actions.
STATUS gives operational visibility across .ai/sdd/ without changing artifacts. It helps the user understand what exists, what is approved, what is still draft, what is blocked, and what the next safe SDD step should be. Treat it as an explicit utility command, not as a semantic auto-loaded skill for ordinary SDD authoring.
Load the SDD reference.
../_shared/references/sdd-practical.md.templates/sdd-index.md as the dashboard reference when useful..ai/steering/*.md files only if they help explain project context; do not summarize steering unless useful..ai/strategy/handoff/strategy-brief.md as optional upstream context and .ai/sdd/handoff/sdd-brief.md as optional downstream handoff output.Inspect the workspace.
.ai/sdd/ exists..ai/sdd/INDEX.md if present..ai/sdd/PLAN.md if present..ai/strategy/handoff/strategy-brief.md if present and report it as an available upstream handoff..ai/sdd/handoff/sdd-brief.md if present and report its readiness/status summary..ai/sdd/ideas/*.md if present..ai/sdd/specs/*/ directories..status when present.requirements.md, design.md, tasks.md, review.md, and decisions.md..status, and invalid .status values.Assess gates.
tasks.md exists..status conflicts with existing artifacts.Produce a concise dashboard.
.status value for each spec./skill:sdd-prd, /skill:sdd-spec, /skill:sdd-tasks, /skill:sdd-exec, or /skill:sdd-review.Do not modify files.
SDD STATUS
Workspace: .ai/sdd
Steering: .ai/steering present/missing
Upstream Handoffs:
- .ai/strategy/handoff/strategy-brief.md: present/missing
Plan:
- [missing/draft/approved] .ai/sdd/PLAN.md
Ideas:
- 001-name — idea:captured — .ai/sdd/ideas/001-name.md
Specs:
- 001-feature — requirements:approved
Artifacts: requirements.md yes, design.md no, tasks.md no, review.md no
Next: /skill:sdd-spec
Feature Workspace:
- Next feature ID: 002
- Numbering source: filesystem `.ai/sdd/specs/*/`
- Issues: none / [duplicate prefix, invalid status, non-canonical directory]
Handoff Output:
- .ai/sdd/handoff/sdd-brief.md: present/missing/readiness
Blocked / Attention:
- [Path] [problem]
Recommended next action:
- [Specific next step]
.status and artifact headers when available.INDEX.md./skill:sdd-plan or /skill:sdd-prd depending on scope.sdd-brief.md is missing or stale, recommend refreshing the SDD handoff.Explicit command-style skill for implementing approved SDD tasks from tasks.md with tight scope, tests, and verification evidence. Use only when the user explicitly asks to execute or implement a specific approved SDD task or feature. Do not auto-load for discussion, planning, review, or unapproved tasks.
Conversational SDD skill for exploring raw product or feature ideas before planning. Use when the user wants to brainstorm, clarify, compare directions, or convert an early idea into a plan or requirements, even without an explicit command. Do not use for implementation or technical task execution.
Explicit command-style skill for initializing or adopting SDD in a project by creating or preparing .ai/, .ai/steering/, and .ai/sdd/. Use only when the user explicitly asks to initialize, set up, adopt, or bootstrap SDD. Do not auto-load for general planning, feature specs, status checks, or implementation.
Cognitive SDD skill for creating or updating optional PLAN.md from captured ideas or project goals. Use when the conversation calls for roadmap, personas, feature mapping, phases, dependencies, and open decisions before requirements, even without an explicit command. Do not use for feature-level requirements or coding.
Core cognitive SDD skill for creating or updating requirements.md from an approved idea, plan, or feature request. Use when the conversation calls for defining WHAT and WHY: user stories, acceptance criteria, EARS functional requirements, NFRs, and boundaries, even without an explicit command. Do not use for technical design or coding.
Cognitive SDD skill for reviewing an implementation against requirements.md, design.md, and tasks.md, producing review.md with coverage, findings, verification evidence, and merge readiness. Use when the conversation calls for review after implementation or before completion, even without an explicit command. Do not use to implement fixes directly.