What problem does it solve? Technical documentation often reads well but is quietly wrong, filled in from what usually goes in a section rather than from what the sources actually say. This Skill turns available context — a session, a diff, a spec, or files you point at — into a Markdown document where every claim is traced to a source, gaps are stated openly, and conflicts are documented instead of silently resolved. ## Core Features & Use Cases - Evidence-based writing pipeline: harvests sources into a context map, classifies every fact by evidence level (confirmed, inferred, unknown, conflicting) and relevance, then validates the draft against the sources rather than against itself. - Nine discovered document templates: architecture, technical overview, feature, API reference, ADR, runbook, investigation, project report, and generic — selected by matching your goal and audience, with new templates picked up automatically from the assets folder. - Interactive and auto modes: interactive mode gates on plan approval for documents others will read; auto mode self-reviews and writes straight through for fast captures of work you just did. - Use case: after finishing a feature or debugging session, ask it to document what was built — it produces a grounded feature doc or investigation report with diagrams and tables only where they carry real relationships. ## Quick Start Ask the assistant to document the feature you just implemented as a Markdown file using the available session context and changed files.
