Curriculum

The AI PRD

Still inside the 88 percent craft theme, this chapter owns the artifact the report calls the differentiator from classic PM: the AI PRD must name risks, guardrails, and success metrics up front because the system is non-deterministic (Produ

1. 05.01

   The AI PRD

   You write an AI PRD that names the failure modes, the guardrails, and a three-level success definition, outcome, trajectory, and step, because a non-deterministic system cannot be specced like a deterministic one.
2. 05.02

   Roadmap around an evaluable slice

   You sequence the roadmap around the smallest slice you can actually evaluate, using a v0-v1-v2 discipline to resolve capability uncertainty by shipping rather than by more planning.
3. 05.03

   Write the spec after the demo

   You invert the order, demo first and spec after, then negotiate the 80 percent wall and the written production boundary that separates a throwaway prototype from what engineering owns.
4. 05.04

   From agreed spec to shipped

   You turn an agreed spec into a dated delivery plan with milestones, cut scope when the date is at risk, and announce the slip yourself before it announces itself.
5. 05.05

   Launch readiness and the narrative

   You run the launch readiness gate, then turn positioning into a messaging hierarchy and write the actual words on the release page, the demo script, and the customer comms.