Execução disciplinada de planos de implementação

O que esta skill faz

A executing-plans é usada quando já existe um plano de implementação para uma sessão separada. Ela exige revisão crítica antes do início, acompanhamento do estado de cada tarefa e execução fiel das verificações especificadas.

Quando usar

• Executar um plano técnico já aprovado
• Acompanhar tarefas com estados claros
• Aplicar verificações após cada etapa
• Concluir uma branch após implementar todo o plano

Como usar

1. Carregue o plano e revise o repositório relacionado
2. Identifique dúvidas ou lacunas críticas antes de começar
3. Transforme as tarefas em itens acompanháveis
4. Execute cada etapa e sua verificação na ordem prevista
5. Use finishing-a-development-branch ao concluir tudo

O que revisar antes de instalar

• Exige um plano escrito e suficientemente claro
• Deve parar diante de bloqueios ou ambiguidades críticas
• Com subagentes disponíveis, o fluxo indicado é subagent-driven-development
• Falhas repetidas de verificação exigem esclarecimento

SKILL.md

---
name: executing-plans
description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
---

# 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. The quality of its work will be significantly higher if run on a platform with subagent support (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.

## 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 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

## 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