Loading...
Loading...
Found 21 Skills
Use when you have a written implementation plan to execute in a separate session with review checkpoints
This skill should be used when the user has a written implementation plan to execute in a separate session with review checkpoints.
This skill should be used when the user has a completed implementation plan (plan.md) and is ready to execute the tasks defined therein. Actively uses Agent Teams or subagents to execute batches of independent tasks in parallel, following BDD/TDD principles.
Use this when you have a written implementation plan and execute it in separate sessions with review checkpoints
Use when you have an approved implementation plan document and need to execute it step by step. Triggers on /execute command, when transitioning from planning with an approved plan, or when resuming execution of a partially completed plan. Provides batch-based execution with TDD, checkpoint reviews, and verification gates.
Use this when you have a written implementation plan to execute in a separate session with review checkpoints.
Execute an approved implementation plan in a separate session with checkpoint reviews. Use after writing-plans when the user wants batched progress updates before more work continues.
You MUST use this, and not the upstream superpowers executing-plans skill, when you have a written implementation plan to execute in a separate session with review checkpoints. Review checkpoints are run in-session by you, not dispatched to a reviewer subagent.
Executes implementation plans with smart task grouping. Groups related tasks to share context, parallelizes across independent subsystems.
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
Disciplined plan execution for implementation tasks. Use when executing a saved implementation plan, following step-by-step instructions from a plan document.
Execute a written implementation plan task-by-task with inline verification. Stop and ask on blockers. No forced sub-skill chains. Use when a plan exists and you're ready to implement.