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.