Plan with evidence — pstack Part 2

Two narrated lessons (about 11 and 13.5 minutes, 1920×1080) adapted from Lauren (@poteto), "The Complete Guide to pstack Pt. 2": rigorous planning is not a longer document, it is a process that turns uncertainty into evidence through research, prototypes, and contracts.

• Source article: https://x.com/poteto/article/2097732320606507506 (Lauren, @poteto, "The Complete Guide to pstack Pt. 2")
• Version 1: pstack-plan-with-evidence-v1.mp4 (H.264 + AAC, captions burned in), subtitles pstack-plan-with-evidence-v1.srt, transcript ../../transcripts/pstack-plan-with-evidence-v1.txt
• Version 2: pstack-plan-with-evidence-v2.mp4 (H.264 + AAC, selectable captions and chapter markers), subtitles pstack-plan-with-evidence-v2.srt, transcript ../../transcripts/pstack-plan-with-evidence-v2.txt

Both are independent educational adaptations, not official pstack productions. The narration is synthetic (Microsoft Aria in version 1, Microsoft Andrew in version 2), and the examples are explanatory, not benchmark results.

Version 1 — Plan with evidence (11:18)

Twenty short chapters that follow the article's argument, from why a longer plan is not a better plan to making planning produce evidence.

1. 00:00 A longer plan is not a better plan.
2. 00:34 Two failures. Two missing inputs.
3. 01:03 Ask for the problem, not your diagnosis.
4. 01:36 Build a shared mental model.
5. 02:14 Separate facts from hypotheses.
6. 02:45 Start where the user starts.
7. 03:19 Four documents. Four different jobs.
8. 03:55 A prompt sequence that compounds context.
9. 04:27 Avoid both planning traps.
10. 04:58 Make alternatives comparable.
11. 05:34 Skills are tools. Playbooks are workflows.
12. 06:03 A five-phase architecture loop.
13. 06:34 Sketch a usable contract, not an essay.
14. 07:09 Judge candidates. Then synthesize.
15. 07:42 Let implementation challenge the design.
16. 08:16 Now write the execution plan.
17. 08:51 Migration means preserving a contract.
18. 09:23 Choose the workflow for the uncertainty.
19. 10:00 The plan is convincing. Nothing ran.
20. 10:35 Make planning produce evidence.

Version 2 — Plan Through Code (13:31)

Opens on a 40-step plan that has never run, then moves through four stages shown in an on-screen tracker: understand, specify, explore, and execute. The article's prompts appear word for word. It ends with a three-question self-check. Example timings, code, and plan rows are illustrative and labelled as such on screen.

1. 00:00 A plan that proves nothing
2. 00:20 Where this comes from
3. 00:51 The lesson in four moves
4. 01:14 Two ways agents fail
5. 01:44 Supervising someone smarter
6. 02:14 Ask it to restate the problem
7. 03:00 /how and /why
8. 03:41 /teach and /recall
9. 04:25 Plan in code, not prose
10. 05:08 One document, one job
11. 06:08 Prompts that compound
12. 06:50 Measure a hundred times
13. 07:14 Skills vs playbooks
14. 07:46 Prototyping is planning with code
15. 08:31 /architect: five phases
16. 09:41 Evidence the design is wrong
17. 10:21 Okay, but I really want a plan
18. 11:05 Pick the workflow for the job
19. 12:00 Check yourself
20. 12:56 Plan with evidence