discovery

Interview project stakeholders and write docs/discovery.md before scope definition.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/zabuuq/sdd-plugin --skill discovery-zabuuq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: discovery
Source: https://github.com/zabuuq/sdd-plugin/tree/main/plugins/sdd/skills/discovery
Command: npx skills add https://github.com/zabuuq/sdd-plugin --skill discovery-zabuuq

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of starting software planning with vague or premature structure by running an interview that captures a project’s idea, motivations, audience, prior art, constraints, and starting context before boundaries and requirements are defined.

Core Features & Use Cases

  • Project nature interview: Guides you through mandatory beats focused on “what is this?” (idea, why, audience, prior art, constraints, starting context).
  • Context-aware exploration: Loads shared behavior, reference material, your profile, and optional uploaded files under docs/refs to avoid re-asking what’s already answered.
  • Discovery artifact creation: Writes docs/discovery.md from interview results (with explicit overwrite confirmation on re-runs) and then hands off to /sdd:scope.

Quick Start

Run /sdd:discovery to interview you about your project’s idea, motivations, audience, prior art, constraints, and starting context, then produce docs/discovery.md and hand off to /sdd:scope.

Frequently Asked Questions about discovery

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

FAQPage Schema
How do I capture project requirements before defining scope?

To capture project requirements before defining scope, an interview workflow guides you through the idea, motivations, audience, prior art, and constraints. It produces a discovery document that ensures alignment before structural boundaries are set.

What is project discovery in product planning?

Project discovery is the process of capturing a project's true nature through an interview before structural decisions are made. It focuses on what the project is, why it exists, and its constraints to prevent premature planning.

How do I start the project discovery interview?

You start the project discovery interview by running the discovery command. It loads your user profile and any reference files under docs/refs to avoid re-asking answered questions, then guides you through mandatory beats.

Can I use existing reference docs during the requirements framing interview?

Yes, you can use existing reference docs during requirements framing. The interview workflow optionally loads content from files uploaded under docs/refs to provide context-aware exploration and avoid redundant questions.

Does the discovery interview require a user profile?

Yes, the discovery interview requires an existing user profile to enforce prerequisites. It checks for this profile before starting and prevents the interview from running if scope is already set in docs/scope.md.

What happens if I run discovery after scope is already set?

If you run discovery after scope is set, the workflow checks docs/scope.md and prevents the interview from proceeding. It ensures discovery only happens before boundaries and requirements are defined.