Phase 5 — Quality & Planning
Roadmap
The sequence that prevents your AI agent from building v3 features before v1 works
2 min read · Document 23 of 30
What is this document?
The Roadmap orders the work into milestones with dependencies, so foundations are built before the features that depend on them.
It separates the first release from later enhancements, keeping scope honest.
Why does it matter?
- Without a roadmap, AI tools implement the most interesting features rather than the most foundational ones.
- Dependencies are explicit, so nothing is built on missing ground.
- The first release stays focused.
What's inside?
- Milestones — Ordered milestones with goals.
- Dependencies — What must finish first.
- Later — Enhancements deliberately deferred.
FoundationCore journeysAdminMarketingLaunch
How CREAH generates it
CREAH builds this document from your Stage 0 answers and interview. Questions that shape it include:
- What must work on launch day?
- Which features can wait for version two?
- Is there a fixed launch date?
Example excerpt
## M1 — Foundation
Auth, database, configuration, base styles. Blocks every other milestone.
## M2 — Core journey
Signup → first value. Depends on M1.
## Later
Referral programme, advanced analytics.Related documents
Phase 2
Product Requirements Document (PRD)
The contract between what you imagined and what gets built
Phase 5Risk Register
The risks your AI coding agent can’t anticipate but you definitely should
Phase 6Build Sequence Specification
Step by step — what to build first, what comes next, which documents to attach