why-driven-decision

Name: why-driven-decision
Availability: InStock
Author: ilandahan

Analyze prompts for explicit and implicit WHY before taking action.

9|2|Updated Dec 10, 2025

Search Tags:#decision-making #product-management #prompt-analysis #golden-circle #why-driven

Ready to run

npx skills add https://github.com/ilandahan/AID --skill why-driven-decision

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: why-driven-decision
Source: https://github.com/ilandahan/AID/tree/main/.claude/skills/why-driven-decision
Command: npx skills add https://github.com/ilandahan/AID --skill why-driven-decision

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill ensures every prompt is grounded in purpose by applying the Golden Circle (WHY -> HOW -> WHAT) before taking action, reducing misalignment and scope creep.

Core Features & Use Cases

WHY-driven prompt analysis: extracts explicit WHY, infers implicit WHY, and anchors outputs to purpose.
Cross-role alignment: guides PM, Dev, and QA in decision-making and reviews to ensure consistent reasoning.
Output & documentation: embeds WHY into responses, comments, and design notes to preserve rationale.
Use Case: before designing a feature, run WHY-driven analysis to align stakeholders and minimize rework.

Quick Start

Begin by providing a prompt and asking for WHY-driven analysis before proceeding. For example: "Explain the core motivation for adding a user analytics feature and outline its WHY, HOW, and WHAT."

Frequently Asked Questions about why-driven-decision

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

FAQPage Schema

What is WHY-driven decision-making in product management?▼

WHY-driven decision-making applies the Golden Circle (WHY -> HOW -> WHAT) to product management, ensuring every prompt and feature is grounded in purpose before action. It makes prompt-level motivation visible to reduce stakeholder misalignment and scope creep.

How do I analyze the motivation for adding a product feature before development?▼

To analyze motivation before development, run a WHY-driven prompt analysis to extract explicit and implicit motivations. Outline the feature's WHY, HOW, and WHAT to align stakeholders and minimize rework before design begins.

Can I use the 5 Whys tracing method for engineering planning and design reviews?▼

Yes, 5 Whys tracing is supported for engineering planning and design reviews. It maintains alignment across PM, Dev, and QA roles by documenting explicit rationale and embedding WHY-driven comments into design notes.

Do I need external tooling to document rationale in design notes?▼

No external tooling is required to document rationale in design notes. WHY-driven analysis operates at the prompt level, embedding purpose directly into responses and comments to preserve decision reasoning without extra dependencies.

What is the best way to prevent scope creep during prompt analysis?▼

The best way to prevent scope creep during prompt analysis is to anchor outputs to purpose using the Golden Circle. Extracting explicit and implicit WHY motivations before taking action ensures decisions remain aligned with the original goal.