clarify-demand

Clarify demand and feasibility before work-item registration with an Intake Brief.

8|Updated Sep 22, 2025
One-click install
npx skills add https://github.com/hardness1020/VibeFlow --skill clarify-demand
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarify-demand
Source: https://github.com/hardness1020/VibeFlow/tree/main/.claude/skills/clarify-demand
Command: npx skills add https://github.com/hardness1020/VibeFlow --skill clarify-demand

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarify demand and feasibility before formal work-item registration to ensure the right problem, users, and scope are understood and aligned.

Core Features & Use Cases

  • Demand Clarification: Elicit key details (problem, users, success criteria, constraints, scope) through guided conversations.
  • Feasibility Research & Synthesis: Quick assessment of feasibility and generation of an Intake Brief to summarize findings for stakeholders.
  • Handoff Readiness: Provide a concrete description and recommended track for /manage-work registration, enabling a smooth handoff.

Quick Start

Begin the intake workflow by asking clarifying questions to surface the problem, users, criteria, and constraints before registering a work item.

Frequently Asked Questions about clarify-demand

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

FAQPage Schema
How do I clarify product demand and feasibility before registering a work item?

You clarify demand by running an intake workflow that elicits the problem, users, success criteria, and constraints through guided conversations before generating an Intake Brief for stakeholder alignment.

What is an intake brief in the demand clarification process?

An Intake Brief is a summary document produced during demand clarification that captures the problem, users, feasibility, complexity, recommended track, rationale, and suggested description for stakeholder review.

How do I assess feasibility for early-stage product ideas across different domains?

Feasibility research assesses early-stage ideas across domains by delegating technical checks to the codebase-analyst, synthesizing findings into a complexity rating and recommended track for the work item.

Can I use this demand intake process for ideas without a defined scope or track?

Yes, the demand intake process applies specifically to early-stage ideas without defined scope, guiding track selection and scoping decisions before formal registration through the manage-work command.

What's the best way to prepare a product work item for registration handoff?

The best way to prepare for registration handoff is to produce an Intake Brief with a concrete description and recommended track, enabling a smooth transition into the manage-work registration command.