Which chapters involve code or technical setup?
Only Chapters 11–13. They cover a local AI environment (VS Code and Claude Code), automation with Python scripts and MCP servers, and building a command center with Next.js. Chapters 1–8 need no coding.
Three chapters involve code or technical setup: Chapters 11, 12, and 13. The book states that no coding is required for Chapters 1–8.
Chapter 11: Local AI Environment
You set up VS Code as a local command center and work with Claude Code. This moves your AI work from a browser chat onto your own computer, next to your project files. See What is Claude Code, and do I need it? and How do I set up VS Code as a local AI workspace?
Chapter 12: Automation and Integration
This chapter covers Python scripts and MCP servers. The book treats these scripts as "disposable software": small tools you create for a job and replace when your needs change. MCP servers connect your AI assistant to other tools and data. See What is an MCP server?
Chapter 13: Building Your Command Center
You build your own command center with Next.js.
The other chapters
- Chapters 1–8 are the core workflow, from building your Project Brain to weekly reports. No coding.
- Chapters 9–10 are the conclusion and key terminology.
- Chapter 14 is the Gemini supplement.
Should you do the technical chapters?
They're optional. The core chapters stand on their own. The technical chapters are where the book's estimated automation savings come from, so they're worth a look once the basics feel comfortable. See How much time can an AI-powered PMO save?
For a gentle introduction, read Local AI setup is too complicated and Building a command center sounds too technical.
Last updated
Still need help?
Or browse more The Book articles, all help topics, or the blog.