plan-review

Evaluate implementation plans for soundness and compatibility with existing infrastructure.

62|2|Updated May 29, 2026
One-click install
npx skills add https://github.com/lucasfcosta/backpressured --skill plan-review-lucasfcosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-review
Source: https://github.com/lucasfcosta/backpressured/tree/main/skills/plan-review
Command: npx skills add https://github.com/lucasfcosta/backpressured --skill plan-review-lucasfcosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews lightweight implementation plans during backpressured development. Use when a backpressured loop's Phase 1 reviewer subagent is judging whether a lightweight implementation plan's approach/architecture is sound before any code is written — approving it or sending it back with approach-level concerns.

Core Features & Use Cases

  • Evaluate load-bearing decisions and pinned risks to ensure sound architecture.
  • Ensure alignment with existing infra and avoid unnecessary reinvention.
  • Guide teams toward simplest viable solution and prevent scope creep.

Quick Start

Provide a structured plan review by listing two concrete load-bearing concerns and a recommended corrective action.

Frequently Asked Questions about plan-review

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

FAQPage Schema
How do I review a software architecture plan before coding begins?

Evaluate load-bearing decisions and pinned risks to ensure sound architecture before coding. This approach prevents unnecessary reinvention and scope creep by guiding teams toward the simplest viable solution during the plan review phase.

What is plan soundness in backpressured software development?

Plan soundness in backpressured development means an implementation plan has acceptable risks and aligns with existing infrastructure. Reviewers codify criteria to approve lightweight architectures or send them back with approach-level concerns before code is written.

When should I send back an implementation plan during a risk assessment?

Send back an implementation plan during a risk assessment when it contains irreversible or expensive choices. Returning the plan with approach-level concerns prevents over-engineering and ensures alignment with existing infra before coding starts.

How do I prevent over-engineering when reviewing lightweight architectures?

Prevent over-engineering in lightweight architectures by codifying plan soundness criteria and evaluating load-bearing decisions. This ensures teams adopt the simplest viable solution and avoid unnecessary reinvention during the review process.

Can I use this plan review process for existing infrastructure compatibility checks?

Yes, you can use plan review for existing infrastructure compatibility checks. The process assesses whether a lightweight implementation plan aligns with current infra and evaluates load-bearing decisions to avoid unnecessary reinvention.