Clean Room

First-run onboarding for Clean Room: say the one job, confirm REA readiness, then start intake. Encodes the carry-through rule and the intake clarification rule (confirm whether each link/repo is the RE target or the destination codebase).

Interview the user one question at a time about the target (what, where, type, one feature or whole app, goal, authorization basis) and write REA-TASK.md, the resumable state file for a Clean Room reverse-engineering run. Use after getting-started, or whenever no REA-TASK.md exists.

Reverse a target with REA: run the engine check, route by target type, start from the matching REA guided prompt, label every claim Observation/Inference/Unknown with Evidence IDs, record unknowns as they appear, and write SPEC.md as behaviour only with no target code. Use at Clean Room next_step 2, or when spec-judge returns rules.

The clean-room judge: check every SPEC.md rule against its cited Evidence and mark it approved, returned, or unknown; send returned rules back to rea-reverse, loop until nothing is returned, run a contamination check for copied target material, then get the user's sign-off. Use at Clean Room next_step 3.

Structured, adaptive interview that turns an approved SPEC.md into build decisions (intent, scope, what stays, what changes, users, platform, stack, constraints, UX, non-goals, acceptance, tests). Skips what SPEC answers, recommends a default for every question, asks about 12 at most in batches. Use at Clean Room next_step 4.

Assemble the single one-shot build prompt for Opus 5.5 from an approved SPEC.md and the rebuild decisions, using a fixed XML-tagged template. Fill every placeholder, write PROMPT.md, paste it in chat. Use at Clean Room next_step 5. The bot never runs the build.