sdd-status

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

sdd-status

sdd-status

Shows the status of all active SDD changes and orchestrator configuration.
Triggers:
/sdd-status
, SDD status, active changes, show open changes, what changes are in progress, orchestrator status

展示所有活跃SDD变更的状态以及Orchestrator配置。
触发方式:
/sdd-status
、SDD status、active changes、show open changes、what changes are in progress、Orchestrator status

Process

流程

Step 0 — Detect persistence mode

步骤0 — 检测持久化模式

Follow
skills/_shared/persistence-contract.md
Mode Detection for Standalone Skills:
  1. Check Engram MCP reachability → if reachable:
    engram
    , else
    none
遵循
skills/_shared/persistence-contract.md
中的独立技能的模式检测
  1. 检查Engram MCP的可达性 → 若可达则使用
    engram
    模式,否则使用
    none
    模式

Step 1 — Locate active changes

步骤1 — 定位活跃变更

engram mode: Search engram for active SDD state artifacts:
mem_search(query: "sdd/", project: "{project}") → list all SDD-related observations
Filter for artifacts that do NOT have an
archive-report
topic_key (those are completed).
none mode: Report "No persistence configured — cannot show change status."
Stop here if no changes found.

engram模式: 在engram中搜索活跃的SDD状态工件:
mem_search(query: "sdd/", project: "{project}") → list all SDD-related observations
筛选出不包含
archive-report
topic_key的工件(包含该key的工件已完成)。
none模式: 提示“未配置持久化 — 无法展示变更状态。”
如果未找到任何变更,流程到此结束。

Step 2 — Classify and group changes

步骤2 — 分类并分组变更

For each active change found in engram, check which artifact types exist:
  • explore
    → marks explore phase done
  • proposal
    → marks propose phase done
  • spec
    → marks spec phase done
  • design
    → marks design phase done
  • tasks
    → marks tasks phase done
  • verify-report
    → marks verify phase done
Infer phase label for each change:
ConditionPhase Label
No artifacts at allnot started
only explore (no proposal)explore only — awaiting proposal
proposal present, spec and design absentpropose done — awaiting spec/design
proposal + spec + design present, tasks absentspec+design done — awaiting tasks
tasks present, verify-report absenttasks done — ready for apply/verify
verify-report presentverify done — ready to archive
Group changes by action bucket:
READY TO ARCHIVE    : verify-report present
AWAITING SPEC/DESIGN: proposal present, tasks absent, (spec or design absent)
AWAITING APPLY      : tasks present, verify-report absent
EXPLORE ONLY        : only explore, no proposal

对于在engram中找到的每个活跃变更,检查存在哪些工件类型:
  • explore
    → 标记探索阶段完成
  • proposal
    → 标记提议阶段完成
  • spec
    → 标记规格阶段完成
  • design
    → 标记设计阶段完成
  • tasks
    → 标记任务阶段完成
  • verify-report
    → 标记验证阶段完成
推断每个变更的阶段标签:
条件阶段标签
无任何工件未开始
仅存在explore(无proposal)仅完成探索 — 等待提议
存在proposal,无spec和design提议完成 — 等待规格/设计
存在proposal + spec + design,无tasks规格+设计完成 — 等待任务
存在tasks,无verify-report任务完成 — 准备应用/验证
存在verify-report验证完成 — 准备归档
按操作类别分组变更:
READY TO ARCHIVE    : verify-report present
AWAITING SPEC/DESIGN: proposal present, tasks absent, (spec or design absent)
AWAITING APPLY      : tasks present, verify-report absent
EXPLORE ONLY        : only explore, no proposal

Step 3 — Render output

步骤3 — 生成输出

Output format (grouped, no redundancy):
Active SDD Changes

-- Ready to Archive --
  [change-name]   explore ok  proposal ok  spec ok  design ok  tasks ok  verify ok

-- Awaiting Apply/Verify --
  [change-name]   explore ok  proposal ok  spec ok  design ok  tasks ok  verify -

-- Awaiting Spec/Design --
  [change-name]   explore -  proposal ok  spec -  design -  tasks -  verify -

-- Explore Only (no proposal yet) --
  [change-name]   explore ok  proposal -

Next actions:
  - [N] ready to archive → /sdd-archive <name>
  - [N] awaiting spec/design → /sdd-spec <name> + /sdd-design <name>
Rules for this format:
  • Each group header is shown only if the group has at least one entry
  • Use
    ok
    for present,
    -
    for absent
  • "Next actions" section is omitted if all groups are empty
  • Do NOT repeat each change's phase in a separate list — the group it belongs to IS its phase

输出格式(分组展示,无冗余):
Active SDD Changes

-- Ready to Archive --
  [change-name]   explore ok  proposal ok  spec ok  design ok  tasks ok  verify ok

-- Awaiting Apply/Verify --
  [change-name]   explore ok  proposal ok  spec ok  design ok  tasks ok  verify -

-- Awaiting Spec/Design --
  [change-name]   explore -  proposal ok  spec -  design -  tasks -  verify -

-- Explore Only (no proposal yet) --
  [change-name]   explore ok  proposal -

Next actions:
  - [N] ready to archive → /sdd-archive <name>
  - [N] awaiting spec/design → /sdd-spec <name> + /sdd-design <name>
该格式规则:
  • 仅当组内至少有一个条目时才显示组标题
  • 使用
    ok
    表示存在,
    -
    表示不存在
  • 如果所有组均为空,则省略“Next actions”部分
  • 不要在单独列表中重复每个变更的阶段 — 所属组即为其阶段

Step 4 — Orchestrator state

步骤4 — Orchestrator状态

Read the project's
CLAUDE.md
and report:
  • Persistence mode: engram / none
  • Skills registry count (from
    ## Skills
    section)
  • Configuration source path
Include this as a header section BEFORE the active changes output:
Orchestrator
  Mode: [engram|none]
  Skills: [N] registered
  Config: [path to CLAUDE.md]

读取项目的
CLAUDE.md
并报告:
  • 持久化模式:engram / none
  • 技能注册表数量(来自
    ## Skills
    章节)
  • 配置源路径
将此部分作为标题区域放在活跃变更输出之前:
Orchestrator
  Mode: [engram|none]
  Skills: [N] registered
  Config: [path to CLAUDE.md]

Rules

规则

  • Read-only: I only inspect engram — no mutations
  • I never modify any files in this phase
  • If no engram artifacts found, I report gracefully and suggest
    /sdd-explore <topic>
    or
    /sdd-propose <change-name>
  • 只读模式:仅检查engram — 不执行任何修改
  • 在此阶段绝不修改任何文件
  • 如果未找到任何engram工件,友好提示并建议使用
    /sdd-explore <topic>
    /sdd-propose <change-name>