What problem does it solve?
Provides a disciplined, reproducible workflow for planning technical implementations, system architecture, and phased roadmaps so teams avoid scope drift, missed dependencies, and unclear handoffs.
Core Features & Use Cases
- Cross-plan dependency detection: scans existing plans in ./plans/, reads plan.md frontmatter, and marks blockedBy/blocks relationships to prevent conflicting work.
- Structured plan generation: produces plan.md and phase-XX.md files following strict frontmatter and output standards with task-hydration guidance.
- Review pipelines: supports archive, adversarial red-team reviews, and validation interviews to harden plans before implementation.
- Operational safety: prompts for confirmations on destructive actions (archive/delete) and mandates ask-user checkpoints for ambiguous decisions.
Quick Start
Use the ck:plan skill to create a new implementation plan for adding OAuth2 authentication, scanning ./plans/ for blockers and outputting the plan directory path.