waypoint-design

To turn a roadmap entry into a design document, provide a waypoint stub to generate a structured design with clear objectives and acceptance criteria. The process evaluates dependencies and unblocked status to scale the design to the waypoint's complexity.

Waypoint design is the process of converting a roadmap stub into a formal, implementation-ready design document. It enables effective task decomposition by defining a clear objective and acceptance criteria scaled to the waypoint's complexity.

To select unblocked waypoints from a roadmap with dependencies, analyze the dependency chain and status tracking. The workflow guides you to identify waypoints whose dependencies are resolved, ensuring they are ready for formal design and task decomposition.

Yes, you can include delegation flows when generating a waypoint design. The design process supports optional delegation flows, allowing you to produce implementation-ready content that can be handed off to a plan or build step.

The best way to decompose complex roadmap tasks is to generate a structured waypoint design that assesses complexity and gathers context. This produces implementation-ready content with clear acceptance criteria, enabling reliable task decomposition.

Your roadmap waypoint lacks clear acceptance criteria because it remains a stub. Converting the entry into a formal waypoint design gathers context and assesses complexity to explicitly define the objective and required acceptance criteria.