feasibility-reviewer

Evaluate technical plans for implementation blockers in brownfield codebases.

1|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/ybbms777/compound-engineering --skill feasibility-reviewer-ybbms777
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feasibility-reviewer
Source: https://github.com/ybbms777/compound-engineering/tree/main/skills/agent-feasibility-reviewer
Command: npx skills add https://github.com/ybbms777/compound-engineering --skill feasibility-reviewer-ybbms777

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technical plans often appear complete on paper but contain hidden architecture conflicts, unacknowledged dependencies, missing edge case handling, or unsafe migration paths that only surface during implementation, leading to wasted development time, rework, and project delays.

Core Features & Use Cases

  • Multi-dimensional feasibility checks: Validates plans against existing codebase infrastructure, traces shadow paths for all data flows, assesses dependency completeness, and evaluates migration safety.
  • Confidence-calibrated findings: Flags issues with clear confidence levels (high/moderate) so teams can prioritize critical blockers over minor concerns.
  • Use Case: When a team submits a plan for a new user notification feature, this skill identifies if the plan ignores existing notification service limits, misses error handling for third-party SMS API failures, and lacks rollback strategy for the feature flag migration.

Quick Start

Use the feasibility-reviewer skill to evaluate the attached technical plan for the new user notification feature and surface any blocking feasibility gaps before development begins.

Frequently Asked Questions about feasibility-reviewer

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

FAQPage Schema
What is a feasibility review for a technical plan?

A feasibility review evaluates proposed technical approaches in planning documents to identify blockers preventing successful implementation. It validates architecture alignment, dependency completeness, edge case coverage, migration safety, and implementability before development begins.

How do I check if a system migration plan is safe for a brownfield codebase?

Check migration safety by tracing shadow paths for all data flows and assessing dependency completeness against existing infrastructure. This identifies missing rollback strategies and hidden architecture conflicts before development to prevent wasted time and rework.

Does this feasibility review detect missing edge case handling in new feature plans?

Yes, the feasibility review traces edge case coverage to detect missing error handling for external dependencies. It flags these gaps with high or moderate confidence levels so teams can prioritize critical blockers over minor concerns.

What's the best way to validate architecture alignment before development kickoff?

The best way to validate architecture alignment is running multi-dimensional feasibility checks against existing codebase infrastructure. This surfaces unacknowledged dependencies and unsafe migration paths early, preventing project delays caused by hidden conflicts during implementation.

Why does a technical plan fail during implementation despite looking complete?

Technical plans fail during implementation because they contain hidden architecture conflicts, unacknowledged dependencies, missing edge case handling, or unsafe migration paths that only surface during coding, leading to wasted development time and rework.