llms: Skill for Claude Code

Discovery — Phase 0 Validation Gate

Structured Discovery & Validation before committing to a feature. Prevents building unvalidated ideas by gating entry into the story and design pipeline with four sequential modes.

Usage

/discovery                   # Show overview of all 4 modes
/discovery problem           # Problem framing: who has it, how urgent, what evidence
/discovery competitive       # Competitive landscape: what exists, differentiators, moat
/discovery feasibility       # Feasibility: technical, economic, time constraints
/discovery checkpoint        # Go/no-go gate: 5-criteria verdict before /story create

Workflow

Step 1: Determine Mode

Parse $ARGUMENTS for explicit mode. If no arguments provided, show overview:

no args         → read templates/overview.md
problem         → read templates/problem/summary.md
competitive     → read templates/competitive/summary.md
feasibility     → read templates/feasibility/summary.md
checkpoint      → read templates/checkpoint/summary.md
<anything else> → show usage error + list valid modes + read templates/overview.md

Step 2: Present Guidance (Progressive Disclosure)

Level 1 — Summary (default, ~20 lines): Read and present the summary template. This is the entry point — frames the questions to answer.

Level 2 — Patterns (on request, ~60 lines): When the user asks for more depth, "show me patterns", "how do I score this", or "give me examples" — read the patterns template.

Level 3 — Full Analysis (on request): No template — dive into specific questions with the user based on context provided.

Step 3: Run Modes Sequentially

Recommended sequence: problem → competitive → feasibility → checkpoint

Each mode builds on the previous:

• problem → frames who, what, and why
• competitive → validates market gap
• feasibility → validates buildability
• checkpoint → synthesizes all three into a go/no-go verdict

You can run individual modes out of order when the user has already done partial research.