Transform vague product ideas into a structured PMContext through automated collection and refinement.
npx skills add https://github.com/Wcof/PMSkill --skill pm-need
Please help me install this Agent Skill. Skill: pm-need Source: https://github.com/Wcof/PMSkill/tree/main/skills/discovery/pm-need Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-need
This Skill helps product teams turn ambiguous ideas, scattered context, or raw stakeholder requests into a structured PMContext that can drive downstream delivery artifacts. It reduces the manual effort of discovery, clarification, and documentation by orchestrating collection, refinement, audit, and optional auto-generation of PRD, stories, and prototypes.
Ask the agent to run pm-need on your feature idea, and add the auto flag if you want it to continue from discovery through PRD, stories, and prototype generation without pausing.
High-intent search queries and answers about installing and using this skill.
To turn vague product ideas into a structured PRD, you need a workflow that refines stakeholder requests into a structured PMContext, orchestrating collection and audit to generate downstream deliverables. This process handles evidence-aware reasoning to distinguish facts from assumptions.
Automating stakeholder intake involves running an end-to-end discovery orchestration that collects raw requests and refines them into a structured PMContext. This process applies confidence labeling and conflict handling to distinguish facts, assumptions, and unresolved gaps during requirement analysis.
Yes, you can generate product documentation autonomously by using a zero-confirmation auto mode for fast execution. This mode runs the entire workflow from requirement discovery through PRD, user stories, premortem risk analysis, and prototype generation without pausing for manual input.
Yes, product discovery workflows support dual operating modes, including an interactive clarification mode for normal PM processes. This allows you to manually guide the collection and refinement of stakeholder requests into a structured PMContext before generating downstream deliverables.
Handling conflicting assumptions during requirements analysis requires evidence-aware reasoning that applies confidence distribution and audit summaries to the collected context. This mechanism identifies conflicts, separates facts from unresolved gaps, and ensures the structured PMContext remains accurate.
From a structured PMContext, you can generate downstream deliverables including PRDs, user stories, premortem risk analysis, and prototype plans. This requires chaining the refined context through automated generation workflows to produce executable documentation for the product team.
GenEducationClarify product requirements from vague ideas into concise PRDs.
WcofGenerates an AI-executable PRD from PMContext with traceable stories and criteria.
WcofRefine product requirement materials into a structured PMContext file.
tgmarinhoConvert conversation content into a Product Requirements Document and publish it to an issue tracker.
