shamt-architect-builder

What problem does it solve?

The two-stage architect-builder pattern separates planning from execution to dramatically reduce token costs while ensuring a mechanically verifiable plan. It reads the codebase and spec to generate a step-by-step implementation plan, validates it with a nine-dimension loop, and then spawns a Haiku builder to execute the plan in order.

Core Features & Use Cases

• Architect (Sonnet/Opus) analyzes the project and spec, creates a mechanically executable plan, and validates it with a 9-dimension loop.
• Builder (Haiku) reads the validated plan and executes each step sequentially without design decisions.
• Provides token savings (60-70%) during implementation and standardizes S6 or ad-hoc workflows for >10 file operations.

Quick Start

Create a mechanical implementation plan using architect-builder, validate it with the 9-dimension loop, then spawn Haiku to execute the plan.