# Reports from Dirigent

Process reports from the Dirigent project (`../dirigent`). They are copied here as input for replacing superpowers. They describe how superpowers-style orchestration (a subagent per task, a review between tasks, fix passes, re-checks, TDD/mutation habits) played out on real implementation work.

The copies are snapshots from 2026-10-15. Relative links inside them point into Dirigent's own workpad (`../dirigent/docs/workpad/`) and do not resolve here.

| Report | What it shows |
|---|---|
| [2026-10-14-chatgpt-importer-retrospective.md](2026-10-14-chatgpt-importer-retrospective.md) | Why the ChatGPT importer took ~25 h of wall clock instead of 1–2 h. Review → fix → re-check loops took about as long as writing the features (~5.2 h vs ~6 h). The table in §3 traces each heavy rule to its source: the user, the `CLAUDE.md` §Superpowers section, Igor, or builder habits. |
| [2026-10-01-lean-process-report.md](2026-10-01-lean-process-report.md) | A side-by-side comparison of the step-by-step baseline (an implementer per task, an Opus review every 1–2 tasks, scoped re-reviews) and the lean experiment, measured from git timestamps. It records the user's 2026-10-05 decision to make lean the default. |
| [2026-10-15-chatgpt-importer-handoff-lean-finish.md](2026-10-15-chatgpt-importer-handoff-lean-finish.md) | The lean rules that came out of the retrospective, written as binding brief rules: which checks run between blocks, tests once per step, no mutation runs. |