Skip to main content

Delivery Standards

This is the execution contract for work handed from BMAD planning to Hank/Max implementation.

Scope Split (Non-Negotiable)​

  • BMAD owns planning artifacts: PRD, scope, acceptance criteria, architecture context.
  • Hank/Max own execution quality: implementation, testing, review, deployment readiness.

Required PR Standard​

Every execution PR must include:

  1. Summary — what changed and why
  2. Scope boundary — what is intentionally out-of-scope
  3. Acceptance mapping — each acceptance criterion mapped to implementation proof
  4. Risk notes — auth/data/perf/security risks
  5. Test evidence — exact commands + output snippets/screenshots
  6. Rollback plan — how to revert safely

PR Template Minimum​

## Summary
## Scope
## Acceptance Criteria Mapping
## Risks
## Test Plan + Evidence
## Rollback Plan

Testing Standard (Minimum Gate)​

At least one item in each bucket is required unless explicitly marked N/A with reason:

1) Unit / Logic​

  • Core logic paths
  • Edge-case behavior

2) Integration​

  • Service/API boundary checks
  • Auth/session behavior where applicable

3) End-to-End / User Path​

  • Primary happy path
  • One failure path

4) Manual Smoke​

  • "Can user actually do the thing" in production-like context
  • Mobile check if user-facing

Review Standard​

Hank review focus​

  • correctness
  • security/auth boundary
  • failure modes + rollback safety
  • maintainability

Max review focus​

  • user flow clarity
  • UI/UX quality
  • product acceptance fit
  • visual/mobile sanity

Compound Execution Loop​

Definition of Done​

A task is done only when all are true:

  • Acceptance criteria satisfied
  • Required tests executed and attached
  • Review comments resolved
  • Rollback path documented
  • Deployment validated

Escalation Rule​

If any of the following appears, stop and escalate before merge:

  • auth/session uncertainty
  • data-loss possibility
  • migration risk without rollback
  • test coverage missing for critical path