Active Listening Skill

Format ambiguous requirements into executable acceptance criteria with structured artifacts.

Updated Nov 8, 2025
One-click install
npx skills add https://github.com/yodakeisuke/BDD-promps-with-eval --skill active-listening-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Active Listening Skill
Source: https://github.com/yodakeisuke/BDD-promps-with-eval/tree/main/.claude/skills/bdd/active-listening
Command: npx skills add https://github.com/yodakeisuke/BDD-promps-with-eval --skill active-listening-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

このスキルは、漠然とした要求や不完全な情報から、真のビジネス価値とユーザーニーズを特定する困難を解消します。これにより、手戻りや無駄な開発を削減し、プロジェクトの初期段階での明確性を高めます。

Core Features & Use Cases

  • 5 Whys & ソクラテス式問答: 根本原因と仮定を深掘りし、要求の本質を明らかにすることで、表面的な解決策に飛びつくことを防ぎます。
  • 5W1Hフレームワーク: 要求のあらゆる側面を網羅的に質問し、スコープを明確化することで、見落としを防ぎます。
  • 要件定義の土台構築: 新規プロジェクトのキックオフ時や、既存機能の改善提案があった際に、ステークホルダーの意図を深く理解し、具体的な要件定義の土台を築きます。

Quick Start

Active Listeningスキルを使って、ECサイトの検索機能に関する曖昧な要求を深掘りしてください。

Frequently Asked Questions about Active Listening Skill

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

FAQPage Schema
How do I extract true requirements from ambiguous or incomplete stakeholder requests?

Active Listening applies three structured techniques—5 Whys, Socratic questioning, and 5W1H framework—to uncover root causes and hidden assumptions. This transforms vague input into executable acceptance criteria, user stories, and Gherkin specifications aligned with actual business value.

What's the best way to clarify scope and prevent requirement misalignment in backlog refinement sessions?

Use Active Listening, Example Mapping, and Formulation techniques during refinement to produce standardized artifacts. These methods enforce declarative language and generate business rules, examples, and structured questions that align all stakeholders before development starts.

Can I use this approach to improve requirements for new project kickoffs and feature enhancement proposals?

Yes. Active Listening builds the foundation for requirement definition at project inception and when evaluating improvement suggestions. It captures stakeholder intent deeply, prevents hand-rework, and reduces wasted development by establishing clarity in early stages.

How do I structure questions to uncover unstated needs and spot gaps in requirement definitions?

The 5W1H framework systematically covers all dimensions of a requirement—who, what, when, where, why, and how—surfacing overlooked details. Combined with Socratic questioning, this prevents scope creep and ensures comprehensive coverage before acceptance criteria are finalized.

What outputs does this technique produce, and how do I use them in downstream development workflows?

Active Listening generates user stories, business rules, examples, questions, and Gherkin specifications. These structured artifacts serve as reference templates and inputs for design, testing, and implementation phases, ensuring all downstream work stays aligned with validated requirements.