solo-validate
End-to-end startup idea validation using S.E.E.D. niche checks, STREAM 6-layer analysis, and Devil's Advocate inversion to generate PRDs.
Introduction
The solo-validate skill provides a rigorous framework for evaluating startup feasibility before committing resources. Designed for founders, product managers, and solo developers, this skill replaces optimistic bias with objective, data-driven validation. It forces a critical look at market viability, technical feasibility, and alignment with lean principles. By identifying 'kill' signals early, it prevents the common trap of building solutions for non-existent problems. This skill processes user ideas through a multi-stage funnel, incorporating knowledge base searches, manifest alignment, niche analysis, and adversarial testing.
-
S.E.E.D. Niche Check: Evaluates Searchability, Evidence of pain, Ease of MVP, and Demand potential.
-
STREAM 6-Layer Analysis: Breaks down the concept into Scope, Time, Resources, Execution, Architecture, and Market layers.
-
Devil's Advocate Inversion: Actively attempts to break the idea by simulating failures, reviewing dead startup pivots, and stress-testing unit economics.
-
Manifest Alignment: Checks the idea against nine core principles, such as privacy-first, one-pain-one-feature, and antifragile architecture.
-
PRD Generation: Produces a detailed Product Requirement Document with specific acceptance criteria if the idea passes initial gates.
-
Deep Research Integration: Connects with research.md files and MCP tools like kb_search, project_info, and web_search for evidence-based validation.
-
Input: Provide a raw startup idea or problem statement to trigger the validation workflow.
-
Prerequisites: Ideally paired with a knowledge base or existing research docs to increase accuracy.
-
Operational Constraints: Highly recommended to run this before any coding begins. If kill flags are triggered (e.g., media giant dominance, no evidence of pain), the skill will explicitly recommend stopping.
-
Usage Tip: If the system suggests a 'KILL', treat it as a signal to iterate on the premise rather than proceeding to build. Use this for 'go or kill' decisions, evaluating opportunities, or when deciding whether to pivot.
Repository Stats
- Stars
- 4,437
- Forks
- 1,203
- Open Issues
- 7
- Language
- Python
- Default Branch
- main
- Sync Status
- Idle
- Last Synced
- Apr 29, 2026, 12:35 PM