Guide structured pre-design interviews and generate a discovery.md brief.
npx skills add https://github.com/skullninja/coco-workflow --skill interview-skullninja
Please help me install this Agent Skill. Skill: interview Source: https://github.com/skullninja/coco-workflow/tree/main/skills/interview Command: npx skills add https://github.com/skullninja/coco-workflow --skill interview-skullninja
Structured pre-design interviews are often ad-hoc and fail to capture deep user intent and constraints. This skill provides a guided approach to elicit the essential context and produces a discovery brief (discovery.md) that feeds the design skill.
Ask Claude to start a discovery interview for a feature to generate a discovery.md.
High-intent search queries and answers about installing and using this skill.
A structured pre-design interview uses a guided flow to elicit user intent, constraints, and requirements. This approach covers problem motivation, scope, functional needs, and technical context to produce a discovery brief for planning.
Product discovery interviews should ask about problem motivation, target users, scope, functional requirements, technical context, and non-functional aspects. Using a template-driven process ensures you capture deep intent and essential constraints before design work begins.
To create a discovery brief, run a guided interview that gathers deep user intent and project constraints. The session outputs a discovery.md file that feeds directly into the design skill to drive downstream work.
Yes, the discovery brief supports iterative refinement. You can update the document while preserving prior context and session memory, ensuring continuity and capturing new requirements as the feature discovery process evolves.
You need a discovery brief during feature discovery and planning, specifically before design work begins. It captures essential context, deep user intent, and constraints that prevent ad-hoc requirements gathering from failing downstream design.
The best way to document non-functional requirements is using a repeatable, template-driven interview flow. This ensures technical context and non-functional aspects are captured alongside functional needs in a structured discovery brief.
clovernguyen1010-ship-itGuide user interviews and requirements discovery to draft PRDs.
jmylchreestGenerate technical design specifications with interfaces, data flow, and acceptance criteria.
rbah31Synchronize product-state and marketing-context to update briefs and generate recommendations.
The-InterdependencyTranslate user requirements into actionable design options with trade-offs.
