From vgv-wingspan
Reviews an externally-authored implementation plan for quality, VGV conventions, and scope. Use for plans not created by /plan.
How this skill is triggered — by the user, by Claude, or both
Slash command
/vgv-wingspan:plan-technical-review path to plan fileWhen 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", "validate my plan", or "check the plan".
path to plan fileThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Review a plan that was not created by `/plan`. `/plan` runs this same review inline during
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/).
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.
After the review completes, use AskUserQuestion to present next steps:
Question: "Technical review complete! What would you like to do next?"
Options:
/buildIf 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.
npx claudepluginhub verygoodopensource/very-good-claude-code-marketplace --plugin vgv-wingspanReviews implementation plans for completeness, feasibility, risks, scope adherence, and alignment with codebase patterns. Provides structured feedback with strengths, concerns, gaps, and improvements before execution.
Orchestrates parallel architecture and experience reviews of implementation plans, scores findings across dimensions like data flow and UX, consolidates ranked fixes for user approval and auto-application. Use after planning, before non-trivial coding.
Reviews implementation plans for flaws by verifying claims against the codebase and getting feedback from external AI consultants. Can be invoked after writing plans or when asked to review a plan.