What problem does it solve? Project documentation often drifts from reality: READMEs list commands that no longer work, manuals describe screens that changed, and changelogs read like raw commit logs. This Skill produces documentation grounded in the actual code, configuration, git history, and real UI screens, so every claim in a document has been verified before it is written. ## Core Features & Use Cases - Audience-targeted documents: Creates READMEs for newcomers, PT-BR task-oriented user manuals with screenshots, technical documentation with architecture views and ADRs, dated changelogs in user language, SOPs, glossaries, and full project wikis. - Verification before writing: Reads pom.xml/package.json, build scripts, git log, and real screens first; executes every install/run command before documenting it and marks anything untestable as "not verified". - Robust wiki mode: Generates a navigable wiki/ folder with a write-ahead manifest, human-edit collision protection, secret scanning, page size caps, and drift detection via git hash-object so stale pages are flagged instead of silently aging. - Use Case: After closing a release, ask for the changelog and a README check; the Skill reads the real git history between tags, writes a dated Adicionado/Corrigido/Alterado block in user language, and runs the README's build command to confirm it works. ## Quick Start Use the docs-projeto skill to write the README and generate the changelog for this project from the real code and git history.
