build-roadmaplisted

# Build Roadmap — foundation-first plan Sequence the work so the **shared foundation is built first**, then modules on top of it. Produce the test/UAT/smoke/QA plans up front so quality is designed in, not bolted on. This is the last planning stage before code — and it ends at the strictest gate in the pipeline. ## Fits in the pipeline - **Stage 5** (`/build-plan`). Input: module map + contracts (Stage 4), stack (Stage 3). Output: a sequenced roadmap + test plans that the Stage 6 coding swarm executes. Built with the `writing-plans` skill. ## Build the foundation FIRST Identify the shared base every module depends on and schedule it before any module work: - Project scaffold, the chosen stack wired up, config/secrets handling, CI skeleton. - Cross-cutting concerns: auth, logging/observability, error handling, the data layer, the module-linking mechanism (DI/registry) and shared contracts from `module-architecture`. - A walking skeleton: one thin end-to-end path that proves the foundation works. Only once the foundation is solid do modules get built on top of it (foundation → modules). ## Roadmap + milestones ``` Phase 0 — Foundation: <shared base items> → exit criteria: walking skeleton green. Phase 1..N — Modules: ordered by dependency (a module before its dependents). Each milestone: deliverable, the modules/contracts it completes, its exit criteria. ``` Order by the dependency graph; never schedule a module before what it depends on. Keep changes small and revi