domains / families / software-engineering / executing-plans

executing-plans

combined

Use when you have a written implementation plan to execute in a separate session with review checkpoints Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available

When to use

• You have a plan from superpowers:writing-plans and your human partner
• Your harness has no subagent tool (see the per-platform references in
• Tasks are mostly independent — the same precondition as
• Use when implementing an existing written plan with verifiable tasks and checkpoints. Preserve the plan file when requested, use existing todos and the user’s latest batching/continuation instruction.

When not to use

• Use this skill only when the task clearly matches the scope described above.
• Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
• Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Skill page

Conflict

The copies describe two different execution models. obra/superpowers is an inline, continuous-execution skill with a ledger, TDD gates, and a single final review. The other three copies (sickn33, LeoYeAI, FreedomIntelligence) are a batched, checkpoint-driven skill that pauses for review between batches. They overlap in the high-level goal (execute a written plan) but disagree on batching, stopping behavior, and required sub-skills, so crowning one would hide a real alternative.