nolantait/executing-plans
config/opencode/skills/executing-plans/SKILL.md
Use when you have a written implementation plan to execute
$ install --global
skillsauthnpx skillsauth add nolantait/dotfiles 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 15, 2026, 10:08 AM4.4s1 file scanned
SKILL.md
- name:
- executing-plans
- description:
- Use when you have a written implementation plan to execute
Executing Plans
Overview
Load plan, review critically, execute tasks in batches, report for review between batches. For Rails projects, three-stage review after each batch: spec compliance, Rails conventions, code quality.
Core principle: Batch execution with checkpoints for architect review.
Announce at start: "I'm using the executing-plans skill to implement this plan."
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 Batch
Default: First 3 tasks
For each task:
- Mark as in_progress
- Follow each step exactly (plan has bite-sized steps)
- Run verifications as specified
- Mark as completed
Rails Projects - MANDATORY
For Rails projects, load ALL convention skills BEFORE executing any task:
rails-controller-conventions
rails-model-conventions
rails-view-conventions
rails-policy-conventions
rails-job-conventions
rails-migration-conventions
rails-stimulus-conventions
rails-testing-conventions
After each batch, add Rails conventions check:
- Spec compliance (does code match plan?)
- Rails conventions (does code follow project conventions?)
- Code quality (is code well-structured?)
| Rationalization | Reality | |-----------------|---------| | "I already know Rails conventions" | These are PROJECT conventions. Load them. | | "Plan already covers conventions" | Plan is architecture. Skills are implementation. | | "Batch is small, conventions don't matter" | Small violations compound. Check every batch. |
Step 3: Report
When batch complete:
- Show what was implemented
- Show verification output
- For Rails projects: Note any convention considerations
- Say: "Ready for feedback."
Step 4: Continue
Based on feedback:
- Apply changes if needed
- Execute next batch
- Repeat until complete
Step 5: 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 mid-batch (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
- For Rails projects: Load ALL convention skills before first task
- Between batches: just report and wait
- Stop when blocked, don't guess
- Never start implementation on main/master branch without explicit user consent
Related Skills
nolantait/test-driven-development
development
VerifiedTrustedCommunity
Use when implementing any feature or bugfix, before writing implementation code
1SKILL.mdUpdated Apr 9, 2026
nolantait/dispatching-parallel-agents
testing
VerifiedTrustedCommunity
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
1SKILL.mdUpdated Apr 9, 2026
nolantait/ask-questions-if-underspecified
testing
VerifiedTrustedCommunity
Clarify requirements before implementing. Use when serious doubts arise.
1SKILL.mdUpdated Apr 9, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026