5889d3428b
- Added 44 external skills from obra/superpowers, ui-ux-pro-max-skill, claude-codex-settings - Added 8 autonomous agents (commit-creator, pr-creator, pr-reviewer, etc.) - Added 23 slash commands for Git/GitHub, setup, and plugin development - Added hooks for code formatting, notifications, and validation - Added MCP configurations for Azure, GCloud, Supabase, MongoDB, etc. - Added awesome-openclaw-skills registry (3,002 skills referenced) - Updated comprehensive README with full documentation Sources: - github.com/obra/superpowers (14 skills) - github.com/nextlevelbuilder/ui-ux-pro-max-skill (1 skill) - github.com/fcakyon/claude-codex-settings (29 skills, 8 agents, 23 commands) - github.com/VoltAgent/awesome-openclaw-skills (registry) - skills.sh (reference) - buildwithclaude.com (reference)
85 lines
2.5 KiB
Markdown
85 lines
2.5 KiB
Markdown
---
|
|
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 tasks in batches, report for review between batches.
|
|
|
|
**Core principle:** Batch execution with checkpoints for architect review.
|
|
|
|
**Announce at start:** "I'm using the executing-plans skill to implement this plan."
|
|
|
|
## 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 Batch
|
|
**Default: First 3 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: Report
|
|
When batch complete:
|
|
- Show what was implemented
|
|
- Show verification output
|
|
- Say: "Ready for feedback."
|
|
|
|
### Step 4: Continue
|
|
Based on feedback:
|
|
- Apply changes if needed
|
|
- Execute next batch
|
|
- Repeat until complete
|
|
|
|
### Step 5: 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 mid-batch (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
|
|
- Between batches: just report and wait
|
|
- 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** - REQUIRED: Set up isolated workspace before starting
|
|
- **superpowers:writing-plans** - Creates the plan this skill executes
|
|
- **superpowers:finishing-a-development-branch** - Complete development after all tasks
|