shamt-architect-builder

To reduce token costs for large code implementation tasks, you can separate planning from execution. An architect model generates a validated plan, and a Haiku builder executes it sequentially, saving 60-70% in token usage.

The architect-builder pattern is a two-stage workflow that separates planning from execution. The architect reads the codebase to generate a step-by-step plan with exact locate/replace content, validates it, and hands it off to a builder for mechanical execution.

Use the architect-builder workflow instead of traditional end-to-end implementation for S6 implementations or ad-hoc work involving more than 10 file operations. This approach standardizes workflows and ensures mechanically verifiable plans.

To create a mechanically executable plan for code automation, format steps explicitly for CREATE, EDIT, DELETE, or MOVE operations. Include exact locate and replace content so the builder can execute each step sequentially without design decisions.

The 9-dimension validation loop works by checking the generated implementation plan against nine distinct criteria. This ensures the plan is mechanically verifiable and seamless before the Haiku builder begins the execution phase.