b-mendoza/executing-plans
.agents/skills/executing-plans/SKILL.md
Use when you have a written implementation plan to execute in a separate session with review checkpoints
testing
Updated Apr 3, 2026
$ install --global
skillsauthnpx skillsauth add b-mendoza/agent-skills executing-plansInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Error
VirusTotalMulti-engine malware detection
70%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 20, 2026, 7:31 AM230.3s1 file scanned
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 (such as Claude Code or Codex). If subagents are available, use superpowers:subagent-driven-development instead of this skill.
The Process
Step 1: Load and Review Plan
- Read plan file
- Review critically - identify any questions or concerns about the plan
- If concerns: Raise them with your 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
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 - 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
Related Skills
b-mendoza/diagnosing-root-causes
testing
VerifiedTrustedCommunity
Diagnoses runtime bugs, crashes, regressions, failing CI/CD pipelines, and underspecified user reports through read-only, evidence-first root-cause analysis with traceable reports and bounded subagent workflows.
SKILL.mdUpdated Jun 9, 2026
b-mendoza/orchestrating-workflow
tools
VerifiedTrustedCommunity
Coordinate an end-to-end Jira or GitHub work-item workflow from initial fetch through per-task implementation. Use this skill when the user provides a Jira ticket URL, a GitHub issue URL, owner/repo/issue coordinates, says "work on ticket PROJECT-123", "work on issue owner/repo#42", "resume <work-item-key>", "continue this workflow", or asks for status without naming a specific phase. This top-level coordinator detects the platform from the input, loads the matching playbook just-in-time, keeps SKILL.md as a routing layer, and dispatches execution-heavy work to downstream skills or co-located utility subagents.
SKILL.mdUpdated Jun 6, 2026
b-mendoza/fetching-work-item
testing
VerifiedTrustedCommunity
Retrieves a Jira ticket or a GitHub issue into docs/<KEY>.md as a read-only, validated Markdown snapshot for downstream workflow phases. Use when a Jira URL, a GitHub issue URL, or owner/repo/number coordinates need the Phase 1 fetch-work-item step. Detects the platform from the input and loads the matching playbook just-in-time.
SKILL.mdUpdated Jun 6, 2026
b-mendoza/council-of-advisors
development
VerifiedTrustedCommunity
Runs a structured nine-seat council deliberation on an idea, project, business, startup, goal, or objective, then writes a full decision handoff file with a compact recommendation summary and reusable mental-model teaching cards. Use when a user asks to stress-test a decision, get adversarial review, classify a decision as reversible or irreversible, or wants multiple independent perspectives on a course of action.
SKILL.mdUpdated Jun 4, 2026