hdd

Validate root causes with a structured hypothesis-driven workflow.

64|5|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/MattWenJun/ClaWiser --skill hdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hdd
Source: https://github.com/MattWenJun/ClaWiser/tree/main/assets/hdd
Command: npx skills add https://github.com/MattWenJun/ClaWiser --skill hdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

HDD provides a structured methodology to diagnose root causes and validate hypotheses when outcomes are uncertain, guiding teams through a repeatable decision-making process before implementing changes.

Core Features & Use Cases

  • Seven-step workflow: HT (Hypothesis Test), PT (Plan Test), AT Design (Acceptance Test Design), DEV (Development), AT Run (Acceptance Test Run), and E2E (End-to-End) to structure problem solving.
  • Evidence-based decision making: formalizes hypotheses, priors, and verification paths to reduce guesswork.
  • Use cases include debugging ambiguous defects, architecture and design decisions under uncertainty, and risk mitigation across product development.

Quick Start

Start HDD by outlining your uncertain problem, identify the hypothesis to test, and map a seven-step plan before coding.

Frequently Asked Questions about hdd

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

FAQPage Schema
What is hypothesis-driven development for debugging and architecture decisions?

Hypothesis-driven development is a structured methodology to diagnose root causes and validate hypotheses under uncertainty. It formalizes hypotheses, priors, and verification paths to reduce guesswork before implementing changes during debugging or architecture planning.

How do I debug ambiguous defects using a structured hypothesis workflow?

To debug ambiguous defects, outline the uncertain problem, identify a hypothesis to test, and map a stepwise plan. This enforces evidence grading and explicit acceptance criteria to guide decision-making through a seven-step process before coding.

When should I use a hypothesis-driven workflow for problem-solving?

Use a hypothesis-driven workflow during diagnosis, debugging, feature planning, and architecture changes where outcomes are uncertain or multiple solutions exist. It applies specifically to scenarios requiring risk mitigation and evidence-based decision-making across product development.

What is the best way to validate root causes under uncertainty in software engineering?

The best way to validate root causes is applying a stepwise process including Hypothesis Test, Plan Test, Acceptance Test Design, Development, Acceptance Test Run, and End-to-End testing. This enforces evidence grading and explicit acceptance criteria to guide decisions.

Does hypothesis-driven development work for risk mitigation across product development?

Yes, hypothesis-driven development works for risk mitigation across product development by enforcing a stepwise process and evidence grading. It formalizes verification paths to reduce guesswork when navigating uncertain architecture decisions or ambiguous defects.