des-business-discovery

Create a validated Business Discovery Brief and Phase 01 support artifacts.

2|Updated May 20, 2026
One-click install
npx skills add https://github.com/DKSang/DES-SKILL --skill des-business-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: des-business-discovery
Source: https://github.com/DKSang/DES-SKILL/tree/main/skills/des-business-discovery
Command: npx skills add https://github.com/DKSang/DES-SKILL --skill des-business-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents data engineering teams from starting technical design with missing or invented business context by creating a validated Business Discovery Brief and Phase 01 support artifacts.

Core Features & Use Cases

  • Business Discovery Brief creation: Document project intent, business problem, stakeholders/consumers, target decisions or use cases, expected value, constraints, assumptions, risks, success criteria, and open questions.
  • Evidence-driven validation: Collect or reference evidence for each critical decision and explicitly mark items as Confirmed, Assumed, Missing, Waived with reason, or Accepted with risk.
  • Phase-Orchestrated Done Gate + handoff: Run a Phase 01 Done Gate and produce a Phase 01-to-Phase 02 handoff so downstream phases do not rely on hidden assumptions.

Quick Start

Use des-business-discovery to draft a Business Discovery Brief by providing the project idea or problem statement and the known stakeholders/consumers, then answer the HALT questions when key decisions are unclear.

Frequently Asked Questions about des-business-discovery

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

FAQPage Schema
How do I document business context before starting data engineering design?

To document business context, create a Business Discovery Brief capturing project intent, stakeholders, target decisions, expected value, and success criteria. This validated brief prevents technical design from proceeding based on missing or invented assumptions.

What is a phase handoff in a data engineering workflow?

A phase handoff is an artifact produced during a Phase 01 Done Gate. It transfers validated business context and evidence-backed decisions to downstream phases, ensuring technical design does not rely on hidden assumptions.

How do I track evidence validation for data project requirements and KPIs?

Track evidence validation by explicitly marking each critical decision or requirement as Confirmed, Assumed, Missing, Waived with reason, or Accepted with risk. This evidence pack approach ensures traceability for requirements and KPIs.

When should I run discovery instead of technical schema design?

Run discovery when a project idea is vague, solution-first, or when technical requests arrive before business context is established. Guardrails forbid schema, pipeline, and KPI formula design until the Business Discovery Brief is complete.

What do I do when key decisions are unclear during business discovery?

When key decisions are unclear during business discovery, answer the HALT checkpoint questions. These checkpoints validate critical assumptions and resolve open questions before producing the Phase 01 handoff artifacts.

Can I use business discovery for vague data project ideas without defined stakeholders?

Yes, you can initiate business discovery for vague ideas by providing the initial problem statement. The workflow then helps identify and document the necessary stakeholders, consumers, and target use cases to build a complete evidence pack.