executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
executing-plans
Disciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.
cc-task
Implement based on an approved plan. Use after cc-plan is finalized.
project-planner
Detects stale project plans and suggests /plan command usage. Triggers on: sync plan, update plan, check status, plan is stale, track progress, project planning.
executing-plans
Use when partner provides a complete implementation plan to execute in controlled batches with review checkpoints - loads plan, reviews critically, executes tasks in batches, reports for review between batches
plan
>
executing-parallel-phase
Use when orchestrating parallel phases in plan execution - creates isolated worktrees for concurrent task execution, installs dependencies, spawns parallel subagents, verifies completion, stacks branches linearly, and cleans up (mandatory for ALL parallel phases including N=1)
plan-executor
Execute implementation plans step-by-step. Use when user says "execute the plan", "implement the plan we created", "start building based on the plan", "go ahead and implement it", "proceed with the implementation", or references a plan file and wants to begin coding.
ln-302-task-replanner
Updates ALL task types (implementation/refactoring/test). Compares IDEAL plan vs existing tasks, categorizes KEEP/UPDATE/OBSOLETE/CREATE, applies changes in Linear and kanban.
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code