the-own-lab/execute-plan
skills/execute-plan/SKILL.md
Execute an implementation plan step by step with verification at each step. Use when implementing code from an approved plan.
development
Updated Apr 21, 2026
$ install --global
skillsauthnpx skillsauth add the-own-lab/Claude-company-of-one execute-planInstall 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 16, 2026, 10:04 PM10.7s1 file scanned
SKILL.md
- name:
- execute-plan
- description:
- Execute an implementation plan step by step with verification at each step. Use when implementing code from an approved plan.
Execute Plan
Execute an approved implementation plan with discipline and verification.
Process
-
Read the full plan before starting — Understand the complete picture before touching any code. Note dependencies between steps and the overall goal.
-
For each step:
- Read the step requirements carefully.
- Write the test first (TDD — see the
tddskill). - Implement the code to pass the test.
- Verify using the step's verification criteria.
- Commit the working step.
-
If a step is unclear — STOP and flag. Never guess at intent. Ask for clarification. Guessing leads to rework.
-
If a step fails verification — STOP and report. Do not proceed to the next step with a broken foundation. Report what failed and why.
Rules
- Follow the plan exactly. The plan was approved for a reason. If you disagree with the plan, raise it — do not silently deviate.
- Do not deviate from scope. If you notice something outside the plan that needs fixing, note it separately. Do not fix it now.
- Do not "improve" beyond the plan. No bonus features. No premature optimization. No "while I'm here" changes.
- One commit per step. Each step produces one atomic commit. This makes rollback and review straightforward.
Related Skills
the-own-lab/write-brief
documentation
VerifiedTrustedCommunity
Update BRIEF.md sections during a command run. Any skill that produces a brief-persisted artifact calls this to write it back.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/verify
development
VerifiedTrustedCommunity
Post-code check: run tests + confirm TODO acceptance items map to passing tests; applies a security lens but is not a separate scan.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/update-docs
documentation
VerifiedTrustedCommunity
Command post-step: write CHANGELOG + TODO once per command run. One call, not per-skill doc writes.
SKILL.mdUpdated Apr 22, 2026
the-own-lab/spec-writing
content-media
VerifiedTrustedCommunity
Author REQUIREMENTS.md + DESIGN.md + TODO.md for a feature. The three files are one contract; they ship together.
SKILL.mdUpdated Apr 22, 2026