docs/discovery/index.md

# Discovery

This directory contains discovery artifacts that validate *what* to build and capture *taste*.

## What is Discovery?

Discovery validates product ideas and captures user taste before detailed planning. It answers:
- What opportunity are we pursuing? (Opportunity Solution Tree)
- What problem are we solving? (PR/FAQ)
- What would DELIGHT users? (Taste capture)
- What would FRUSTRATE users? (Anti-patterns)
- What FEELING should users have? (North star)
- How does this compare to alternatives? (RICE/ICE prioritization)

## File Format

Each feature has two files:
- `{feature}.md` — Human-readable discovery doc with OST, PR/FAQ, taste
- `{feature}.json` — Machine-readable taste data for downstream skills

## Discovery Index

| Feature | Status | Date |
|---------|--------|------|
| *None yet* | | |

## Relationship to Other Docs

```
discovery/        →  Validate + Taste (OST, PR/FAQ)
    ↓
delivery-specs/   →  Engineering handoff (functional requirements)
    ↓
design-docs/      →  Technical approach (ADR-style)
    ↓
FEATURES.json     →  Links docs to implementation
    ↓
specs/            →  Implementation specs (autocode)
    ↓
learnings/        →  Knowledge extracted after completion
```

## Creating Discovery Docs

Use the `discovery` skill for structured discovery:

```
skill({ name: "discovery" })
```

The skill guides you through:
1. **Opportunity Solution Tree** — Outcome, opportunities, solutions
2. **PR/FAQ** — Headline, problem, solution, customer quote
3. **Taste interview** — Delights, frustrations, feeling, maturity
4. **Prioritization** — RICE/ICE scoring

## Integration with Autocode

The `autocode-implementation-planner` skill automatically reads the JSON file:
- `taste.delights` → Success criteria in implementation spec
- `taste.frustrations` → Anti-patterns to explicitly avoid
- `taste.feeling` → North star for implementation decisions
- `scope.out_of_scope` → Boundaries the implementation must respect