project-requirements-clarification

Name: project-requirements-clarification
Availability: InStock
Author: w020316

Guide structured questioning to clarify project ideas into requirement documents.

Updated May 15, 2026

Search Tags:#planning #requirements #socratic #product-management #user-research #stakeholders

Ready to run

npx skills add https://github.com/w020316/cautious-broccoli --skill project-requirements-clarification

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-requirements-clarification
Source: https://github.com/w020316/cautious-broccoli/tree/main/workflow/project-requirements-clarification
Command: npx skills add https://github.com/w020316/cautious-broccoli --skill project-requirements-clarification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

通过系统化的引导式提问，帮助用户把模糊的项目想法澄清为结构化的需求描述，节省需求梳理时间并降低沟通成本。

Core Features & Use Cases

Socratic questioning：以“为什么、对谁、解决什么”等维度持续提问，逐步揭示核心需求。
结构化产出：最终产出包含项目一句话描述、核心价值、目标用户画像、关键特征清单等可落地的需求文档。
可重复使用与迭代：技能可在项目开发过程中的不同阶段重复触发以重新澄清变更需求。使用场景示例：当用户提出一个模糊的产品点子时，系统引导整理成可开发的需求清单并形成规格文档。

Quick Start

Initiate a guided clarification session to transform a vague idea into structured requirements.

Frequently Asked Questions about project-requirements-clarification

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

FAQPage Schema

How do I turn vague product ideas into structured requirements?▼

To turn vague product ideas into structured requirements, use Socratic questioning to clarify why the project exists, who it serves, and what it solves. This guided elicitation produces a unified spec including user personas and feature lists.

What is Socratic questioning for requirements elicitation?▼

Socratic questioning for requirements elicitation is a method of continuously asking why, for whom, and what problem is solved to gradually reveal core product needs from ambiguous stakeholder conversations and early idea captures.

How do I document stakeholder conversations into a unified spec?▼

You document stakeholder conversations into a unified spec by applying structured elicitation techniques during discussions. This translates evolving product requirements into actionable documentation like a one-sentence project description and core value proposition.

Can I reuse a requirements clarification workflow for evolving product requirements?▼

Yes, you can reuse a requirements clarification workflow for evolving product requirements. The interactive questioning session can be triggered repeatedly throughout project development to re-clarify and document changed stakeholder needs.

What should be included in a structured requirements document for product management?▼

A structured requirements document for product management should include a one-sentence project description, core value proposition, target user personas, and a key feature list to ensure actionable and unified specifications.

Does guided requirements elicitation work for early idea capture?▼

Guided requirements elicitation works effectively for early idea capture by systematically questioning the initial concept. It transforms rough concepts into structured outputs, lowering communication costs and saving requirement sorting time.