Guide clients through structured questions to generate a draft PRD.
npx skills add https://github.com/selcukyucel/north-starr-genai --skill discover-selcukyucel
Please help me install this Agent Skill. Skill: discover Source: https://github.com/selcukyucel/north-starr-genai/tree/main/skills/discover Command: npx skills add https://github.com/selcukyucel/north-starr-genai --skill discover-selcukyucel
This skill helps product teams and consultants turn vague problem statements into structured requirements by guiding a client through targeted questions and capturing essential details to form a PRD draft.
Input a client problem statement, topic area, or conversation context, and let the skill guide you through structured questions to surface needs and generate a draft PRD.
High-intent search queries and answers about installing and using this skill.
To elicit requirements from a client without a PRD, input their problem statement or topic area into a guided discovery workflow. The skill organizes grouped questions around problem, solution, and constraints to surface needs and synthesize a draft PRD.
The best way to turn a vague problem statement into a structured PRD draft is through guided client interviews. By asking targeted questions, you can capture essential details and frame them into a Problem, Solution, and Why structure with MVP scope.
You can generate a Problem/Solution/Why framing and MVP scope by running a structured requirement elicitation process. It classifies project type and effort internally, then outputs a draft PRD document containing success criteria and MVP scope.
Yes, you can use guided interviewing to draft product management requirements for stakeholders. The workflow coordinates conversations, asks grouped questions, and hands off to internal assessment tools to produce actionable PRD outputs.
The elicited requirements draft PRD outputs as a markdown file located at .plans/PRD-discover.md. This document contains the synthesized client answers, MVP scope, and defined success criteria.
No, you do not need prior context to start requirement elicitation for a draft PRD. The workflow is designed to start directly from a problem statement, a topic area, or existing conversation context to guide the discovery process.
carlosapgomesGuide brainstorming and requirement clarification with open-ended prompts.
juanelojgaBreak down complex projects into actionable tasks with timelines, dependencies, and milestones.
nashirabbashDraft production-ready PRDs from vague ideas via stakeholder interviews.
allaydesaiConduct simulated product manager interviews to create PRDs.
