ck:plan

To create a technical roadmap, provide a high-level task description to initiate planning and generate a formal plan with phases, milestones, and dependencies. This documents implementation architectures to guide feature development.

Automated planning workflows enable phase definition and task hydration by taking a high-level task description and expanding it into structured phases, milestones, and documented dependencies for cross-team coordination.

The best way to align stakeholders across multiple squads is through cross-team collaboration planning, which identifies dependencies, milestones, and trade-offs to improve delivery predictability for technical roadmaps.

Yes, you can use it for risk assessment and governance during solution architecture design. It identifies trade-offs, constraints, and validation checkpoints specifically to de-risk delivery of complex initiatives.

You need formal documentation for implementation architectures and milestones when orchestrating complex technical plans across features. It is required to improve delivery predictability and manage cross-team coordination.

Planning technical roadmaps without cross-team coordination limits delivery predictability, as you cannot effectively identify dependencies, manage trade-offs, or establish validation checkpoints across multiple squads.