Install
$ agentstack add skill-rbraga01-a-team-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.
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
Load plan, review critically, execute all tasks, report when complete.
Announce at start: "I'm using the executing-plans skill to implement this plan."
Prefer subagent-driven-development over this skill when subagents are available — it provides higher quality through per-task fresh context and two-stage review.
The Process
Step 1: Load and Review Plan
- Read plan file completely
- Review critically — identify questions or concerns about the plan
- If concerns: raise with human partner BEFORE starting
- If no concerns: create TodoWrite and proceed
Step 2: Execute Tasks
For each task:
- Mark as in_progress
- Follow each step exactly (plan has bite-sized steps)
- Run verifications as specified
- Mark as completed
Do not pause to check in between tasks unless blocked.
Step 3: Complete Development
After all tasks complete:
- Use
finishing-a-development-branchskill - Verify tests, update docs, commit
When to Stop and Ask
STOP executing immediately when:
- Hit a blocker (missing dependency, test fails, instruction unclear)
- Plan has critical gaps preventing starting
- Verification fails repeatedly
Ask for clarification rather than guessing.
Hard Rules
- Never start on main/master branch without explicit user consent
- Follow plan steps exactly — don't improvise
- Stop when blocked, don't guess
- Skip nothing in the verification steps
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: RBraga01
- Source: RBraga01/a-team
- License: MIT
- Homepage: https://rbraga01.github.io/a-team/
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.