executing-plans

Files (1)

• SKILL.md

SKILL.md (first lines)

# Executing Plans

1. Work on a branch, never directly on `main` or `master` — create one if needed. Where the work is long-running or would collide with other changes, an isolated worktree is worth it; decide that from the work in front of you, not from habit.
2. Read the plan in full.
3. Review it critically. Raise questions and concerns with your partner before starting, not halfway through.
4. Create a todo per task.
5. For each task: mark it in progress, follow its steps exactly as written, run every verification the plan specifies, then mark it complete.
6. Do not skip verifications and do not batch them to the end. The plan puts them where they are for a reason.
7. Stop and ask when you hit a blocker, a missing dependency, a verification that keeps failing, or an instruction you do not understand. Guessing costs more than asking.
8. If your partner revises the plan, return to step 2.

Terminal state: invoke finishing-a-development-branch.

From tim-hub/superpowers-slim, MIT.

More from tim-hub/superpowers-slim