dew-discover

Develop shared problem-domain understanding with assumptions inventory and measurable acceptance criteria.

5|1|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/jkerdels/dew-plugin --skill dew-discover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dew-discover
Source: https://github.com/jkerdels/dew-plugin/tree/main/skills/dew-discover
Command: npx skills add https://github.com/jkerdels/dew-plugin --skill dew-discover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

dew-discover helps you build crystal-clear shared understanding of a problem domain so you can set goals and acceptance criteria before any implementation discussion starts.

Core Features & Use Cases

  • Assumptions inventory: surfaces hidden or implicit assumptions and makes them explicit, ranked by risk and uncertainty.
  • Stakeholder-aligned context: clarifies who is affected, what the current pain is, system boundaries, and what success means to each stakeholder.
  • Measurable success criteria: turns vague targets into concrete, testable metrics with thresholds for good, acceptable, and not acceptable.

Quick Start

Use the dew-discover skill at the start of your project to define stakeholders, boundaries, must-haves, and acceptance criteria without discussing implementation details.

Frequently Asked Questions about dew-discover

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

FAQPage Schema
How do I define measurable success criteria and acceptance criteria before implementation?

To define measurable success criteria and acceptance criteria, you must turn vague targets into concrete, testable metrics with explicit thresholds for good, acceptable, and not acceptable outcomes before any implementation discussion starts.

What is the best way to surface and inventory hidden assumptions during problem framing?

Surfacing hidden assumptions during problem framing involves making implicit assumptions explicit and ranking them by risk and uncertainty to ensure shared understanding across the problem domain.

How do I map stakeholder context and system boundaries for new feature scoping?

Mapping stakeholder context for feature scoping requires clarifying who is affected, identifying current pain points, defining system boundaries, and determining what success means to each stakeholder group.

Can I use problem framing techniques to re-validate requirements after discovering later-stage gaps?

Yes, problem framing techniques can be applied to re-validate requirements after later-stage gaps are discovered, ensuring explicit assumptions inventory and stakeholder context mapping are updated accordingly.

Does workflow planning require discussing implementation details when setting project goals?

Workflow planning for setting project goals does not require discussing implementation details; the focus remains on defining stakeholders, boundaries, must-haves, and acceptance criteria.