fjy8018/superpowers-lite
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Create Superpowers Lite fork

Browse Source
This commit is contained in:
mujing
2026-05-12 16:05:03 +08:00
parent f2cbfbefeb
commit dd2eb8b351
33 changed files with 221 additions and 399 deletions
Download Patch File Download Diff File Expand all files Collapse all files

52
skills/executing-plans/SKILL.md
View File

@@ -1,39 +1,50 @@
---
name: executing-plans
description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
description: Manual-only skill. Activate only after an explicit user request for superpowers-lite:executing-plans.
---
# Executing Plans
## Overview
Load plan, review critically, execute all tasks, report when complete.
Load plan, review critically, group tasks into phases when useful, execute all phases, 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.
**Note:** Tell your human partner that Superpowers Lite works better with access to subagents for larger plans. If subagents are available and the user explicitly wants that workflow, use superpowers-lite: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 1: Confirm Branch, Load, and Review Plan
1. Confirm the current git branch is not `main` or `master` with `git branch --show-current`
2. If on `main` or `master`, stop and ask the user to switch or create a feature branch before implementation
3. Read plan file
4. Review critically - identify any questions or concerns about the plan
5. If concerns: Raise them with your human partner before starting
6. If no concerns: Create TodoWrite and proceed
### Step 2: Execute Tasks
### Step 2: Group Tasks Into Phases
For each task:
Before implementation, decide whether adjacent tasks should run as one phase:
- Group tasks that touch the same files or complete one coherent behavior
- Keep tasks separate when they are independent, risky, or easier to review alone
- Preserve the plan's task checklist, but use phase-level review checkpoints
### Step 3: Execute Phases
For each phase:
1. Mark as in_progress
2. Follow each step exactly (plan has bite-sized steps)
3. Run verifications as specified
4. Mark as completed
2. Follow each included task step exactly (plan has bite-sized steps)
3. Run verifications specified by the included tasks
4. Request or perform one review for the whole phase
5. Mark all included tasks as completed only after the phase review is addressed
### Step 3: Complete Development
### Step 4: 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
- **REQUIRED SUB-SKILL:** Use superpowers-lite:finishing-a-development-branch
- Follow that skill to verify tests, present options, execute choice
## When to Stop and Ask for Help
@@ -60,11 +71,14 @@ After all tasks complete and verified:
- 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
- Work in the current branch by default; do not create or switch to a worktree unless the user explicitly asks
- Never start implementation on `main` or `master`; ask the user to switch or create a feature branch
## 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
- **superpowers-lite:writing-plans** - Creates the plan this skill executes
- **superpowers-lite:finishing-a-development-branch** - Complete development after all tasks
**Optional workflow skills:**
- **superpowers-lite:using-git-worktrees** - Use only when the user explicitly asks for an isolated workspace