## Core Concept A three-step Claude Code workflow where documentation is both planning artifact and verification mechanism: 1. **Plan first**: Claude writes a complete plan before any code changes 2. **Document after**: after implementation, update clear, well-named docs describing what was built 3. **Verify consistency**: Claude explicitly checks that the docs match the actual code The key is step 3: documentation is not just a record of intent (the plan) or outcome (post-implementation docs) — it is an active verification tool. When Claude checks docs against code, discrepancies reveal either incomplete implementation or documentation drift, creating a self-correcting loop. (Drew Wilson, Feb 2026.) ## Pipeline vs Loop - Pipeline: Plan → Code → Document (linear, one-way) - Loop: Plan → Code → Document → Verify → Fix (cyclical, self-correcting) The verification step is what makes it a loop. It could be a `/verify-docs` skill or a PreToolUse hook before `git commit`. ## Related Concepts - [[Plan-First Workflow Gates]] — supplies the planning phase - [[Test-Driven Document Quality]] — supplies the validation methodology - [[Self-Healing Git Workflow]]