Exercise: /init - Check readiness for TDD

---

Let's talk about how Claude Code works under the hood, because understanding this will help you use the /init command more effectively.

The sequence goes like this: you put in a prompt, then Claude talks to itself about the prompt. It has a tool called the todo manager, and it inserts tasks into the todo manager. When it's finished doing that, it loops over the tasks.

This "talk to itself about the prompt" phase is essentially Claude with tooling - it can call the todo manager. Then, when it's finished that initial thinking, the program loops over the tasks, picks the next task, and prompts Claude: "Here is a todo list task, please do this task." Claude then talks to itself about that task and performs it.

So when you run /init to check readiness for test-driven development, Claude is going through this exact process. It's analyzing your project structure, thinking about what's needed for TDD, creating tasks to check different aspects, and then systematically working through them.

Understanding this workflow helps you appreciate what's happening when Claude initializes your project for TDD - it's not just a simple scan, it's a thoughtful, systematic analysis of your codebase.