acaprino/executing-plans
plugins/ai-tooling/skills/executing-plans/SKILL.md
Execute an existing implementation plan task-by-task with verification at each step. TRIGGER WHEN: user says 'execute the plan', 'run the plan', 'implement the plan', 'start implementing'. DO NOT TRIGGER WHEN: user wants to write a plan (use writing-plans), wants to brainstorm (use brainstorming), or is doing ad-hoc implementation.
documentation
Updated Apr 20, 2026
$ install --global
skillsauthnpx skillsauth add acaprino/alfio-claude-plugins 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%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 20, 2026, 4:02 AM12.3s1 file scanned
SKILL.md
- name:
- executing-plans
- description:
- >
- TRIGGER WHEN:
- user says 'execute the plan', 'run the plan', 'implement the plan', 'start implementing'.
- DO NOT TRIGGER WHEN:
- user wants to write a plan (use writing-plans), wants to brainstorm (use brainstorming), or is doing ad-hoc implementation.
Source: Ported from obra/superpowers -- skills/executing-plans
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: This skill works best on platforms with subagent support (such as Claude Code or Codex). When subagents are available, prefer dispatching a fresh subagent per task for higher quality results.
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:
- Verify all tests pass
- Check if the project's
CLAUDE.mdneeds updating based on changes made (new files, changed conventions, updated dependencies) - If
CLAUDE.mdis stale, propose specific updates before finalizing - Present summary of what was built
- Offer options: merge to main, create PR, or clean up branch (squash commits, update docs)
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
Related skills and practices:
- ai-tooling:writing-plans - Creates the plan this skill executes
- Use a git worktree or dedicated branch to isolate work before starting
- After completion: verify tests pass, then merge, create PR, or clean up branch
Related Skills
acaprino/memory-forensics
tools
VerifiedTrustedCommunity
Master memory forensics techniques including memory acquisition, process analysis, and artifact extraction using Volatility and related tools. Use when analyzing memory dumps, investigating incidents, or performing malware analysis from RAM captures.
5SKILL.mdUpdated May 13, 2026
acaprino/binary-analysis-patterns
development
VerifiedTrustedCommunity
Master binary analysis patterns including disassembly, decompilation, control flow analysis, and code pattern recognition. Use when analyzing executables, understanding compiled code, or performing static analysis on binaries.
5SKILL.mdUpdated May 13, 2026
acaprino/kotlin-specialist
development
VerifiedTrustedCommunity
Idiomatic Kotlin implementation patterns: coroutines and structured concurrency, Flow / StateFlow / SharedFlow, Kotlin Multiplatform (KMP) shared-code architecture, Jetpack Compose UI, Ktor server with JWT auth and Exposed, and type-safe DSL design (lambdas with receivers, delegated properties, inline reified, value classes). TRIGGER WHEN: building, writing, or reviewing Kotlin code using coroutines / Flow / suspend functions, expect/actual, Compose composables / ViewModels, Ktor routing, sealed-class state modeling, scope functions, or DSL builders. DO NOT TRIGGER WHEN: libGDX game work (use libgdx-development), Android Java without Kotlin, or pure JVM tuning unrelated to Kotlin language features.
5SKILL.mdUpdated May 13, 2026
acaprino/frontend-strategy
tools
VerifiedTrustedCommunity
Strategic website planning skill that conducts structured client discovery, produces professional deliverables (website brief, sitemap, design direction, content strategy), and orchestrates frontend-design, frontend-layout, seo-specialist, and content-marketer agents automatically. TRIGGER WHEN: planning a new website or redesign before any code is written. DO NOT TRIGGER WHEN: the task is outside the specific scope of this component.
5SKILL.mdUpdated May 13, 2026