amigos — scenario names travel

Scenario names travel

This is the detail that makes everything traceable. Every scenario written in the amigos session gets a name — short, specific, drawn from the situation. That name travels through every artifact that touches this story.

AMIGOS              FLOW                FIGMA              API                  TEST                PR
concurrent-submit → concurrent-submit → marking-pane    → concurrent-submit  → concurrent-submit → concurrent-submit

One anchor, named once, traceable in both directions. When a test fails, you know exactly which specification the code violated. When a bug is filed, you trace it to the scenario that was missing or wrong. The scenario name keeps the chain intact from the amigos session to the production incident — and from the production incident back to the brief.

Resolution gate — Amigos to Pull

Enough to pull.

The story has its scenarios written and named. The trio agrees the scenarios cover the happy path and the edge cases that matter. The links to Epic, brief, wireframe states, API contract, and ADRs are all present.

Test: a developer who was not in the amigos session can pull this story, read it, and build it without asking a question.

Part Seven — Closing →