Skip to content
Skills Library
Programming · Review & audit

plan-technical-review

/plan-technical-review

Reviews an externally-authored implementation plan for quality, VGV conventions, and scope — a hand-written plan, or one from another tool or a teammate. Plans created by /plan are already reviewed during creation. Triggers on "review the plan", "is this plan ready", "validate my plan", or "check the plan".

Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Reviews an externally-authored implementation plan for quality, VGV conventions, and scope — a hand-written plan, or one from another tool or a teammate. Plans created by /plan are already reviewed during creation. Triggers on "review the plan", "is this plan ready", "validate my plan", or "check the plan".

Triggers from the description

review the planis this plan readyvalidate my plancheck the plan

Arguments

/plan-technical-review path to plan file
Original author description

Reviews an externally-authored implementation plan for quality, VGV conventions, and scope — a hand-written plan, or one from another tool or a teammate. Plans created by /plan are already reviewed during creation. Triggers on "review the plan", "is this plan ready", "validate my plan", or "check the plan".

How it works

  1. Review
  2. Handoff
  3. Important
  4. The handoff block
Original SKILL.md headings · 60 lines, 396 words
SKILL.md preview
---
name: plan-technical-review
user-invocable: true
description: Reviews an externally-authored implementation plan for quality, VGV conventions, and scope — a hand-written plan, or one from another tool or a teammate. Plans created by /plan are already reviewed during creation. Triggers on "review the plan", "is this plan ready", "validate my plan", or "check the plan".
argument-hint: path to plan file
effort: high
compatibility: Designed for Claude Code (or similar products with agent support)
---

# 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.

> **Every question in this skill goes through the AskUserQuestion tool.** When that tool is
> not available — another harness, or a non-interactive session — put the same question and
> the same options in your reply as a short numbered list, and stop there for the answer.
> Never answer a question on the user's behalf and carry on: a question the user never sees
> is not a question, and a step that waits on one is not optional.

**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](references/plan-review.md) 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:**

1. **Clear context and build (Recommended)**: clear context for a fresh start, then build
2. **Start building**: execute the plan with `/build`
3. **Refine the plan**: improve the plan based on review findings
4. **Done for now**: review complete

**If the user selects "Clear context and build"** → Follow the [clear context handoff](references/clear-context-handoff.md) 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.

## Important

## The handoff block

The handoff is the user's only instruction for picking the work up in a fresh session, so its
shape is fixed here as well as in the reference. Print exactly this and then **stop**,
substituting the next skill and the real document path:

```md
To continue with a fresh context, run:

/clear

Then start <NEXT_ACTION> with:

/<NEXT_SKILL> <DOC_PATH>
```

Print it even when the document cannot be read from here, and even when the reference file
cannot be read — a cleared context is a new session, and the skill that picks it up validates
the path. Withholding the block because a check failed strands the user mid-handoff.
Files in this package (3)
  • SKILL.md 3 KB
  • references/clear-context-handoff.md 1 KB
  • references/plan-review.md 1 KB

Versions

The database has no other skills named plan-technical-review.

Database snapshot: 13.11.2026 · package version 65726710634c (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100review-plan
    Use after writing implementation plans (superpowers:writing-plans output) or when the user says "review plan", "check my plan", "sanity check the plan", "validate plan", "review before executing". Also use before superpowers:executing-plans if a plan has not been reviewed yet.
  • 90sp-planning
    Use when the user asks for a concrete implementation plan for an agreed change before code is written.
  • 90plan-review
    Use when reviewing an implementation plan before coding or launching workers to check approach, scope, and repo-convention fit.
  • 85executing-plans
    Use when you have a written implementation plan to execute in a separate session with review checkpoints
  • 100review-plan
    Use when the user asks to review the plan, sanity-check the plan, vet the plan, evaluate the plan, "is this plan ready", feasibility check on a plan, "review-plan PATH", or when another skill (like implement-plan) requests pre-flight plan evaluation before execution. Do NOT use…
  • 100review-plan
    This skill should be used when the user asks to "review plan for security", "check plan for security issues", "security review of implementation plan", "audit the plan for vulnerabilities", or "check my plan before coding". Also triggers when the user mentions security in the…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.