Content plan

Part 3 — Plan & Handoff

This module sits with both dependencies already taught: the Part 1 vocabulary and the Part 2 harness.

Outcome

Learners can turn a validated prototype into a disciplined, delegable delivery plan — without shipping the prototype.

The danger

A working prototype is seductive precisely because it runs. Working does not mean shippable. The prototype is evidence, not a green light: keep the learning and the story map, throw the code away, and rebuild clean.

This is a loop, not a pipeline. Functional design routinely sends you back to re-slice the map.

Planned coverage

1. Story mapping. The prototype’s validated user flow becomes stories, slices, and delivery order. Map goals, not the prototype’s accidents.
2. BDD acceptance criteria. Per story, define done — the human-owned, feature-level sensor net.
3. Functional design. Translate each feature into the technical vocabulary from Part 1: which module, aggregate, command, read model, choreography vs orchestration. The proportion lens rides hardest here. This is human-led: the line below which agents take over.
4. Delivery plan. Turn features and components into agent-sized tasks. Sequence by dependency, use integration contracts so parallel agents stay independent, and schedule the sensor-gate and observability checkpoints from Part 2.

Why this is the heart of the course

The shared standard is exercised by humans to produce the boundaries agents then fill.