void-plan-review

Critique a written plan through CEO, Eng, Design, and DevEx lenses before implementation.

Updated May 29, 2026
One-click install
npx skills add https://github.com/voidcorp-core/void-harness --skill void-plan-review-voidcorp-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: void-plan-review
Source: https://github.com/voidcorp-core/void-harness/tree/main/packages/core/skills/void-plan-review
Command: npx skills add https://github.com/voidcorp-core/void-harness --skill void-plan-review-voidcorp-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Plans often reach implementation with unchallenged premises, missing test coverage, incomplete UI states, or poor developer experience, and fixing those gaps in code review costs far more than catching them in the plan. This Skill reviews an already-written plan from up to four expert lenses and surfaces findings as decisions before the plan becomes tickets. ## Core Features & Use Cases - Four review lenses: CEO (premise, ambition, mandatory alternatives, scope modes), Eng (architecture, failure modes, deep test-coverage trace, performance), Design (information architecture, interaction states, AI-slop risk, accessibility), and DevEx (time-to-first-value, error messages, docs, upgrade path). - Orchestrated all mode: Runs applicable lenses in a fixed CEO → Design → Eng → DX order, auto-decides only mechanical findings, escalates taste calls, and synthesizes cross-lens themes into one final gate. - Findings become tasks: Each lens appends a P1/P2/P3 Implementation Tasks list to the plan and returns a CLEARED or NOT CLEARED verdict without rewriting the plan itself. - Use Case: Before converting a spec in docs/plans/ into tickets, run the Eng lens to trace every branch and error path, then run all to get a deduplicated task list and a ship/no-ship verdict. ## Quick Start Ask the agent to review the plan in docs/plans with the void-plan-review skill using all lenses and append the findings as an implementation task list.

Frequently Asked Questions about void-plan-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a plan before implementation with an AI agent?

Invoke the skill on a plan document in docs/specs or docs/plans and pick one lens or the orchestrated all mode. It surfaces findings one decision at a time, appends a P1/P2/P3 task list, and returns a CLEARED or NOT CLEARED verdict.

What is the difference between plan review and code review?

Plan review critiques a written plan before any code exists, checking premise, architecture, test coverage, design states, and developer experience. Code review examines an actual diff, so plan review catches gaps an order of magnitude cheaper.

When should I use the CEO lens versus the Eng lens?

Use the CEO lens to challenge the premise, ambition, and alternatives of a plan, including scope modes like EXPANSION or REDUCTION. Use the Eng lens as the gating check for architecture soundness, failure modes, and test coverage.

Does the plan review skill modify the plan document?

No, it never rewrites or restructures the plan. It only appends an Implementation Tasks list with severities, and the plan author folds the fixes in through the separate plan-authoring skill.

When is the Design or DevEx lens skipped?

Both lenses are scope-gated. The Design lens is skipped when the plan has no UI surface, and the DevEx lens is skipped when the plan exposes no API, CLI, SDK, library, or docs surface.