OPC Board

Problem

Solo developers and one-person teams often lack a structured way to answer whether an idea is viable, buildable, and worth pursuing. This skill does not write a full business plan from scratch or make the final decision for the user. Instead, it turns a product idea, target user, business model, or launch channel into a clear, evidence-based feasibility review.

How It Works

The skill uses five advisors across five dimensions:
- Technical checks whether the project can be delivered independently.
- Growth checks whether the idea has a plausible growth path.
- Experience checks usability and delivery constraints.
- Business checks sustainability, including open-source or community maintenance models.
- Risk checks failure modes, compliance exposure, and operational constraints.

Each dimension is scored with sub-items using 0/1/2 values, then combined according to the deterministic scoring engine. Intake can reuse the bundled assets/intake-form.html; missing items are marked and scored conservatively. The output is a Markdown or HTML report that includes a scorecard, a Go/Conditional/No Go verdict, Pre-Mortem, MoSCoW, an OPC decision card, action items, and a disclaimer.

Boundaries

It fits indie SaaS, open-source projects, side projects, and experimental ideas. It is not a substitute for legal, financial, or medical compliance advice, and it cannot produce a valid score from only a product name without follow-up information. Non-commercial projects are scored with open-source or community maintenance assumptions rather than being forced into a revenue-based penalty.