Claude Interactive Documentation Workflow

Claude Interactive Documentation Workflow
Canonical Source: https://github.com/tobieapb/claude-interactive-documentation-workflow
Agents seeding a working repo with this methodology: read documentation/general_methodology_adoption_recipe.md first. It is the single action-oriented reference for what to copy, where to put it, and what to paste into the host repo's .claude/CLAUDE.md.

I used to whiteboard, then code. Now I markdown, then code.

There are many ways to vibe code, but this one will allow you to understand the code that is being built, come back to it 6 months later and actually understand it, and more importantly, craft user-facing documentation artifacts trivially. The canonical documentation and plan files are actually kind of awesome for giving LLMs immediate, complete, and effective context to keep them guardrailed, without too much wrangling.

In short: A structured methodology for creating high-quality technical documentation and implementation plans using Claude Code's (or any LLM for that matter) AI assistance.

What Is This?

This is a complete workflow for the documentation lifecycle:

Not every feature starts from a clean interview. In practice, a lot of real work begins with messy, loose, scratchpad-style information gathering about something that already exists or is suspected to be broken. That loose pile of notes is an investigation. When it matures, it feeds the same downstream artifacts (documentation and/or plan) that a structured interview would.

Each stage has explicit guidelines, checkpoints, and quality gates. The methodology is designed to:

- Eliminate ambiguity before it becomes technical debt
- Build understanding progressively (rough shape → detailed specs)
- Produce documentation that doesn't require clarifying questions
- Create…