idea

Interview users to gather feature requirements and create Beads tasks.

19|Updated Dec 28, 2025
One-click install
npx skills add https://github.com/fall-out-bug/sdp --skill idea-fall-out-bug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: idea
Source: https://github.com/fall-out-bug/sdp/tree/main/.claude/skills/idea
Command: npx skills add https://github.com/fall-out-bug/sdp --skill idea-fall-out-bug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the initial phase of feature development by conducting deep, interactive interviews to gather comprehensive requirements, ensuring alignment with product vision before any design or coding begins.

Core Features & Use Cases

  • Interactive Requirements Gathering: Engages in a structured interview process to uncover details about a feature's mission, alignment with product vision, problem statement, technical approach, and potential tradeoffs.
  • Beads Task Creation: Automatically creates a task in the Beads task management system with a detailed description derived from the interview.
  • Intent File Generation: Produces a machine-readable JSON file (docs/intent/{task_id}.json) that captures the essence of the gathered requirements.
  • Use Case: When starting a new feature like "implementing a user notification system," you can use @idea to guide the AI through a series of questions that will result in a well-defined Beads task ready for the design phase.

Quick Start

Initiate requirements gathering for a new feature by running the idea skill with a brief description of the feature.

Frequently Asked Questions about idea

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I gather feature requirements interactively before starting development?

Gathering feature requirements interactively involves deep interviewing to capture mission, problem statements, and technical approaches, ensuring product vision alignment before design begins and generating structured outputs for subsequent development phases.

What is the best way to document feature definition tradeoffs during requirements gathering?

Documenting feature definition tradeoffs involves capturing technical compromises and problem statements during the interview process, recording them alongside the mission in human-readable task descriptions and machine-readable JSON intent files.

How do I create structured Beads tasks from a product vision interview?

Creating structured Beads tasks from a product vision interview happens automatically after deep questioning, deriving a detailed task description from gathered requirements and registering it directly within the Beads task management system.

Does the requirements gathering process generate machine-readable outputs for downstream phases?

Yes, the requirements gathering process generates a machine-readable JSON intent file at `docs/intent/{task_id}.json`, capturing the essence of gathered requirements to enable seamless handoff to subsequent development phases.

Can I use this interactive interview approach for any new feature like a user notification system?

Yes, you can use interactive interviewing for new features like a user notification system by providing a brief description to initiate the structured interview, which uncovers technical approaches and results in a well-defined Beads task.

When do I need to run an interactive requirements gathering interview instead of writing tasks manually?

You need an interactive requirements gathering interview when starting a new feature to ensure comprehensive requirement capture and product vision alignment, preventing misaligned development by capturing tradeoffs and technical approaches before any coding begins.