missions
Missions
Autonomous multi-milestone development for large goals. Takes a big objective, decomposes it into milestones and features, builds each feature via TDD in isolated worktrees, then gates each milestone behind independent validation agents that exercise the system as a black box.
The key insight from Factory's architecture: agents are highly reactive to their context. An agent that implemented something is biased toward confirming its own work. Missions separates the "build" and "judge" roles with fresh context boundaries, and defines success criteria (the validation contract) before any code is written.
Principle #10 (Agents drift, gates don't) — the validation contract IS the gate. Independent validators with no shared context with the builders are what keep a multi-day autonomous run from optimizing toward "looks done." Principle #2 (Rebuild often) — between milestones, ask "would I structure this the same way knowing what I know now?" before continuing. The reflection point is built into the milestone boundary for a reason. See /principles.