10x-roadmap

Generating a roadmap from a PRD involves reading the product requirements and probing the codebase baseline to infer an ordered sequence of user-visible slices. The process produces dependency-ordered milestones suitable for downstream planning.

Dependency sequencing in product delivery is the process of ordering vertical, end-to-end slices based on codebase baseline evidence and gaps. It ensures milestones are ordered correctly to prevent execution errors during codebase implementation.

Handling unknown requirements when creating a roadmap involves running a capped human interview of 2–3 anchoring choices to surface real unknowns. Slices are then marked as proposed, ready, or blocked instead of guessing.

Yes, roadmap generation works with an existing tech-stack file by optionally using context/foundation/tech-stack.md and shape-notes.md alongside the PRD. This baseline-aware sequencing uses existing repository evidence to skip known work.

You cannot accidentally overwrite an existing roadmap file because the Skill detects when roadmap files already exist and routes the interaction to prevent collisions. This roadmap collision handling protects your prior planning workflow.

A key limitation of automated PRD decomposition is that it must avoid implementation-level decisions and cannot resolve all unknowns. It relies on a capped human interview to route open questions and mark blocked slices.