Architect

Sketch types, function signatures, class shapes, and module boundaries with not implemented bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch.

Start

Open a worklist with one entry per phase before starting.

1. Ground
2. Sketch
3. Agree
4. Implement
5. Scrap

Phase A: Ground the problem

Build a real mental model of every system the new code touches. Use the how skill on the relevant subsystems.

Naming a file isn't grounding. Produce the architectural explanation how prescribes. If the design redefines ownership or layering, also use the why skill on the existing shape so the rationale becomes a constraint, not a guess.