discovery

@discovery - Product Discovery Gate

Validate before specifying. Answer "should we build this?" before "how should we build this?"

---

EXECUTE THIS NOW

When user invokes @discovery "feature description" or when @feature invokes it (unless --quick):

Phase 1: Roadmap Pre-Check

1. Extract 3-5 high-signal keywords from the feature description (nouns + domain verbs — NOT generic terms like "add", "update", "implement").
2. If memory search returns > 10 results, reduce to 2 most specific terms.

sdp memory stats   # warn if index > 24h old
sdp memory search "<keyword1> <keyword2> <keyword3>"

1. Analyze results for:

   • Features in ROADMAP.md covering same domain terms
   • Workstream files with matching Scope Files or goals
   • Existing docs/drafts/idea-*.md that cover similar territory

2. Present Overlap Report (HIGH and MEDIUM confidence only; log LOW to file):

   Found N potentially related items:
   [HIGH] Rework Loop — covers [summary]. Similarity reason: [1 sentence]
   [MEDIUM] 00-008-02 — touches [same module]. Overlap type: [data model / API / user flow]
   

3. User resolution (single question):

   • A) These are different — proceed to Phase 2
   • B) This extends existing workstream — incorporate and modify
   • C) This supersedes existing workstream — flag for later review (propose: set status to 'deferred')
   • D) Show me more detail before deciding

Gate: Proceed only after user resolves.

Mode --quiet: Phase 1 only, then stop. Output: overlap report only.

---

Phase 2: Signal Check (~30 seconds)

1. Ask 2 questions:

   • "What user problem does this solve and for whom?"
   • "Do you know of existing solutions (libraries, tools, competitors)?"

2. Run web search: "{feature_name} existing solutions 2026"

3. Route to track:

Condition	Track
User answers both confidently AND search finds ≥1 clear prior art	OBVIOUS
User answers but search shows competitive landscape	COMPETITIVE
User uncertain on Q1 OR search shows no clear prior art	NOVEL