What problem does it solve? Software repositories often lack clear developer documentation, leaving new contributors to reverse-engineer the technology stack, architecture, and change workflows from raw code. This Skill studies a repository's actual implementation and produces verified, progressively structured developer documentation under docs/. ## Core Features & Use Cases - Evidence-Based Repository Analysis: Inspects dependency manifests, entrypoints, schemas, CI configuration, and tests to build a verified model of the product, technology stack, architecture, domain, and main flows, classifying every finding as confirmed, inferred, unconfirmed, or contradictory. - Progressive Documentation Design: Proposes an adaptive docs/ structure with a clear entrypoint, Technology at a Glance, Architecture at a Glance, repository map, and goal-based reading paths for onboarding, feature work, and debugging. - Approval-Gated Authoring: Stops at a documented proposal gate before writing any project documentation, then validates links, commands, and claims against implementation evidence. - Use Case: Point the Skill at a legacy repository with scattered READMEs; it inventories the real stack, proposes a docs/index.md structure with reading paths, and after approval writes verified onboarding and architecture documentation. ## Quick Start Analyze this repository and create a developer documentation proposal with verified technology and architecture summaries before writing any docs.
