post-impl-docslisted

# Post-Implementation Documentation Skill Automatically update repository documentation to reflect code changes. This skill ensures that when code is implemented, the documentation stays in sync with the actual codebase. ## Variables | Variable | Default | Description | |----------|---------|-------------| | UPDATE_README | true | Update README.md for new features/APIs | | UPDATE_CHANGELOG | true | Add entries to CHANGELOG.md | | UPDATE_DOCS_FOLDER | true | Update files in docs/ that reference changed code | | UPDATE_DOCSTRINGS | true | Update inline docstrings for changed functions/classes | | CHANGELOG_FORMAT | conventional | `conventional`, `keep-a-changelog`, `simple` | | COMMIT_DOCS | true | Commit documentation changes with code | ## Instructions **MANDATORY** - Follow the Workflow steps below in order. Do not skip steps. 1. Analyze what code changes were made (git diff) 2. Determine documentation impact 3. Update README if new features/APIs added 4. Update CHANGELOG with change summary 5. Scan docs/ folder for references to changed symbols 6. Update inline docstrings for modified functions/classes ## Red Flags - STOP and Reconsider If you're about to: - Update documentation without understanding the code changes - Add CHANGELOG entries for trivial changes (typos, formatting) - Update README for internal implementation details - Modify docstrings without verifying the behavior changed **STOP** -> Review the diff -> Understand the impact -> Then document ## Wor