菜单
Show a pipeline overview of all specifications — counts of Draft / Implementing / Done, plus stale-spec detection.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Validate a spec directory end-to-end — structural completeness, FR/SC counts, falsifiable success criteria, FR coverage in plan tasks, no stale CL-N references, and constitution compliance. Single gate before implementation.
Create a specification for non-trivial platform changes. Creates a GitHub issue anchored to a spec directory with the SDD template. Type is auto-inferred from the description; pass an explicit type to override.
Resolve [NEEDS CLARIFICATION] markers — present 2–3 structured options, append the chosen decision as a CL-N entry to clarifications.md, replace the marker in spec.md with the CL-N reference. Append-only — never overwrites prior deliberations.
Create or update a Pull Request with AI-generated description, mermaid diagram, file walkthrough, and automatic SDD spec detection. Uses templates/pr-body.md for structure.
Verify that a merged spec's success criteria (SC-XXX) are actually met in the live cluster. Deploys the example manifest, watches Flux reconciliation, queries VictoriaMetrics/VictoriaLogs for evidence, writes docs/specs/<dir>/VERIFICATION.md.
Research patterns, ecosystem tools, and best practices before filling a spec. Runs in a forked Explore subagent so it can query Context7, WebSearch, and the whole codebase without consuming the main context window. Writes docs/specs/NNN-slug/research.md.
| name | spec-status |
| description | Show a pipeline overview of all specifications — counts of Draft / Implementing / Done, plus stale-spec detection. |
| when_to_use | When the user says "spec status", "where are we on specs", "spec pipeline", "what specs are in flight", "show SDD overview", "any stale specs", "what's in progress", or asks for a summary of ongoing spec work. |
| disable-model-invocation | true |
| allowed-tools | Bash(find:*), Bash(grep:*), Bash(gh:*), Read |
Display a pipeline overview of all specifications. Counts are pre-computed via dynamic context injection so Claude reasons on fresh state.
find docs/specs -name spec.md -not -path '*/done/*' -not -path '*/templates/*' -type f 2>/dev/null | sortfind docs/specs/done -name spec.md -type f 2>/dev/null | wc -lQ=$(( ($(date +%m) - 1) / 3 + 1 )); find "docs/specs/done/$(date +%Y)-Q${Q}" -name spec.md -type f 2>/dev/null | wc -lfind docs/specs -name spec.md -not -path '*/done/*' -not -path '*/templates/*' -mtime +14 -type f 2>/dev/nullgh issue list --label spec:draft --state open --json number,title --jq 'length' 2>/dev/null || echo "n/a"gh issue list --label spec:implementing --state open --json number,title --jq 'length' 2>/dev/null || echo "n/a"Render the pipeline overview the user sees.
For every file in the Active spec files list above, extract the **Status**: line (one of: draft, in-review, approved, implementing, done).
| Category | Spec statuses |
|---|---|
| Draft | draft, in-review |
| Implementing | approved, implementing |
| Done | (count from pre-computed done) |
╔═══════════════════════════════════════════════════════════════╗
║ Spec Pipeline Status ║
╚═══════════════════════════════════════════════════════════════╝
Stage Count Specs
────────────────────────────────────────────────────────────
Draft N <slug-list>
Implementing N <slug-list>
Done NN (archived in docs/specs/done/)
(NN this quarter)
⚠️ Stale (>14 days unchanged):
→ <slug> (last modified: <date>)
If the stale list is empty, omit that section. If GitHub issue counts differ from file counts, flag the drift (label desync).
[NEEDS CLARIFICATION] markers → suggest /clarify./validate./spec — create a new specification/clarify — resolve clarification markers/validate — check spec completeness/create-pr — create PR that auto-references spec