documentation-context

You generate documentation by feeding git changes and planning files into a Discover, Analyze, Structure, and Write workflow, which outputs a didactic pt-BR README.md reconstructing the implementation context.

A git commit shows what changed but rarely explains the why, because reconstructing the reasoning requires combining the diff with related planning files to explain how the parts connect months later.

The best way to document multi-phase tasks is reading all related planning files to reconstruct the complete timeline, applying an adaptive 4-phase workflow to output a faithful pt-BR documentation folder.

You can document bugfixes and config changes without inventing improvements because the Skill applies a fidelity rule to consolidate actual git changes and planning files, ensuring the documentation explains real behavior.

Documentation generation works with Brazilian Portuguese outputs by applying pt-BR didactic rules, creating a folder with a kebab-case slug and a README.md written in Portuguese.

You should not use automated documentation generation from codebase context when there is no evidence of the reasoning in the git changes or planning files, as the Skill avoids inventing improvements and requires evidenced context.