菜单
Runs the bug diagnosis stage: root-cause analysis with a failing reproduction test and reproduction scenarios, fix planning, and adversarial plan review. Use standalone for diagnosis-only work, or composed as the upstream stage of /belt:bug-fix. --codex enables adversarial plan review.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Experimental (mattpocock/skills wayfinder port, MIT). Charts a foggy effort as a shared Linear decision map, resolves its decision tickets across bounded sessions, and hands one graduated effort to /belt:requirements. Upstream of /belt:feature-dev; one run graduates exactly one effort.
Runs the shared build stage: TDD implementation from the plan document's task list and two-agent code review with autonomous triage. Use standalone with an existing plan.md/fix-plan.md, or composed as the build stage of /belt:feature-dev and /belt:bug-fix. QA runs as its own stage (/belt:qa) after build; integration happens at the orchestrator's integrate phase.
Runs the feature design stage: goal-sheet intake (/belt:goal) followed by a design document (architecture + key decisions) reviewed by belt:spec-reviewer. Use standalone for design-only work, or composed as the first stage of /belt:feature-dev. Task breakdown lives in the plan stage (/belt:plan), not here. --codex enables adversarial spec review.
Quality-gated feature pipeline from ticket to integration: goal-sheet intake, design document with spec review, implementation plan with QA scenarios, context-reset checkpoint, TDD implementation, autonomous code review, mandatory QA with human-readable evidence (screenshots / transcripts), and integration with evidence publishing. Accepts a Linear id, URL, free text, or a requirements.md path. --codex enables adversarial review.
Runs the implementation planning stage: writes plan.md (test strategy + task list) and scenarios.yml (QA replay scenarios) from an approved design.md, then reviews the plan via belt:spec-reviewer. Use standalone when a design already exists, or composed between the design and build stages of /belt:feature-dev. --codex enables adversarial plan review.
Interview-driven requirements definition. Resolves a Linear ticket, URL, or free-text request, investigates the codebase, asks only human-decidable questions in dependency-ordered rounds until the frontier is empty, and writes docs/requirements/<YYYY-MM-DD-topic>/requirements.md reviewed by belt:spec-reviewer. The result feeds /belt:feature-dev as input.
| name | diagnose |
| description | Runs the bug diagnosis stage: root-cause analysis with a failing reproduction test and reproduction scenarios, fix planning, and adversarial plan review. Use standalone for diagnosis-only work, or composed as the upstream stage of /belt:bug-fix. --codex enables adversarial plan review. |
| user-invocable | true |
| argument-hint | [--codex] |
Belt pipeline for the bug diagnosis stage. Pipeline structure, args, phase
order, and invocation mapping are defined in pipeline.yml and surfaced
dynamically by belt-agent next / belt-agent status. This SKILL.md covers
the supplement loading contract, phase-specific runtime notes, and red flags.
Artifacts follow the unified docs/features/<YYYY-MM-DD-topic>/ layout with
branch bugfix/<YYYY-MM-DD-topic> — see
plugins/belt/skills/design/references/path-convention.md (SSOT).
Before invoking a phase's skill, read the referenced supplement to inject
phase-specific overrides. fix-plan-review has no supplement; invoke its
declared skill directly.
| Phase | Supplement | Purpose |
|---|---|---|
| rca | ./references/rca-supplement.md | RCA Report 5 sections, Symmetry Check, Reproduction Test FAIL, parallel exploration order, rca-scenarios.yml produce (always) |
| fix-plan | ./references/fix-plan-supplement.md | RCA Fix Strategy -> task traceability, Given/When/Then test cases, verifiable completion conditions, task granularity |
/belt:spec-review is reused for fix-plan review. The
grill-me prompt under the design-judgment observation does not fire by
default (design decisions are already settled in rca / fix-plan). If it
fires, treat it as a signal that upstream phases need to be revisited.rca and fix-plan produce a narrative note so context can be restored
after /clear. Note paths are declared in pipeline.yml as
belt://current/notes/phase-<id>.md URIs; resolve the physical path via
belt-agent status (read phases[].produces[].resolved_path) or
belt-agent locate belt://current/notes/phase-<id>.md.
Each note contains four sections (## Decisions / ## Concerns /
## Directives / ## Observations) and minimal frontmatter (phase,
run_id).
Full convention: plugins/belt-agent/references/narrative-convention.md
docs/features/<topic>/: they are phase-produced; manual edits break belt's phase-start mtime filter.(none) placeholders and keep headings../references/rca-supplement.md — rca phase override./references/fix-plan-supplement.md — fix-plan phase overrideplugins/belt/skills/design/references/path-convention.md — docs/features/<YYYY-MM-DD-topic>/ naming rules (SSOT)plugins/belt-agent/references/narrative-convention.md — narrative note schema