plan

Topics in the source

• Plan
• When to use
• Overview
• Complexity triage
• Rules for both routes
• Boundaries

User enters plan mode or asks to plan before implementing User asks to create a workspace, design doc, ADR, or task breakdown User asks to resume, review, or amend an existing design or workspace User asks to integrate workspace artifacts into durable storage Planning must always take less time than implementation. The effort scales with complexity, never the other way around. This file holds the triage: assess the complexity, then load exactly one route file. Never load both. Assess the work against three triggers, in order: 1. Resuming? Root CLAUDE.md has an ## Active workspaces entry → load complex-plan.md and follow its Phase 0. 2. Multi-session scope? More than one session of work, more than 5 tasks, or a domain model worth tracing → full workspace: load complex-plan.md. 3. Hard-to-reverse decision? Persistence, protocol, public contract → that decision gets an ADR whatever the route; the route still follows trigger 2. On the small route an additive flag, a CLI option, or an output shape is a decision bullet, not an ADR. The small route writes an ADR only for persistence or a wire protocol, the small route's shortcut. Both pass the admission test in complex-plan.md. None of th

This is an excerpt. Refer to the complete source and its current requirements.