plan-founder-review

Engineering plan validation requires reading the plan and companion JSON, verifying file paths exist, and checking consistency between Markdown and JSON against the actual codebase. This skill performs that founder review by comparing architecture, dependencies, and prerequisites to deliver a concrete verdict before execution.

A plan feasibility review checks architecture alignment, risk coverage, scope, prerequisites, contracts, and test strategy against the actual codebase. It verifies that file paths and dependencies exist and are consistent between Markdown and JSON plan files to prevent costly implementation missteps.

Checking file paths and dependencies involves comparing the plan's Markdown and companion JSON against the actual codebase. This skill verifies that specified file paths exist, validates dependencies and prerequisites, and checks Markdown-JSON consistency to produce a concrete plan verdict.

The plan review skill reads both the plan Markdown and a companion JSON file to verify consistency between them, but also independently validates file paths, dependencies, and architecture against the actual codebase. It enforces reading the plan thoroughly and delivers a verdict with actionable recommendations regardless of format gaps.

Enforcing a plan quality gate requires a rigorous founder review that challenges scope, architecture, prerequisites, contracts, and test strategy against codebase reality. This skill produces a verdict with concrete actionable recommendations after verifying file paths and dependencies, upholding plan quality before execution.

Reviewing engineering plans for risk and test coverage before coding prevents costly implementation missteps by identifying architectural gaps, missing prerequisites, and inadequate test strategy early. This skill scrutinizes risk assessment and scope alignment with the actual codebase, delivering a verdict with concrete recommendations.