skills.rest
sinositato
sinositatoCOMMUNITY
Explore all skills by this author →
GitHub

prd-discover

Gather problem, user, scope, and success criteria into a markdown context file.

Updated Feb 14, 2026
Search Tags:#requirements#product management#discovery#prd#context gathering
One-click install
npx skills add https://github.com/sinositato/tato-claude-plugins --skill prd-discover
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prd-discover
Source: https://github.com/sinositato/tato-claude-plugins/tree/main/plugins/prd-builder/skills/prd-discover
Command: npx skills add https://github.com/sinositato/tato-claude-plugins --skill prd-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill streamlines the initial phase of Product Requirements Document (PRD) creation by systematically gathering essential context from the user.

Core Features & Use Cases

  • Structured Questioning: Asks targeted questions about the problem, users, scope, constraints, and success criteria.
  • Contextual Output: Saves gathered information into a structured markdown file, ready for the drafting stage.
  • Use Case: When starting a new feature, use this skill to ensure all critical aspects are considered before writing the PRD, preventing scope creep and ensuring clarity.

Quick Start

Run the prd-discover skill to start gathering context for a new feature called 'user-authentication'.

Frequently Asked Questions about prd-discover

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

FAQPage Schema
What is PRD context gathering and why is it needed before writing product requirements?▼

PRD context gathering systematically collects essential information on problem statements, target users, scope, constraints, and success criteria to ensure clarity and prevent scope creep before drafting product requirements.

How do I gather context for a Product Requirements Document using a structured discovery session?▼

Start a structured discovery session to ask targeted questions about your feature's problem, users, scope, and constraints. The gathered context is then saved as a markdown file ready for subsequent PRD drafting.

What's the best way to prevent scope creep when starting a new product feature?▼

Conducting a structured discovery session before drafting product requirements ensures all critical aspects like scope and constraints are considered upfront, effectively preventing scope creep and ensuring project clarity.

Can I save gathered product management context directly into a markdown file?▼

Yes, the gathered context from the discovery session is automatically saved into a structured markdown file, providing a contextual output document that is ready for the subsequent product requirements drafting stage.

Does this discovery process require any specific product management tools or dependencies?▼

No specific external tools or dependencies are required to run the context gathering process. It independently conducts the discovery session and saves the structured output directly as a markdown file.

Related Skills

Explore More Product & Management Skills→
Adelie-SquadAdelie-Squad
17

PMF Planner Agent

...

Official
Advanced
julianromlijulianromli
182

prd

Generate comprehensive Product Requirements Documents with structured sections for architecture, APIs, and testing.

Community
Advanced
devCharuzudevCharuzu

agile-product-owner

Organize Agile backlog management and sprint execution with user stories and capacity planning.

Community
Advanced
EvolutionAPIEvolutionAPI
520

pm-product-brainstorming

Guide product teams through structured brainstorming modes with a session framework.

Official
Advanced