ldy26098
/
BMAD-METHOD
mirror of https://github.com/bmad-code-org/BMAD-METHOD.git
1
0
Fork 0
Code Packages Projects Releases Wiki Activity
BMAD-METHOD/devKalla-Fordonscervice/_wds/workflows/6-design-deliveries/steps/step-6.2-create-delivery.md

3.5 KiB
Raw Blame History

Step 6.2: Create Design Delivery

Goal: Package complete testable flow into Design Delivery YAML file

Purpose

Create a Design Delivery file that serves as the contract between design and development.

This file documents:

  • What's being delivered
  • Why it matters (user value)
  • What's included (scenarios, components)
  • How to implement (technical requirements)
  • How to validate (acceptance criteria)

Before You Start

Ensure you have:

  • ✅ Completed step 6.1 (flow is complete)
  • ✅ All scenario specifications ready
  • ✅ All component definitions ready
  • ✅ Clear understanding of user value

Instructions

Execute the following substeps in sequence to build the Design Delivery file:

Substep 1: Initialize Delivery File

Load, read completely, then execute: substeps/6.2-substeps/01-initialize-delivery.md

This substep will:

  • Choose delivery ID (DD-XXX format)
  • Copy template
  • Fill out basic metadata

Substep 2: Define User Value

Load, read completely, then execute: substeps/6.2-substeps/02-define-user-value.md

This substep will:

  • Define problem being solved
  • Define solution provided
  • Define success criteria

Substep 3: List Design Artifacts

Load, read completely, then execute: substeps/6.2-substeps/03-list-artifacts.md

This substep will:

  • List all scenarios included
  • List user flows
  • List design system components used

Substep 4: Define Technical Requirements

Load, read completely, then execute: substeps/6.2-substeps/04-define-technical.md

This substep will:

  • Specify platform/tech stack
  • List integrations needed
  • Define data models
  • Set performance requirements

Substep 5: Define Acceptance Criteria

Load, read completely, then execute: substeps/6.2-substeps/05-define-acceptance.md

This substep will:

  • List functional requirements
  • List non-functional requirements
  • Define edge cases to handle

Substep 6: Add Testing Guidance

Load, read completely, then execute: substeps/6.2-substeps/06-add-testing-guidance.md

This substep will:

  • Define user testing approach
  • Define QA testing scope
  • Define design validation checks

Substep 7: Estimate Complexity

Load, read completely, then execute: substeps/6.2-substeps/07-estimate-complexity.md

This substep will:

  • Estimate size and effort
  • Identify dependencies
  • Document assumptions
  • Assess risk level

Critical Rules

  • 🛑 NEVER load multiple substeps simultaneously
  • 📖 ALWAYS read entire substep file before execution
  • 🚫 NEVER skip substeps or optimize the sequence
  • 🎯 ALWAYS follow the exact instructions in each substep

Validation

Before proceeding, verify:

  • Delivery ID is unique and follows format
  • All required fields are filled
  • All scenarios are referenced
  • All components are listed
  • Technical requirements are clear
  • Acceptance criteria are testable
  • Complexity estimate is realistic

Next Step

After Design Delivery file is complete:

✅ Design Delivery file created: deliveries/DD-XXX-name.yaml

Load and execute: step-6.3-create-test-scenario.md

Do NOT skip ahead.

Success Metrics

✅ Design Delivery file created ✅ All required fields filled ✅ All scenarios and components referenced ✅ Technical requirements documented ✅ Acceptance criteria defined ✅ Testing guidance provided ✅ Complexity estimated

Remember: This Design Delivery is the contract between design and development. Be thorough!