document-feature

Generate module documentation from feature artifacts and git diffs.

1|Updated Apr 22, 2026

Search Tags:#documentation #ai workflow #knowledge capture #module docs #git diff #feature artifacts

Ready to run

npx skills add https://github.com/AbsolutSystems/absolutpowers --skill document-feature-absolutsystems

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: document-feature
Source: https://github.com/AbsolutSystems/absolutpowers/tree/main/claude/skills/document-feature
Command: npx skills add https://github.com/AbsolutSystems/absolutpowers --skill document-feature-absolutsystems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns completed feature work into lasting module documentation, so teams do not lose implementation knowledge after delivery.

Core Features & Use Cases

Feature-to-doc transformation: Reads planning artifacts, task files, and git diffs to infer what a feature changed.
Module-level documentation: Creates or updates docs/modules/{module}.md so each module has a current, durable reference.
Merge with existing knowledge: Preserves unrelated documentation while updating only the parts affected by the feature.
Use Case: After a feature ships, ask it to harvest the work into module docs so a new developer can understand the module before extending it.

Quick Start

Give the skill the path to the feature's planning or tasks file and ask it to update the affected module documentation from the feature artifacts and git diff.

Frequently Asked Questions about document-feature

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate module documentation from git diffs and feature artifacts after shipping?▼

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.

Can I update existing module docs without losing unrelated documentation?▼

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.

What is the best way to capture implementation knowledge from a completed feature for future reference?▼

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.

Do I need to provide file-to-module mapping when consolidating feature artifacts into documentation?▼

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.

How does freshness metadata work when updating module documentation from feature changes?▼

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.