plan-management

Phase transitions are automated based on task completion and plan-related keywords. The Skill enforces proper workflow states within the roadmap → milestones → playbooks → phases hierarchy, preventing invalid transitions and ensuring systematic progress through your project structure.

Yes. The Skill automatically generates detailed playbooks from task descriptions, organizing them within your roadmap hierarchy. Each playbook maps to a single branch and enforces a one-task-per-playbook policy to maintain clarity and prevent scope drift.

Use hierarchical planning to structure work as roadmaps → milestones → playbooks → phases. The Skill coordinates this hierarchy automatically, manages phase transitions, and ensures coherence between playbooks, state documentation, and git branches throughout your project lifecycle.

It enforces coherence among playbooks, state records, and git branches while requiring evidence-based task completion and critic verification before commit. This structured validation prevents tasks from expanding beyond their defined playbook scope.

No. The Skill automatically synchronizes state.md, playbooks, and git branches, applying triggers on plan-related keywords during new-task creation, phase transitions, session starts, and task completions.

Invalid transitions are blocked by the Skill's state enforcement. It validates transitions within your playbook phases and requires proper completion evidence before advancing, maintaining workflow integrity across your project hierarchy.