Loading...
Loading...
Found 33 Skills
Auto-activates when working with implementation plans. Triggers on "continue the plan", "next task", "what's the plan status", "run task 2.1", or when user references plans/*.plan.md files. Not for creating plans - use /superplan command for that.
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Execute a phased implementation plan using subagents. Use when asked to execute, run, or carry out a plan — especially one created by make-plan.
Execute written implementation plans: first read and critically review the plan, then implement in small batches (default 3 tasks), produce verification evidence per batch and pause for feedback; must stop immediately and ask for help when blocked/tests fail/plan unclear. Trigger words: execute plan, implement plan, batch execution, follow the plan.
Execute software engineering plan documents using Eve jobs, dependencies, and review gating.
Execute implementation plans incrementally with verification at each step. Works through numbered sections one at a time, sanity-checks assumptions against the codebase, and stops on inconsistencies. Use when implementing a pre-defined plan document. Triggers on "implement this plan", "execute step 3.1", "resume plan at section 4".
Execute a verified plan document. Consumes verification receipts from tl-agent-plan-audit to avoid redundant re-verification. Defines the trust model, staleness protocol, and exit gate execution process. Use when executing a .plan.md file, starting plan implementation, or when the user says "implement the plan" or "execute the plan".
Execute detailed implementation plans systematically. Breaks down planned tasks into actionable steps with progress tracking and milestone management.
Use when executing implementation plans with independent tasks in the current session - dispatches fresh subagent for each task, reviews once per phase, loads phases just-in-time to minimize context usage
Execute approved implementation plans phase by phase with automated and manual verification. Use when the user explicitly says "implement the plan", "execute the plan", or "start implementing" and has a plan file ready. Do not use for ad-hoc coding tasks without a plan.
Execute all plans in a phase with wave-based parallelization
Execute an existing plan file. Use when a user asks to carry out a .plan.md task list.