Proposal: Prototype Parity Kit — prototype-to-implementation quality gate for BMad

[JeremieP69]

Hello BMad maintainers,

I would like to propose Prototype Parity Kit, an open-source BMad extension that keeps a validated browser-renderable prototype actionable from PRD through UX, architecture, and implementation.

Repository and release

• Repository: https://github.com/JeremieP69/bmad-prototype-parity-kit
• Latest release: https://github.com/JeremieP69/bmad-prototype-parity-kit/releases/tag/v0.5.1
• SHA-256: f67a9bf409255cbe0904fafd22f96293f1151cc8b8789740f26aab1e27d20589

What it adds

• proto-design-source: captures versioned prototype evidence — baselines, rendered HTML, tokens, and story bindings.
• proto-parity-check: validates UI stories against the bound evidence, detects stale baselines, and records approved deviations.
• ppk-setup: registers the module and its capabilities with BMad help.

Proposed workflow placement

1. Capture or refresh prototype evidence before UI implementation.
2. Bind every UI story to its prototype evidence.
3. Run the per-story parity gate before the story closes.
4. Run a scoped parity audit before epic closure.

The gate is judged per route and viewport. Its normal target is at most 5% pixel mismatch with every remaining hotspot accounted for; it has an explicit stall stop after three iterations without meaningful progress.

Validation

The current release has a passing BMad module-structure validation and 10/10 Node tests passing. The package is neutralized for distribution and contains no project-specific material.

I would appreciate guidance on the preferred upstream location and module format for a community extension intended to integrate with BMad workflows and bmad-help.

Created and maintained by Jeremie PERERA.

Thank you for considering it.