batteryshark Reconstruct an Implementation Brief
- Run
bin/reverse-brief PATHto collect a bounded repository inventory. - Inspect entry points, tests, public interfaces, configuration, examples, history, and user-visible text. Treat code as evidence of implementation, not proof of original intent.
- Write the brief using references/brief-template.md: problem, users, observed behavior, constraints, acceptance criteria, inferred decisions, contradictions, and open questions.
- Label every non-obvious statement as observed, inferred, or unknown. Cite concrete files and commands.
- Reconcile documentation against behavior and tests; surface contradictions instead of silently choosing a story.
Use agents/brief-reviewer.md for an independent intent-versus-evidence pass.