plan-review

Validate software implementation plans against design specifications and risk factors.

Updated Feb 17, 2026

Search Tags:#code review #implementation plan #quality gate #risk assessment #development process #plan review

Ready to run

npx skills add https://github.com/mscipio/bilt-transactions-export --skill plan-review-mscipio

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/mscipio/bilt-transactions-export/tree/main/.opencode/skills/plan-review
Command: npx skills add https://github.com/mscipio/bilt-transactions-export --skill plan-review-mscipio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill acts as a critical quality gate, identifying flaws in implementation plans before any code is written, thereby preventing wasted development effort and rework.

Core Features & Use Cases

Comprehensive Checklist: Covers spec compliance, completeness, task granularity, feasibility, edge cases, and risk assessment.
Iterative Feedback: Provides structured feedback to improve plans through a defined revision cycle.
Use Case: After a writing-plans skill generates a plan for a new authentication feature, this skill rigorously reviews it for missing steps, unclear tasks, or overlooked security risks before development begins.

Quick Start

Review the implementation plan located at '.context/plans/2026-02-21-auth-plan.md' for the 'User Authentication' feature.

Frequently Asked Questions about plan-review

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

FAQPage Schema

How do I review an implementation plan before coding starts?▼

Reviewing an implementation plan involves validating it against design specifications, completeness, feasibility, edge cases, and risk factors to serve as a mandatory quality gate before code execution begins.

What is a quality gate in the software development process?▼

A quality gate in the software development process is a mandatory validation step that checks implementation plans for spec compliance, edge cases, and risks, preventing wasted development effort before code execution begins.

How do I assess risks and edge cases in a software implementation plan?▼

Assess risks and edge cases in a software implementation plan by using a comprehensive checklist that validates spec compliance, task granularity, and feasibility, providing structured feedback through defined revision cycles.

How many revision cycles are allowed before escalating a flawed implementation plan?▼

A maximum of three revision cycles are allowed before escalation. During these cycles, structured feedback is provided to iteratively improve the implementation plan and address any identified flaws.

Does this plan review process work independently of other development tools?▼

Yes, the plan review process operates independently with no external dependencies. It rigorously evaluates generated plans for missing steps, unclear tasks, or overlooked security risks before development begins.