Frame real problems from vague requests using structured discovery steps.
npx skills add https://github.com/epicsagas/epicsagas --skill discover-epicsagas
Please help me install this Agent Skill. Skill: discover Source: https://github.com/epicsagas/epicsagas/tree/main/skills/discover Command: npx skills add https://github.com/epicsagas/epicsagas --skill discover-epicsagas
Helps teams articulate the real problem behind vague requests, turning solution-first thinking into structured problem definitions and JTBD framing.
Identify a vague request, run the discovery steps, and generate a framed problem statement with constraints and success criteria.
High-intent search queries and answers about installing and using this skill.
To frame a clear problem statement from vague user requests, classify request signals and apply a guided discovery probing framework. This process produces a documented problem frame with boundaries, constraints, and success criteria to prevent jumping to solutions.
The best way to structure problem definition for software teams is using a stepwise discovery process that transforms solution-first thinking into Jobs-to-be-Done framing. It yields a documented problem frame with explicit boundaries and success criteria.
To align stakeholders when scoping project ideation, apply a probing framework to translate vague requests into a clear problem statement. Documenting constraints and assumptions ensures all stakeholders share a unified understanding of the problem boundaries.
You need problem framing workflows for feature scoping when facing vague or solution-first requests. Applying a discovery process categorizes these signals and produces a structured problem definition with documented boundaries to prevent premature solutioning.
To use Jobs-to-be-Done to prevent jumping to solutions, apply a stepwise discovery process that probes vague requests and categorizes signals. This produces a structured problem definition with documented assumptions rather than a direct feature build.
GenEducationClarify product requirements from vague ideas into concise PRDs.
benshapyroTransforms vague ideas into actionable product specifications using Five Whys, MECE, and Socratic Probing across Vision to Scoping phases.
reckerswartzFrame ambiguous stakeholder requests into problem statements and architectural options.
neurofooGuide product development through the five stages of Design Thinking.
