plan-reviewer

Validate engineering implementation plans against structured review criteria.

2|Updated Jun 3, 2021

Search Tags:#documentation #validation #engineering #traceability #risk-assessment #quality-assurance #plan-review

Ready to run

npx skills add https://github.com/kalindudc/shell --skill plan-reviewer-kalindudc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-reviewer
Source: https://github.com/kalindudc/shell/tree/main/home/.config/opencode/skills/plan-reviewer
Command: npx skills add https://github.com/kalindudc/shell --skill plan-reviewer-kalindudc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan reviews ensure engineering implementations meet objectives, quality, and feasibility before proceeding to build.

Core Features & Use Cases

Structured ingestion of plan documents (High-Level Objective, Low-Level Tasks, Context) and automated checks against entry criteria.
Dimensional evaluation across Completeness, Correctness, Feasibility, Risk, Tradeoffs, Consistency, and Testability with actionable findings.
Use cases include architecture proposals, module roadmaps, deployment plans, and design reviews with formal approval recommendations.

Quick Start

Provide a structured plan review for a given plan document and return a formatted assessment with recommended actions.

Frequently Asked Questions about plan-reviewer

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

FAQPage Schema

How do I validate an engineering implementation plan before starting development?▼

Plan validation involves performing structured reviews to identify gaps across completeness, correctness, feasibility, risk, tradeoffs, consistency, and testability. You provide a plan document containing a High-Level Objective, Low-Level Tasks, Context, and Validation Gates for automated cross-checking of dependencies and constraints.

What should an architecture proposal or deployment roadmap include to pass a structured plan review?▼

A structured plan review requires your architecture proposal or deployment roadmap to include a High-Level Objective, Low-Level Tasks, Context, and Validation Gates. The review cross-checks referenced files, dependencies, and constraints to ensure engineering implementations meet quality and feasibility standards.

Can I use automated plan reviews for module roadmaps at early maturity levels?▼

Automated plan reviews are applicable to module roadmaps and design reviews at various maturity levels and project sizes. The process enforces the presence of required plan file sections and evaluates dimensional completeness to provide actionable findings and formal approval recommendations.

What is the best way to assess risks and tradeoffs in a technical design document?▼

Assessing risks and tradeoffs in a technical design document requires a dimensional evaluation covering Completeness, Correctness, Feasibility, Risk, Tradeoffs, Consistency, and Testability. This structured review approach returns a formatted assessment with recommended actions to resolve identified gaps.

Why does my engineering plan review fail during the automated checks against entry criteria?▼

Engineering plan reviews fail automated entry criteria checks when the plan file is missing required sections like a High-Level Objective, Low-Level Tasks, Context, or Validation Gates. The review also fails if it cannot cross-check referenced files, dependencies, and constraints within the document.

How do I perform a structured design review for a component plan with traceability requirements?▼

Performing a structured design review for a component plan requires ingesting the document and running dimensional evaluations for quality assurance and traceability. The review validates referenced files and dependencies, returning a formatted assessment with actionable findings and formal approval recommendations.