breadboard-reflection

Audit breadboard wiring for design smells by supplying the breadboard document and requirements to trace user stories, apply the naming test, and verify wiring consistency against expected outcomes.

The naming test validates breadboard affordances by ensuring each has a single idiomatic verb and clear boundaries. This surfaces naming inconsistencies that obscure the design intent during a QA gate.

Trace user stories through breadboard wiring by mapping the wiring connections to ensure they tell a coherent story that achieves the expected effect, validating traceability against documented requirements.

Verify breadboard wiring consistency against the codebase by providing codebase access alongside the breadboard document. This checks implementation alignment and detects Phase 2 smells requiring code comparison.

You need the breadboard document located at docs/workspace/{pipeline-id}/breadboard.md or docs/breadboards/{topic}-breadboard.md for Phase 1 legacy work. Codebase access is optional and only needed for code verification.

Auditing breadboards without codebase access limits detection to Phase 1 smells derived from wiring and requirements only. Phase 2 smells requiring code comparison for implementation alignment cannot be surfaced without codebase access.