ck:plan

To create a technical implementation plan, you transform feature requirements into research-backed phases, deliverables, and output standards. This process eliminates vague ideas by producing detailed, phase-based documentation you can validate and execute safely.

Task hydration in workflow planning is the process of expanding phase steps into executable session tasks. It hydrates execution tasks by phase when appropriate, enforcing best-practice rules while handing off to the next execution step.

Yes, you can apply red-team review and validation gates to system architecture roadmapping. The planning workflow supports fast, hard, parallel, and two-approach modes to validate solution designs before producing final phase documentation.

The best way to break down system architecture is applying phase breakdown techniques that turn requirements into research-backed phases and deliverables. This yields self-contained plan.md and phase files with absolute plan paths for execution.

No, you do not need external dependencies to generate a phase-based technical roadmap. The planning workflow operates independently with a references component, requiring only your feature or technical task input to produce the plan.

The planning workflow hands off execution tasks by hydrating phase steps into session tasks and always outputting a cook handoff reminder. This reminder includes an absolute plan path to ensure seamless execution continuity.