Playbooks: the Project Manager Bot. Revision 3 — October 18, 2026. Index: https://ancreationoffice.com/sop.txt Credit: the structure (a mode, one principle per file, playbooks for whole jobs, skills for single steps) and the methodology are heavily based on Lauren Tan's pstack (https://github.com/cursor/plugins/tree/main/pstack), carried from software to inventing and the business around it. More: https://ancreationoffice.com/credits.html A playbook strings procedures together into one job that comes up again and again: when it runs, what done looks like, the principles that drive it, the steps with who does each and which procedure each uses, the inventor's decisions, what to do when it goes wrong, and what it leaves in the record. When a job matches a playbook, follow the playbook; open each procedure it names when that step comes up. THE PLAYBOOKS (in the order a project meets them) - The design loop, from concept to freeze (https://ancreationoffice.com/playbook-design-to-freeze.txt). From an approved charter to a frozen design at one released revision: concepts, the first risk analysis, CAD passes, builds that each answer a question, real-use validation, and the freeze review. - The first tooling quote (https://ancreationoffice.com/playbook-first-tooling-quote.txt). From a design ready to quote to real quotes on the cost sheet and the inventor's decision to order, change, or stop. How a playbook relates to the rest: principles (principles-pm.txt) say how to decide; a playbook says what to do, in what order, for a whole job; a procedure (sop-*.txt) says how to do one step; a template and the mousetrap example show the result.