メニュー
Diagnose and fix a bug in the existing codebase. Enforces: reproduce first, write failing test, implement smallest fix, verify all tests pass, document root cause.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Run a goal-bounded autonomous loop over the harness — select, build, verify, and commit features one at a time with a maker/checker split, an explicit stop-contract, and a per-run token/commit budget. Best run in the orchestrator agent.
Sync FEATURES.json and PLAN.md after architecture or scope changes mid-project. Preserves completed feature status while updating not-started features to align with the latest ARCHITECTURE.md and PLAN.md.
Initialize a new harness-managed solution project from a brief idea. Use when starting a brand new project. Creates docs/IDEA.md, docs/PLAN.md, docs/FEATURES.json, docs/ARCHITECTURE.md, docs/PROGRESS.md, AGENTS.md, and .github/copilot-instructions.md.
Design a feature before building it — research latest patterns, evaluate approaches, design APIs/data models/UI, and produce a technical design document. Use after /add-features and before the builder starts implementing.
Provide feedback on a design document and request changes. Use after /design-feature to iterate on the technical design before implementation begins. Supports multiple rounds of review.
Plan new features to add to an existing onboarded project. Analyzes impact on existing modules, designs features that fit the current architecture, and ensures backward compatibility.
| name | fix-issue |
| description | Diagnose and fix a bug in the existing codebase. Enforces: reproduce first, write failing test, implement smallest fix, verify all tests pass, document root cause. |
The user will describe the bug, error message, or unexpected behavior.
Read docs/ARCHITECTURE.md and docs/FEATURES.json to identify the affected area.
NEVER skip reproduction. Read the code, run existing tests, reproduce manually if possible. If you can't reproduce, document what you tried and ask for more details.
Trace the call chain. Check recent git commits. Check if the same pattern exists elsewhere. Classify: logic error, data error, integration error, configuration error, or regression.
Write a test that reproduces the exact bug scenario — it must FAIL with current code and PASS after the fix.
Smallest possible change. Don't refactor surrounding code. Fix all occurrences if the same bug exists elsewhere.
Run the new test (should pass). Run ALL existing tests (nothing else should break). Reproduce original issue (should be gone).
Add a B-prefix entry to docs/FEATURES.json with status "complete". Update docs/PROGRESS.md with root cause, fix, and regression test. Commit: fix(B###): description
Is this a pattern that could exist elsewhere? Suggest /refactor if so.
