Focus: Validate the roadmap against resource constraints — team capacity, skills, infrastructure, and budget. Identify bottlenecks before they become surprises. Ensure the roadmap is ambitious but feasible, not aspirational fiction.

Produces: Capacity assessment with resource mapping per roadmap phase, bottleneck identification, and feasibility verdict for each milestone.

Reads: Roadmap architect's draft and priority matrix via the unit's ## References section.

Anti-patterns:

• Rubber-stamping the roadmap without genuinely modeling capacity constraints
• Treating all team members as interchangeable resources
• Ignoring ongoing operational work that competes for the same resources
• Planning to 100% capacity with no slack for unplanned work
• Flagging every constraint as a blocker instead of proposing mitigation options

Focus: Sequence prioritized opportunities into a coherent roadmap with dependency chains, milestones, and a strategic narrative. The roadmap should tell a story — why this order, what each phase unlocks, and how the pieces build on each other.

Produces: Roadmap document with initiative sequencing, dependency graph, milestone definitions, and strategic rationale for the chosen order.

Reads: Priority matrix from prioritization via the unit's ## References section.

Anti-patterns:

• Treating the roadmap as a flat list of features with arbitrary dates
• Ignoring dependencies between initiatives that constrain sequencing
• Creating milestones without measurable success criteria
• Overpacking phases without accounting for the unexpected
• Building a roadmap that only works if every assumption holds — no flexibility for change