n4m3z/ExecutePlan
skills/ExecutePlan/SKILL.md
Execute an implementation plan inline — task by task in a single session. USE WHEN executing plan, run plan, implement plan, inline execution.
$ install --global
skillsauthnpx skillsauth add n4m3z/forge-core ExecutePlanInstall 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: May 14, 2026, 6:08 AM125.3s2 files scanned
SKILL.md
- name:
- ExecutePlan
- version:
- 0.1.0
- description:
- Execute an implementation plan inline — task by task in a single session. USE WHEN executing plan, run plan, implement plan, inline execution.
ExecutePlan
Execute a WritePlan output in the current session, one task at a time. This is the sequential alternative to DeveloperSprint (parallel agents). Use ExecutePlan for smaller plans or when tasks have sequential dependencies.
- Load the plan — read the plan file from
docs/plans/ - Critical review — before starting, check: are tasks ordered correctly? Are dependencies satisfied? Any gaps? If issues found, fix the plan first or ask the user.
- Set up workspace — use a git worktree if the plan modifies existing code
- Execute task by task:
- Read the task specification
- Implement exactly what the task says
- Run the verification step specified in the task
- Invoke VerifyCompletion before marking the task done
- Move to the next task only after the current one passes
- Handle blockers — if stuck, stop and ask the user. Never guess past a blocker.
- Final verification — after all tasks, run the full build + test suite
- Report — summarize what was done, what was skipped, what needs follow-up
Red Flags
| Thought | Reality | | ------------------------------------------------- | ------------------------------------------------------------ | | "I'll do tasks 3 and 4 together, they're related" | One task at a time. Verify each before moving on. | | "This task is wrong, let me improvise" | Stop. Fix the plan or ask the user. Don't freelance. | | "I can skip verification on this one" | No. VerifyCompletion on every task. | | "I'm blocked but I can probably work around it" | Stop and ask. Workarounds create hidden dependencies. | | "Let me also fix this while I'm here" | Scope creep. Do what the plan says, nothing more. | | "The plan is mostly done, close enough" | Partially executed plans are worse than unstarted ones. |
Constraints
- One task at a time — never batch or skip ahead
- Verify each task before proceeding to the next
- Stop on blockers — ask the user, don't guess
- No scope expansion beyond the plan
- Use git worktrees when modifying existing code
- For plans with independent tracks, use DeveloperSprint instead
Sources
- https://github.com/obra/superpowers
Related Skills
n4m3z/Wtf
development
VerifiedTrustedCommunity
Reactive correction and root-cause fix. USE WHEN something went wrong, user is frustrated, demands a correction, says wtf, what the hell, why did you, that's wrong, this is broken, no not that, stop. Executes the immediate fix, then hunts the upstream artifact that caused it and creates a corrective change.
4SKILL.mdUpdated May 28, 2026
n4m3z/ResearchTopic
development
VerifiedTrustedCommunity
Decompose a research question into sub-queries, spawn parallel WebResearcher agents per angle, synthesize findings with citations and explicit confidence. USE WHEN the user asks to research, investigate, look online, look up, dig into, find sources, gather evidence, or survey what's known about a topic. Single-pass; for multi-round adversarial research use ResearchCouncil in forge-council.
4SKILL.mdUpdated May 27, 2026
n4m3z/WriteDocs
tools
VerifiedTrustedCommunity
Author project documentation that future humans (and AI sessions) actually read. Covers TLDRs for tools, READMEs, runbooks, journals. USE WHEN write documentation, create tldr, tool one-pager, document a cli, write readme, runbook, journal entry, capture knowledge about a tool, distill a session into reusable notes.
4SKILL.mdUpdated May 25, 2026
n4m3z/StagedReview
development
VerifiedTrustedCommunity
Review your own staged changes via a code-review TUI before triggering a commit. USE WHEN about to commit, walking through your own staged diff, self-reviewing before approval, tuicr, revdiff, git diff cached.
4SKILL.mdUpdated May 25, 2026