executing-plans

โดย obra

ใช้เมื่อคุณมีแผนการดำเนินงานที่เขียนไว้เพื่อดำเนินการในเซสชันแยกต่างหาก โดยมีจุดตรวจสอบเพื่อทบทวน

npx skills add https://github.com/obra/superpowers --skill executing-plans

Executing Plans

Overview

Load plan, review critically, execute all tasks, report when complete.

Announce at start: "I'm using the executing-plans skill to implement this plan."

Note: Tell your human partner that Superpowers works much better with access to subagents. The quality of its work will be significantly higher if run on a platform with subagent support (such as Claude Code or Codex). If subagents are available, use superpowers:subagent-driven-development instead of this skill.

The Process

Step 1: Load and Review Plan

  1. Read plan file
  2. Review critically - identify any questions or concerns about the plan
  3. If concerns: Raise them with your human partner before starting
  4. If no concerns: Create TodoWrite and proceed

Step 2: Execute Tasks

For each task:

  1. Mark as in_progress
  2. Follow each step exactly (plan has bite-sized steps)
  3. Run verifications as specified
  4. Mark as completed

Step 3: Complete Development

After all tasks complete and verified:

  • Announce: "I'm using the finishing-a-development-branch skill to complete this work."
  • REQUIRED SUB-SKILL: Use superpowers:finishing-a-development-branch
  • Follow that skill to verify tests, present options, execute choice

When to Stop and Ask for Help

STOP executing immediately when:

  • Hit a blocker (missing dependency, test fails, instruction unclear)
  • Plan has critical gaps preventing starting
  • You don't understand an instruction
  • Verification fails repeatedly

Ask for clarification rather than guessing.

When to Revisit Earlier Steps

Return to Review (Step 1) when:

  • Partner updates the plan based on your feedback
  • Fundamental approach needs rethinking

Don't force through blockers - stop and ask.

Remember

  • Review plan critically first
  • Follow plan steps exactly
  • Don't skip verifications
  • Reference skills when plan says to
  • Stop when blocked, don't guess
  • Never start implementation on main/master branch without explicit user consent

Integration

Required workflow skills:

  • superpowers:using-git-worktrees - Ensures isolated workspace (creates one or verifies existing)
  • superpowers:writing-plans - Creates the plan this skill executes
  • superpowers:finishing-a-development-branch - Complete development after all tasks

Skills เพิ่มเติมจาก obra

brainstorming
obra
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
creativeresearchdesign
systematic-debugging
obra
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
developmenttestingcode-review
writing-plans
obra
Use when you have a spec or requirements for a multi-step task, before touching code
developmentproject-management
using-superpowers
obra
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
developmentdocumentproductivity
requesting-code-review
obra
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
developmentcode-review
test-driven-development
obra
Use when implementing any feature or bugfix, before writing implementation code
developmenttestingcode-review
verification-before-completion
obra
ใช้เมื่อกำลังจะยืนยันว่างานเสร็จสมบูรณ์ แก้ไขแล้ว หรือผ่านเกณฑ์ ก่อนที่จะคอมมิตหรือสร้าง PR - ต้องรันคำสั่งตรวจสอบและยืนยันผลลัพธ์ก่อนที่จะอ้างว่าสำเร็จเสมอ ต้องมีหลักฐานก่อนการยืนยันเสมอ
testingcode-reviewdevelopment
subagent-driven-development
obra
ใช้เมื่อดำเนินการตามแผนการดำเนินงานที่มีงานอิสระในเซสชันปัจจุบัน
developmentproject-management