| name | cc-investigate |
| version | 1.1.1 |
| description | Use when a bug, regression, broken task, or unexpected behavior needs root-cause investigation, reproducible evidence, and a frozen repair handoff before cc-do resumes coding. |
| triggers | ["帮我查这个 bug","先别修先找根因","debug this bug","investigate this regression","why is this broken","root cause this","先调查再修"] |
| reads | [".codex/skills/cc-investigate/PLAYBOOK.md",".codex/skills/cc-investigate/CHANGELOG.md",".codex/skills/cc-investigate/references/investigation-contract.md",".codex/skills/cc-investigate/assets/ANALYSIS_TEMPLATE.md",".codex/skills/cc-investigate/assets/TASKS_TEMPLATE.md",".codex/skills/cc-investigate/assets/TASK_MANIFEST_TEMPLATE.json"] |
| writes | [{"path":"devflow/changes/<change-key>/planning/analysis.md","durability":"durable","required":true},{"path":"devflow/changes/<change-key>/planning/tasks.md","durability":"durable","required":true},{"path":"devflow/changes/<change-key>/planning/task-manifest.json","durability":"durable","required":true},{"path":"devflow/changes/<change-key>/change-meta.json","durability":"durable","required":true}] |
| entry_gate | ["Read the current bug report, existing requirement artifacts, relevant code, tests, and recent history before forming any hypothesis.","Use a FIX-<number>-<description> change key for new bug-fix investigations.","Reproduce or narrow the symptom first, then freeze the evidence chain before proposing repair tasks.","Do not write production code here; this stage ends with planning/analysis.md plus executable repair tasks for cc-do."] |
| exit_criteria | ["planning/analysis.md records symptom, reproduction, evidence chain, confirmed root cause, and repair boundary.","planning/tasks.md and planning/task-manifest.json are explicit enough that cc-do can repair the bug without chat memory.","The honest next step is cc-do, cc-plan, or roadmap."] |
| reroutes | [{"when":"The issue is actually a new feature, a scope redesign, or a product decision instead of a bug investigation.","target":"cc-plan"},{"when":"The discussion expands into project sequencing or roadmap priority instead of one broken requirement.","target":"roadmap"},{"when":"Root cause and repair boundary are already frozen.","target":"cc-do"}] |
| recovery_modes | [{"name":"repro-reset","when":"The current conversation cannot state a stable reproduction path or the symptom evidence is stale.","action":"Drop the narrative, rebuild the reproduction from canonical artifacts and fresh output, then restate the symptom before testing hypotheses."},{"name":"re-open-investigation","when":"New execution evidence disproves the current root-cause contract or widens the suspected blast radius.","action":"Reopen planning/analysis.md, update the evidence chain, and regenerate repair tasks only after the new root cause is frozen."}] |
| tool_budget | {"read_files":10,"search_steps":6,"shell_commands":6} |
