feasibility-reviewer

Detect architecture conflicts, dependency gaps, and migration risks in planning documents.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill feasibility-reviewer-andreicr1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feasibility-reviewer
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/feasibility-reviewer
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill feasibility-reviewer-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate planning documents against existing code, services, and infrastructure to catch architecture conflicts, dependency gaps, migration risks, and implementability issues before coding begins.

Core Features & Use Cases

  • Architecture reality checks: ensures proposed approaches align with the stack and existing patterns.
  • Shadow path tracing: identifies happy, nil, empty, and error data flows for new integrations.
  • Dependency & migration assessment: catalogs external dependencies and concrete migration steps.
  • Implementability readiness: verifies concrete interfaces, file paths, and error handling to start work immediately.

Quick Start

Review a planning document and run feasibility-reviewer to surface actionable architectural and implementation risks before coding begins.

Frequently Asked Questions about feasibility-reviewer

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

FAQPage Schema
How do I check if a technical architecture plan is feasible before coding?

Architecture reality checks validate proposed technical approaches by enforcing concrete checks against existing code, data flows, and external dependencies. This ensures new architectural plans align with the current stack and existing patterns before implementation begins.

What is shadow path tracing for data flow integration?

Shadow path tracing identifies happy, nil, empty, and error data flows for new integrations within an architecture. It enforces concrete checks to ensure proposed technical approaches handle all data states and edge cases safely across existing components.

How do I assess migration risks and external dependencies in a project proposal?

Assess migration risks by cataloging external dependencies and verifying concrete migration steps within planning documents. This dependency and migration assessment enforces concrete checks to guide actionable improvements and ensure migration safety before coding begins.

Does this feasibility review work for existing codebase and infrastructure contexts?

Yes, feasibility review applies to architectural plans and project proposals within a codebase and infrastructure context. It surfaces risks across existing components, data flows, and external dependencies to validate implementability readiness.

What is implementability readiness in architectural planning?

Implementability readiness verifies concrete interfaces, file paths, and error handling exist to start work immediately. It enforces concrete checks within planning documents to ensure proposed technical approaches are ready for implementation without blocking gaps.