idea

@idea - Requirements Gathering with Progressive Disclosure

Deep interviewing to capture comprehensive feature requirements using progressive disclosure (3-question cycles). Creates markdown spec, optionally creates Beads task.

---

EXECUTE THIS NOW

When user invokes @idea "feature description":

Step 1: Read Context

Read existing project files to understand context:

• PRODUCT_VISION.md - Align with project goals
• docs/specs/**/* - Similar features

Step 2: Progressive Interview (3-Question Cycles)

Question Target:

• Minimum: 12 questions (bounded exploration)
• Maximum: 27 questions (deep analysis)
• Average: 18-20 questions per feature

3-Question Cycles:

1. Ask 3 focused questions
2. Offer trigger point after each cycle
3. User chooses: continue / deep design / skip to @design

Cycle 1 - Vision (3 questions):

• What is the core mission of this feature?
• How does this align with PRODUCT_VISION.md?
• Who are the primary users?

TRIGGER POINT (after each cycle):

• Continue (more questions)
• Deep design (jump to @design with architectural exploration)
• Skip to @design (move to workstream decomposition)

Cycle 2 - Problem & Users (3 questions):

• What problem does this solve?
• What are the user pain points?
• What happens if we don't build this?

Cycle 3 - Technical Approach (3 questions):

• Storage/data requirements?
• Failure modes to handle?
• Integration points?

Cycle 4 - UI/UX & Quality (3 questions):

• UI/UX requirements?
• Performance targets?
• Security considerations?

Cycle 5 - Testing & Edge Cases (3 questions):

• Testing strategy?
• Edge cases to handle?
• Success metrics?

Step 3: TMI Detection

If user provides extensive detail upfront:

• "detailed spec", "full implementation", "complete architecture"
• User writes >500 characters in initial prompt

Offer shortcuts:

• Continue with targeted questions (recommended)
• Skip to @design with detailed spec
• Use --quiet mode for minimal questions