- Home
- Skills
- Bacoco
- Bmad Skills
- Bmad Discovery Research
bmad-discovery-research_skill
- Python
61
GitHub Stars
4
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill bacoco/bmad-skills --skill bmad-discovery-research- CHECKLIST.md510 B
- REFERENCE.md9.2 KB
- SKILL.md4.1 KB
- WORKFLOW.md834 B
Overview
This skill helps turn vague ideas and early problem statements into structured discovery artifacts that product and engineering teams can act on. It identifies goals, constraints, risks, and open questions, then produces a discovery brief, brainstorm notes, a product brief, and a research dossier. The skill is aimed at Level 3-4 projects or any situation where requirements are unclear and research is needed. It recommends readiness for planning or signals the need for further discovery.
How this skill works
The skill validates entry criteria and classifies project complexity, then runs desk research across provided context assets and cites sources. It frames findings into concise problem summaries, goals, personas, constraints, and a prioritized risks/questions register. Deliverables are produced from templates and include recommendations on whether the project is ready to progress to product planning.
When to use it
- You have a vague idea and need structured clarity to begin planning.
- You want competitive or market research to assess an opportunity.
- Stakeholders disagree or goals are unclear and need alignment.
- You’re starting a complex/novel Level 3-4 project requiring discovery.
- You need prioritized open questions and risk owners before drafting requirements.
Best practices
- Provide an initial problem statement, stakeholders list, and any relevant assets before starting.
- Flag missing or low-confidence data early and gather clarifying inputs rather than guessing.
- Capture assumptions and open questions with recommended owners and timelines.
- Classify project complexity up front to select appropriate depth of research.
- Use the produced artifacts as inputs to downstream planning and development workflows.
Example use cases
- Brainstorming features and technical approaches for a new product idea.
- Conducting market and competitor research to validate an opportunity.
- Documenting an existing project to surface unknowns before scoping.
- Turning stakeholder conversations into a prioritized question and risk register.
- Preparing a research dossier to support executive decision-making.
FAQ
At minimum, give a concise problem statement, list of stakeholders, and links to any repos or market docs. If essential context is missing the skill will request it.
When will this skill not be used?
Don’t use it when requirements are already detailed, the project is small and well-defined, or you need implementation-level help; those scenarios are handled by product-planning or development execution workflows.