What problem does it solve? It turns scattered multi-turn discussions about requirements, project structure, and learning topics into persistent, versioned Markdown documents stored under .claude/repo/_self/, preventing decisions and analysis from being lost in conversation history. ## Core Features & Use Cases - Three discussion modes: Intent mode (requirements and design drafts), project-learning mode (status, concepts, comparisons), and basic-knowledge mode (concept notes), each producing only its allowed document types. - Versioned document system: Intent, design, status, compare, and concepts documents follow strict naming conventions with auto-incrementing versions; old versions are never overwritten. - Reference repository analysis: Reads external repos under .claude/repo/ and writes source-evidence-backed analysis documents into _self/_read/ with mandatory file path and line number citations. - Use Case: A user discussing how to design an auth module gets a structured intent document plus iterated design drafts (v1, v2...) with verbatim original requests, while a separate discussion analyzing the current codebase produces a status document and a comparison against open-source implementations. ## Quick Start Ask the assistant to help you organize your requirements or analyze a project module, for example by saying you want to clarify the goal and design of a new feature and have the discussion saved as structured documents.
