document-feature

Module documentation generation reads planning files, task files, and git diffs to infer feature changes. It consolidates completed implementation artifacts into durable docs, ensuring new developers can understand module updates before extending the codebase.

Yes, merging existing module docs preserves unrelated documentation sections. The update process intelligently targets only the parts affected by the completed feature, maintaining current module references while integrating new source changes.

Capturing implementation knowledge transforms post-delivery feature artifacts into durable module documentation. By reading planning files and source changes, it prevents teams from losing implementation context after shipping, creating a lasting reference for future development.

Yes, accurate file-to-module mapping is required to consolidate feature artifacts into documentation. This mapping ensures planning files, task files, and git diffs correctly update the corresponding module documentation file.

Freshness metadata tracks the update status of the module documentation file. When consolidating feature artifacts and git diffs, it appends metadata to the updated module docs, indicating the current state and recency of the documentation.