veschin

Use when bootstrapping an existing project into PTSD pipeline

Use when adding tasks to tasks.yaml

Use when reviewing BDD scenarios before advancing to tests stage

Use when reviewing implementation after all tests pass

Use when reviewing a PRD section before advancing to seed stage

Use when reviewing seed data before advancing to bdd stage

Use when reviewing tests before advancing to impl stage

Use at session start or when unsure what to do next

Use when bootstrapping an existing project into PTSD pipeline

Use at session start or when unsure what to do next

Use when writing Gherkin BDD scenarios for a feature

Use when implementing code to make failing tests pass

Use when creating golden seed data for a feature

Use when writing tests from BDD scenarios for a feature

Use when bootstrapping an existing project into PTSD pipeline

Invoke when writing or modifying a Bevy module (SimDomain/StaticData/View/InputUI) on the magnum_opus core. Enforces contract-first workflow.

Perform a hard audit of the Magnum Opus repo - build, tests, clippy warnings, unwrap/TODO counts, oversized files, PTSD pipeline state, and drift between CLAUDE.md claims and reality. Use at session start when CLAUDE.md claims feel stale, before committing large changes, or whenever asked to verify the true state of the code.

Read this BEFORE using the `hifi` tool on a hard or large engineering task (non-trivial code, a tricky algorithm, a system design, an incident diagnosis). hifi verifies ONE self-contained artifact by running it; this explains how to extract the verifiable pieces of your work and delegate each as one hifi run, instead of one-shotting a hard piece yourself or handing hifi a whole feature, scaffold, or multi-file build.