kienbui1995/executing-plans
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 23, 2026
$ install --global
skillsauthnpx skillsauth add kienbui1995/magic-powers 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 24, 2026, 12:56 AM42.4s1 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
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: If subagents are available, use magic-powers:subagent-driven-development instead — higher quality through fresh context per task.
The Process
Step 1: Load and Review Plan
- Read plan file
- Review critically — identify questions or concerns
- If concerns: raise with user 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
- Use magic-powers:verification-before-completion before marking done
- Mark as completed
Step 3: Complete Development
After all tasks verified:
- Use magic-powers:finishing-a-development-branch
- Verify tests, present options, execute choice
When to Stop and Ask for Help
STOP executing immediately when:
- Hit a blocker (missing dependency, test fails, unclear instruction)
- 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:
- User 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
- Stop when blocked, don't guess
- Never start implementation on main/master without explicit user consent
Integration
Required workflow skills:
- magic-powers:using-git-worktrees — set up isolated workspace before starting
- magic-powers:writing-plans — creates the plan this skill executes
- magic-powers:finishing-a-development-branch — complete development after all tasks
- magic-powers:verification-before-completion — verify before claiming done
Related Skills
kienbui1995/xr-interface-design
content-media
VerifiedTrustedCommunity
Use when designing for XR (AR/VR/MR), choosing interaction modes, or adapting 2D UI patterns for spatial computing
SKILL.mdUpdated Apr 24, 2026
kienbui1995/writing-skills
testing
VerifiedTrustedCommunity
Use when creating new skills, editing existing skills, or verifying skills work before deployment
SKILL.mdUpdated Apr 24, 2026
kienbui1995/writing-plans
development
VerifiedTrustedCommunity
Use when you have a spec or requirements for a multi-step task, before touching code
SKILL.mdUpdated Apr 24, 2026
kienbui1995/workflow-templates
development
VerifiedTrustedCommunity
Use when executing a structured workflow — select and run a feature, bugfix, refactor, research, or incident template with correct agent and model assignments per phase.
SKILL.mdUpdated Apr 24, 2026