OpenSkillIndex← back to search
claude-code

Awesome-vibe-coding executing-plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

install
source · Clone the upstream repo
git clone https://github.com/adriannoes/awesome-vibe-coding
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/adriannoes/awesome-vibe-coding "$T" && mkdir -p ~/.claude/skills && cp -r "$T/cursor/skills/executing-plans" ~/.claude/skills/adriannoes-awesome-vibe-coding-executing-plans && rm -rf "$T"
manifest: cursor/skills/executing-plans/SKILL.md
source content

Executing Plans

Source: obra/superpowers (MIT) · v5.0.5

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: Subagent-driven development (dispatching fresh subagents per task) often yields higher quality. If subagents are available, prefer that approach. Otherwise, use this skill for inline execution with checkpoints.

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."
  • Use finishing-a-development-branch 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:

  • using-git-worktrees - Set up isolated workspace before starting (recommended for feature work)
  • writing-plans - Creates the plan this skill executes
  • finishing-a-development-branch - Complete development after all tasks