investigation-state

What problem does it solve?

Preserve multi-session debugging context so hypotheses, evidence, eliminated approaches, and next steps are not lost between agent turns, system restarts, or handoffs, reducing duplicated work and missed clues during root-cause investigation.

Core Features & Use Cases

• Durable JSON store: Authoritative investigations are saved as UUID-named JSON files under the user's ~/.superpowers/investigations/ directory and updated atomically.
• CLI-first workflow: A single recommended tool (investigation-crud.sh) provides create, list, show, export, hypothesis/evidence management, lifecycle commands, and schema validation to avoid manual edits.
• Hypothesis & evidence tracking: Record hypotheses with structured evidence entries, verdicts, eliminated approaches, next steps, and related tickets or TODOs for clean handoffs and continuity.
• Lifecycle management & safety: Enforced states (active/paused/resolved/abandoned), stale-investigation checks, concurrent-investigation guidance, and markdown export for readable handoffs.
• Use case: Start a long-running reproduction and debugging session, persist all findings and checks, resume after interruption, or hand the investigation to another agent without losing context.

Quick Start

Start a new investigation and record the first hypothesis by running the investigation-crud.sh create command with a title, observed behavior, and reproduction steps.