Execute Plan
Batch-execute tasks from the active epic capsule sequentially, with a human checkpoint after each step. Use when user has an approved plan and wants step-by-step oversight.
Install
$ agentstack add skill-danielvm-git-bigpowers-execute-plan ✓ 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-danielvm-git-bigpowers-execute-plan) 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
Execute Plan
Execute tasks from the active epic (specs/epics/eNN-slug/epic.yaml story tasks[]) one at a time, showing evidence after each step before proceeding.
> HARD GATE — Do NOT proceed if on main or master. Run kickoff-branch first. > > HARD GATE — Active epic must exist with runnable verify on each task. If missing, run plan-release then plan-work or build-epic.
Process
1. Read the plan
Read specs/state.yaml (active_epic, active_story) and the matching specs/epics/*/epic.yaml. Parse depends-on in task descriptions for execution waves.
> CONTEXT ISOLATION — Spawn each skill with a fresh context window. Pass decisions only through specs/state.yaml handoff — never rely on prior chat history.
Confirm with the user: step count, skip/reorder, stop-after step.
2. Execute step by step
For each task in the active story:
a. Announce — task desc and verify command.
b. Execute — code or delegate-task / dispatch-agents for waves.
c. Run verify — must be green before advancing.
d. Log — non-obvious decisions in specs/state.yaml under decisions[] or handoff block.
e. Checkpoint — ask to proceed unless autonomous mode requested.
f. Story UAT — after last task, run manual verification script from story notes or verify-work.
On verify failure: fix and re-run; never advance on red.
Update specs/execution-status.yaml when a story/epic completes (bash scripts/sync-status-from-epics.sh or direct edit).
3. Blockers
Report blocker; ask skip/adapt/stop; update epic capsule if plan changes.
4. Final report
Suggest: verify-work → run-evals → audit-code → simulate-agents → commit-message → release-branch
Rules
- Loop until behavioral correctness is verified: if a verify command passes but the observed behavior is still wrong, return to step 1 and run the execution cycle again.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: danielvm-git
- Source: danielvm-git/bigpowers
- License: MIT
- Homepage: https://github.com/danielvm-git/bigpowers
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.