Architect Sketch types, function signatures, class shapes, and module boundaries with bodies and pseudocode. Synthesize across multiple model perspectives, then fill in code against the chosen sketch. Start Open a todolist 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. Run the how skill over the relevant subsystems. Naming a file isn't grounding. Produce the architectural explanation prescribes. If the design redefines ownership or layering, also run the wh…