Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
Reviews an externally-authored implementation plan for quality, VGV conventions, and scope.
Install Plan Technical Review
$ npx skills add VeryGoodOpenSource/vgv-wingspan --skill plan-technical-review -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install VeryGoodOpenSource/vgv-wingspan plan-technical-review --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/VeryGoodOpenSource/vgv-wingspan.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/plan-technical-review .claude/skills/plan-technical-review && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "plan-technical-review" agent skill from https://github.com/VeryGoodOpenSource/vgv-wingspan/tree/main/skills/plan-technical-review into .claude/skills/plan-technical-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-technical-review", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/VeryGoodOpenSource/vgv-wingspan/tree/main/skills/plan-technical-reviewType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add VeryGoodOpenSource/vgv-wingspan --skill plan-technical-review -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install VeryGoodOpenSource/vgv-wingspan plan-technical-review --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VeryGoodOpenSource/vgv-wingspan.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/plan-technical-review .agents/skills/plan-technical-review && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "plan-technical-review" agent skill from https://github.com/VeryGoodOpenSource/vgv-wingspan/tree/main/skills/plan-technical-review into .agents/skills/plan-technical-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-technical-review", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add VeryGoodOpenSource/vgv-wingspan --skill plan-technical-review -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install VeryGoodOpenSource/vgv-wingspan plan-technical-review --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VeryGoodOpenSource/vgv-wingspan.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/plan-technical-review .cursor/skills/plan-technical-review && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "plan-technical-review" agent skill from https://github.com/VeryGoodOpenSource/vgv-wingspan/tree/main/skills/plan-technical-review into .cursor/skills/plan-technical-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-technical-review", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/VeryGoodOpenSource/vgv-wingspan.git --path skills/plan-technical-review--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add VeryGoodOpenSource/vgv-wingspan --skill plan-technical-review -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install VeryGoodOpenSource/vgv-wingspan plan-technical-review --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VeryGoodOpenSource/vgv-wingspan.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/plan-technical-review .gemini/skills/plan-technical-review && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "plan-technical-review" agent skill from https://github.com/VeryGoodOpenSource/vgv-wingspan/tree/main/skills/plan-technical-review into .gemini/skills/plan-technical-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-technical-review", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install VeryGoodOpenSource/vgv-wingspan plan-technical-reviewInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add VeryGoodOpenSource/vgv-wingspan --skill plan-technical-review -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/VeryGoodOpenSource/vgv-wingspan.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/plan-technical-review .github/skills/plan-technical-review && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "plan-technical-review" agent skill from https://github.com/VeryGoodOpenSource/vgv-wingspan/tree/main/skills/plan-technical-review into .github/skills/plan-technical-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-technical-review", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add VeryGoodOpenSource/vgv-wingspan --skill plan-technical-review -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install VeryGoodOpenSource/vgv-wingspan plan-technical-review --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VeryGoodOpenSource/vgv-wingspan.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/plan-technical-review .opencode/skills/plan-technical-review && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "plan-technical-review" agent skill from https://github.com/VeryGoodOpenSource/vgv-wingspan/tree/main/skills/plan-technical-review into .opencode/skills/plan-technical-review/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "plan-technical-review", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
plan-technical-review- GitHub stars
- 108
- Token cost
- ~479 tokens
- SKILL.md length
- 194 words
- Files
- 3 (incl. references)
- Skills in repo
- 11
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reviews an externally-authored implementation plan for quality, VGV conventions, and scope.
- Works in 4 steps: Clear context and build (Recommended):… → Start building: execute the plan with… → Refine the plan: improve the plan based… → …
- Tasks that involve Planning
- SKILL.md covers Review and Handoff
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Plan Technical Review is an agent skill from VeryGoodOpenSource/vgv-wingspan. Reviews an externally-authored implementation plan for quality, VGV conventions, and scope. Plans created by /plan are already reviewed during creation.
Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/clear-context-handoff.md` and `references/plan-review.md`). Compatibility notes: Designed for Claude Code (or similar products with agent support)
It sits in Agent Workflows, covering Planning. The repository describes itself as: AI-assisted workflows that follow Very Good Ventures best practices. It pairs perfectly with our Very Good AI Flutter Plugin. The licence is MIT.
When your agent uses it
- Tasks that involve Planning
Example prompts
- “Use the plan-technical-review skill to review an externally-authored implementation plan for quality, VGV conventions, and scope”
- “/plan-technical-review”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code (or similar products with agent support)
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Clear context and build (Recommended): clear context for a fresh start, then build
- Start building: execute the plan with /build
- Refine the plan: improve the plan based on review findings
- Done for now: review complete
What it can do on your machine
Read from SKILL.md and the folder at commit 19e0695. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Designed for Claude Code (or similar products with agent support)
From compatibility in the SKILL.md frontmatter.
Context cost
Plan Technical Review loads about 479 tokens when it runs, and up to ~501 if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 194 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from VeryGoodOpenSource/vgv-wingspan at commit 19e0695, republished under its MIT licence (© VeryGoodOpenSource). 194 words, ~479 tokens.
Download SKILL.mdSave it as
.claude/skills/plan-technical-review/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- plan-technical-review
- description
- Reviews an externally-authored implementation plan for quality, VGV conventions, and scope. Plans created by /plan are already reviewed during creation.
- compatibility
- Designed for Claude Code (or similar products with agent support)
- user-invocable
- true
- when_to_use
- Use to review a plan you did not create with /plan — a hand-written plan or one from another tool. Triggers on "review the plan", "is this plan ready"…
- argument-hint
- path to plan file
- effort
- high
Plan technical review
Review a plan that was not created by /plan. /plan runs this same review inline during
creation, so use this skill for externally-authored plans — hand-written, from another tool,
or from a teammate.
Plan file: $ARGUMENTS (if empty, ask the user for the plan path or pick the most recent file under docs/plan/).
Review
Follow the plan review procedure with <PLAN_PATH> set to the
plan file. It runs the simplicity, VGV, and scope-splitting agents in parallel, applies their
findings to the plan inline, and resolves any scope-splitting recommendation.
Handoff
After the review completes, use AskUserQuestion to present next steps:
Question: "Technical review complete! What would you like to do next?"
Options:
- Clear context and build (Recommended): clear context for a fresh start, then build
- Start building: execute the plan with
/build - Refine the plan: improve the plan based on review findings
- Done for now: review complete
If the user selects "Clear context and build" → Follow the clear context handoff for /build with the actual plan file path. Then stop.
When invoked by another skill, return control to the caller after the review completes — do not present handoff options.
© VeryGoodOpenSource, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files (references) in skills/plan-technical-review of VeryGoodOpenSource/vgv-wingspan.
- SKILL.md
- references/clear-context-handoff.md
- references/plan-review.md
Open the folder on GitHubat commit 19e0695
Compare with similar skills
Plan Technical Review next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Plan Technical Review this skillVeryGoodOpenSource/vgv-wingspan | 108 | — | ~479 | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Interview Meaddyosmani/agent-skills | 102k | 6 repos | ~3.8k | Automated safety check: Pass | MIT | |
| OpenSpec Guided OnboardingFission-AI/OpenSpec | 71k | 1 repos | ~4.5k | Automated safety check: Pass | MIT | |
| Writing Plansgeeksblabla/stateofdev.ma | 163 | 56 repos | ~661 | Automated safety check: Pass | None | |
| Subagent Driven DevelopmentAsvarox/allkaraoke | 261 | 37 repos | ~1.2k | Automated safety check: Pass | None |
Similar skills
Interview Me
addyosmani/agent-skills
Asks one question at a time, each with a best guess attached, until the agent is about 95 percent sure what you really want, before any plan, spec or code.
OpenSpec Guided Onboarding
Fission-AI/OpenSpec
Walks you through a complete OpenSpec workflow cycle with narration while doing real work in your codebase.
Writing Plans
geeksblabla/stateofdev.ma
A skill your agent uses when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file…
Subagent Driven Development
Asvarox/allkaraoke
A skill your agent uses when executing implementation plans with independent tasks in the current session
Planning With Files
jd-opensource/JoySafeter
Implements Manus-style file-based planning for complex tasks.
More from VeryGoodOpenSource/vgv-wingspan
All 11 skills in this repoOn-Demand Code Review
VeryGoodOpenSource/vgv-wingspan
Runs parallel review agents over a branch, chosen paths or a whole project and merges their findings into one numbered report you can act on by id.
Git Rebase onto Base Branch
VeryGoodOpenSource/vgv-wingspan
Rebases the current feature branch onto the latest main, master or develop, stashing uncommitted work first and aborting cleanly if conflicts appear.
Feature Brainstorm
VeryGoodOpenSource/vgv-wingspan
Clarifies what to build before how, by asking one question at a time about a feature idea and then handing the result on to planning.
Create Pull Request
VeryGoodOpenSource/vgv-wingspan
Stages, commits, pushes and opens a pull request with a Conventional Commits message, after running the project's checks unless told to skip them.
Post-Incident Debrief
VeryGoodOpenSource/vgv-wingspan
Produces a blameless post-incident debrief with timeline, root cause and follow-up actions after an outage, failed release or significant bug, while details are fresh.
Targeted Emergency Bug Fix
VeryGoodOpenSource/vgv-wingspan
Applies a minimal fix to an emergency bug through triage, root-cause location, a hotfix branch and a blast-radius check, with tests and review still required.
Related
Categories
Questions about Plan Technical Review
What does Plan Technical Review do?
Reviews an externally-authored implementation plan for quality, VGV conventions, and scope. Plan Technical Review is an agent skill from VeryGoodOpenSource/vgv-wingspan. Reviews an externally-authored implementation plan for quality, VGV conventions, and scope.
When should I use Plan Technical Review?
Plan Technical Review fits situations like: tasks that involve Planning.
How do I install Plan Technical Review in Claude Code?
Run `npx skills add VeryGoodOpenSource/vgv-wingspan --skill plan-technical-review -a claude-code`. Or copy the skill folder (skills/plan-technical-review in VeryGoodOpenSource/vgv-wingspan) into .claude/skills/plan-technical-review in your project. Claude Code loads it when a task matches its description.
How do I install Plan Technical Review in Codex?
Run `npx skills add VeryGoodOpenSource/vgv-wingspan --skill plan-technical-review -a codex`. Or copy the skill folder (skills/plan-technical-review in VeryGoodOpenSource/vgv-wingspan) into .agents/skills/plan-technical-review in your project. Codex loads it when a task matches its description.
Can I use Plan Technical Review in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add VeryGoodOpenSource/vgv-wingspan --skill plan-technical-review -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/plan-technical-review, .gemini/skills/plan-technical-review, .github/skills/plan-technical-review and .opencode/skills/plan-technical-review in your project.
What does Plan Technical Review need to run?
SKILL.md names no scripts, command-line tools or credentials: Plan Technical Review is instructions for the agent only. Compatibility (from SKILL.md): Designed for Claude Code (or similar products with agent support).
Does Plan Technical Review access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Plan Technical Review safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Plan Technical Review use?
Plan Technical Review is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Plan Technical Review use?
About 479 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 22 tokens, read only when the agent opens those files.
What are the alternatives to Plan Technical Review?
Skills that share tags, products or a category with Plan Technical Review: Executing Plans Inline (obra/superpowers, 296k stars), Interview Me (addyosmani/agent-skills, 102k stars), OpenSpec Guided Onboarding (Fission-AI/OpenSpec, 71k stars) and Writing Plans (geeksblabla/stateofdev.ma, 163 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Plan Technical Review?
VeryGoodOpenSource (a GitHub organization) maintains it in VeryGoodOpenSource/vgv-wingspan, which has 108 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on September 30, 2026.
Source: VeryGoodOpenSource/vgv-wingspan on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.