- A disappointing output has one of four root causes — under-specification (Module 2), context overload (Module 1), wrong feature/model (Module 1), or stale configuration (Module 5) — and diagnosis means checking which one actually applies, since similar symptoms can come from different causes with different fixes
- Fixing one bad response in-conversation and promoting a fix to persistent configuration are two different steps; recurrence of the same correction across conversations is the signal that it's time for the second step
- Workflow optimization promotes shared context, format, and verification steps into Projects, Skills, and standing instructions — proactively, not just after a recurring correction becomes a problem
- This module doesn't introduce new frameworks — it teaches when to invest in the frameworks from Modules 1, 2, 3, 5, and 6
Key Takeaways
Estimated time: 3 minutes