How does it handle complex architectural decisions?

It presents 2-3 distinct approaches with clear trade-offs, providing a recommendation while allowing you to choose the direction that best fits your needs.

Can it help prevent scope creep?

Absolutely. It applies YAGNI (You Ain't Gonna Need It) principles and suggests phasing for large ideas to keep projects focused and manageable.

Does it support interactive decision making?

Yes, it utilizes the AskUserQuestion tool to provide structured options, making it faster and easier for users to select preferences or rank priorities than open-ended text.

When does the Discovery skill trigger?

It triggers automatically at the start of tasks like 'build,' 'create,' or 'help me with,' as well as mid-task when implementation ambiguities or edge cases arise.

How are requirements documented?

The skill captures success criteria, scope boundaries, constraints, and edge case handling in a 'Capture' phase to ensure execution proceeds without further interruptions.

Discovery Requirement Gathering

Name: Discovery Requirement Gathering
Author: btimothy-har

bybtimothy-har

0•

협업 도구

Facilitates structured user interviews and requirement gathering to transform ambiguous requests into clear, actionable technical specifications.

The Discovery skill provides Claude Code with a systematic framework for requirement elicitation and scope negotiation. It employs specialized interview techniques—such as scenario probing and preference comparison—to resolve ambiguities before implementation begins. By guiding users through a three-phase pipeline consisting of Interview, Design, and Capture, it ensures technical decisions align with user priorities, prevents scope creep through YAGNI principles, and documents success criteria to streamline the development lifecycle.

주요 기능

01Comprehensive requirement capture covering success criteria and constraints

02Interactive tool integration for multi-choice decision-making and priority ranking

03Structured interview techniques for surfacing edge cases and hidden requirements

04Rigorous scope negotiation to prevent feature creep and gold-plating

05Collaborative design phase for comparing architectural trade-offs

060 GitHub stars

사용 사례

01Clarifying ambiguous feature requests or architectural decisions at the start of a task

02Defining 'done' criteria and error-handling strategies for new feature development

03Selecting between multiple technical implementations with distinct performance or complexity trade-offs

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add btimothy-har/basecamp discovery

For use in Claude.ai and ChatGPT