clarify

Identify and resolve the highest-value open questions blocking discovery progress.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill clarify-heymishy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/heymishy/2x2-v3-28-03-20216/tree/main/.github/skills/clarify
Command: npx skills add https://github.com/heymishy/2x2-v3-28-03-20216 --skill clarify-heymishy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Discovery clarification helps identify and resolve gaps quickly, ensuring a sharper artefact before /benefit-metric runs.

Core Features & Use Cases

  • Identifies the highest-value open questions blocking discovery progress.
  • Reads product context and the existing discovery artefact to surface gaps across four categories.
  • Updates the discovery artefact with clarified outputs after each session and produces a summary.

Quick Start

Start a clarification session to surface and resolve the top blockers in your discovery.

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I clarify discovery scope when MVP requirements are unclear?

Surface discovery blockers by reading product context and the existing discovery artefact to identify unresolved questions. It updates the artefact with clarified outputs after each session to sharpen scope before downstream metric definition.

How do I resolve stakeholder disputes over MVP scope during product discovery?

Resolve stakeholder MVP scope disputes by iteratively refining the discovery artefact across four gap categories. The skill identifies the highest-value open questions blocking consensus and updates the product context after each session.

When do I need to clarify discovery questions before defining a benefit metric?

You need to clarify discovery questions when a discovery is vague or scoping is unclear before running benefit-metric analysis. It ensures a sharper artefact by surfacing and resolving the top blockers between these phases.

Can I use existing product context to identify gaps in my discovery artefact?

You can use existing product context to identify gaps by reading it alongside the discovery artefact. The skill surfaces open questions across four categories and updates the artefact with clarified outputs after each session.

What are the limitations of iteratively refining discovery scope for unclear MVPs?

Iteratively refining discovery scope relies on reading existing product context and artefacts, so limitations arise if inputs are incomplete. It focuses on surfacing open questions across four categories rather than generating new product requirements.