skill-ao92265-claude-code-playbook-executing-plans · by Install
$ agentstack add skill-ao92265-claude-code-playbook-executing-plans ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-ao92265-claude-code-playbook-executing-plans) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Executing Plans
Implement written plans through structured batches with review checkpoints.
When to Use
- A plan exists in
docs/plans/ - User says "execute the plan" or "implement the plan"
- After completing the writing-plans skill
- When resuming work on a documented plan
Process
Step 1: Load and Review
- Read the plan file from
docs/plans/ - Critically assess it - Does it still make sense?
- Raise concerns before proceeding
- Confirm understanding with user
Step 2: Execute Batch
Work through tasks in batches (typically 3 at a time):
- Mark progress - Note which task you're on
- Follow steps precisely - Don't skip verifications
- Run all commands - Check they produce expected output
- Commit after each logical unit
Step 3: Report Results
After each batch, use the batch report format from assets/execution-template.md.
Step 4: Continue or Adjust
Based on feedback:
- Continue - Execute next batch
- Adjust - Modify approach based on feedback
- Pause - Save progress and stop
Step 5: Complete Development
When all tasks done:
- Run final verification (all tests, linting)
- Summarize what was built
- Offer to commit/PR if not done
Critical Rules
STOP IMMEDIATELY When:
- Missing dependency - Something needed isn't available
- Unclear instructions - Plan step is ambiguous
- Failed verification - A check didn't pass
- Unexpected state - Reality doesn't match plan
Never force through obstacles or guess at solutions.
Return to Review When:
- Plan needs updating
- Fundamental approach needs to change
- New information changes requirements
Progress Tracking and Output Format
See assets/execution-template.md for the progress tracking block and per-task execution format.
Adapted from obra/superpowers executing-plans skill
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: ao92265
- Source: ao92265/claude-code-playbook
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.