clarify

Transforms vague user input into a concept one-pager via adaptive dialogue and Convergence Test.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Pyl-Tech/stream-coding --skill clarify-pyl-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify
Source: https://github.com/Pyl-Tech/stream-coding/tree/main/.agents/skills/clarify
Command: npx skills add https://github.com/Pyl-Tech/stream-coding --skill clarify-pyl-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify transforms a vague or early-stage idea into a sharp concept so strategy and downstream planning don’t get forced prematurely or built on uncertain assumptions.

Core Features & Use Cases

  • Structured dialogue: Guides an adaptive conversation to uncover the real problem, audience, success vision, and what’s already been tried.
  • Explore and challenge: Uses reframing techniques (e.g., inversion, constraint/scale shifts, simplification) to surface assumptions and generate viable variations.
  • Converge with an exit gate: Produces a concept one-pager and runs a Convergence Test to ensure key assumptions are confirmed or explicitly deferred.

Quick Start

Ask the AI: "I have an early idea for a product but I’m not sure about the scope or audience—help me clarify it and produce a concept one-pager for strategy."

Frequently Asked Questions about clarify

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

FAQPage Schema
How do I turn a vague product idea into a build-ready concept?

To turn a vague product idea into a build-ready concept, you guide an adaptive dialogue to uncover the real problem and audience, then apply reframing techniques to resolve critical uncertainties and generate a concept one-pager.

What is assumption management in early product scope definition?

Assumption management in product scope definition uses reframing techniques like inversion and constraint shifts to surface hidden uncertainties, ensuring critical assumptions are explicitly confirmed or deferred before strategy planning begins.

How do I define product scope when the target audience is unclear?

To define product scope with an unclear target audience, run an adaptive multi-phase dialogue to challenge existing assumptions, exploring problem variations until the direction becomes concrete enough to pass a convergence test.

What is the best way to document product strategy before planning begins?

The best way to document early product strategy is producing a concept one-pager that captures the problem, audience, and success vision, passing a convergence test to prevent premature planning on uncertain assumptions.

When should I use concept development techniques for post-research grounding?

You should use concept development for post-research grounding when target audience, problem, and direction are not yet concrete, requiring adaptive dialogue to adopt, adapt, or build upon findings before strategy planning.