discoverlisted

Capture feature ideas with structured questioning into a discovery staging area before they reach the backlog. Use when the user says 'capture idea', '/discover', '/discover refine D###', or wants to record a new request without committing to it yet. Sister skill: /promote (graduates the item into the backlog).
Maximumsoft-Co-LTD/claude-flightdeck · ★ 1 · AI & Automation · score 77

Install: claude install-skill Maximumsoft-Co-LTD/claude-flightdeck

# /discover — Structured Requirement Capture Capture raw ideas into `docs/spec/discovery.md` (index) + `docs/spec/discovery/D<###>-<slug>.md` (detail file). Discovery is the staging area — nothing reaches the backlog without `/promote`. ## Token budget (MANDATORY) - Never full-Read the backlog or sprint files — use Grep for the duplicate scan. - Read existing discovery detail files only when refining a specific D###. - Keep the interactive interview lean — short, targeted questions; don't dump exhaustive checklists on the user. ## Usage - `/discover` — interactive 3-stage interview - `/discover <title>` — quick raw capture (skip the interview) - `/discover refine D###` — fill gaps on an existing item - `/discover review D###` — readiness check (the same gate `/promote` will run) - `/discover show D###` / `/discover list` / `/discover drop D###` ## Interactive steps 1. **Stage 1 — Core**: title, problem statement, affected user roles, source of the request, affected components / services. 2. **Estimate complexity** — trivial/small → 3-4 follow-ups; medium → 5-8; large → 8-10. Don't over-ask small items. 3. **Stage 2 — Scope**: target behaviour, explicit non-goals, related features, cross-component impact (events, persistence, UI entry points). Ask which areas of the system will need to change. 4. **Stage 3 — Context**: urgency, technical constraints, deadlines, related discovery items. 5. **Allocate next D### ID** — `Grep` `docs/spec/discovery.md` for the highest ID and