Ask_Why

Convert vague planning requests into decision-backed plans via iterative question rounds.

118|9|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/maxkura/Ask_Why --skill ask-why
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Ask_Why
Source: https://github.com/maxkura/Ask_Why/tree/main/Ask_Why
Command: npx skills add https://github.com/maxkura/Ask_Why --skill ask-why

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps you turn ambiguous, open-ended tasks into a traceable planning conversation by making assumptions explicit and guiding iterative human decisions instead of producing an ungrounded final answer.

Core Features & Use Cases

  • Decision-round planning for ambiguity: Runs concise P2A rounds to clarify goals, boundaries, risks, and tradeoffs when early wrong choices cause rework.
  • Assumption challenge + convergence: Early rounds challenge weaknesses and explore divergent directions, then progressively converge to a draft and finally a final plan.
  • Durable state artifacts: Maintains PLAN.md, DECISIONS.md, and OPEN_QUESTIONS.md (and FINAL_PLAN.md when converged) so reasoning is preserved and replayable.

Quick Start

Use Ask_Why to help you design a product workflow by asking it to run decision rounds and produce PLAN.md, DECISIONS.md, OPEN_QUESTIONS.md, and then FINAL_PLAN.md after the direction is clear.

Frequently Asked Questions about Ask_Why

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

FAQPage Schema
How do I turn vague product design requests into decision-backed plans?

PRD planning handles ambiguous requirements by making assumptions explicit and guiding iterative human decisions. It uses prioritized unknowns to clarify goals, boundaries, and risks before producing an ungrounded final answer.

How do I create a traceable workflow design from ambiguous requirements?

Creating traceable workflow design involves maintaining durable state artifacts like PLAN.md and DECISIONS.md. These files preserve reasoning throughout iterative question rounds, ensuring planning logic remains replayable and verifiable.

Can I use iterative question rounds for research planning and agent design?

Iterative question rounds apply directly to research planning and agent design where user preferences materially affect outcomes. The process uses fixed question formats to explore divergent directions before converging on a draft plan.

What is the best way to prevent high-rework in technical strategy planning?

Preventing high-rework in technical strategy planning requires an entry gate to decide whether to run, followed by prioritized P0/P1/P2 unknowns. This structure catches early wrong choices before they cascade into rework.

Does decision-round planning work for skill design and PRD creation?

Decision-round planning works for skill design and PRD creation by running concise rounds to clarify goals and tradeoffs. It maintains OPEN_QUESTIONS.md and FINAL_PLAN.md artifacts so reasoning is preserved when direction converges.