executing plans

Engineering Community

Skill notes

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 ../using-superpowers/references/). If subagents are available, use superpowers:subagent-driven-development instead of this skill.

Step 1: Load and Review Plan

Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one Read plan file Review critically - identify any questions or concerns about the plan If concerns: Raise them with your human partner before starting If no concerns: Create todos for the plan items and proceed

Step 2: Execute Tasks

For each task: Mark as in_progress Follow each step exactly (plan has bite-sized steps) Run verifications as specified 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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@obra · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Load and Review Plan

Ensure an isolated workspace: use superpowers:using-git-worktrees to create one or verify the existing one Read plan file Review critically - identify any questions or concerns about the plan If concerns: Raise them with your human partner before starting If no concerns: Create todos for the plan items and proceed

02
Step 2: Execute Tasks

For each task: Mark as in_progress Follow each step exactly (plan has bite-sized steps) Run verifications as specified Mark as completed

03
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

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.