AGENT SKILL

sp-executing-plans

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.

License 许可
MIT
最近更新
2026-09-09
Stars
★ 0
Forks
0

01 前言 Front Matter

name
sp-executing-plans
description
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.

02 资源文件 1

03 SKILL.md 正文

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 (Claude Code, Codex CLI, Codex App, Copilot CLI, and Gemini CLI all qualify; see the per-platform tool refs in the upstream superpowers:using-superpowers skill, which this marketplace does not vendor). If subagents are available, use sp-subagent-driven-development instead of this skill.

The Process

Step 1: Load and Review Plan

  1. Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one
  2. Read plan file
  3. Review critically - identify any questions or concerns about the plan
  4. If concerns: Raise them with your human partner before starting
  5. If no concerns: Create todos for the plan items 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

04 同仓库更多 Skills

ThodsaphonSonthiphin
ThodsaphonSonthiphin/Seem

wait-what

Stop. That last message did not land — re-pitch it.

★ 0
ThodsaphonSonthiphin
ThodsaphonSonthiphin/Seem

sp-writing-plans

You MUST use this, and not the upstream superpowers writing-plans skill, when you have a spec or requirements for a multi-step task, before touching code. The plan review is a checklist you run yourself, and execution hands off to sp-subagent-driven-development or sp-executing-plans.

★ 0
ThodsaphonSonthiphin
ThodsaphonSonthiphin/Seem

sp-subagent-driven-development

You MUST use this, and not the upstream superpowers subagent-driven-development skill, when executing implementation plans with independent tasks in the current session. Dispatched task and whole-branch reviews run the scrutinize-dispatch skill; the re-review is deliberately unrouted.

★ 0
ThodsaphonSonthiphin
ThodsaphonSonthiphin/Seem

sp-requesting-code-review

You MUST use this, and not the upstream superpowers requesting-code-review skill, when completing tasks, implementing major features, or before merging to verify work meets requirements. The review itself runs the scrutinize-dispatch skill.

★ 0
ThodsaphonSonthiphin
ThodsaphonSonthiphin/Seem

sp-receiving-code-review

You MUST use this, and not the upstream superpowers receiving-code-review skill, when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.

★ 0
ThodsaphonSonthiphin
ThodsaphonSonthiphin/Seem

sp-executing-plans

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.

★ 0