documenter

Update PRD files and generate atomic Git commits for completed development tasks.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/elihuvillaraus/skills --skill documenter-elihuvillaraus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: documenter
Source: https://github.com/elihuvillaraus/skills/tree/main/documenter
Command: npx skills add https://github.com/elihuvillaraus/skills --skill documenter-elihuvillaraus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of updating project documentation and crafting precise Git commit messages after development tasks are completed, ensuring consistency and saving developer time.

Core Features & Use Cases

  • PRD Updates: Automatically marks completed user stories in PRD documents.
  • Progress Tracking: Appends detailed status updates to a progress.md file.
  • Atomic Commits: Creates individual, well-formatted Git commits for each completed story, including documentation changes.
  • Use Case: After a sprint, this Skill ensures all completed features are reflected in the PRD and commit history, providing a clear audit trail.

Quick Start

Invoke the documenter skill after receiving 'RALPH_DONE' signals for a completed priority group.

Frequently Asked Questions about documenter

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

FAQPage Schema
How do I automate PRD updates and Git commit messages after a development sprint?

This workflow automates PRD updates and Git commit messages by tracking completed user stories and generating atomic Git commits. It appends status updates to progress files, ensuring accurate commit messages for feature development.

What is an atomic Git commit and how does it relate to project documentation?

An atomic Git commit bundles a single completed user story with its project documentation updates. This mechanism tracks story completion and ensures the commit history accurately reflects feature development and PRD modifications.

How do I track story completion in a progress.md file during feature development?

Track story completion by automatically appending detailed status updates to a progress.md file. This logging mechanism records development progress and ensures accurate commit messages during feature development.

Do I need an existing Git repository to automate documentation and commits?

Yes, automating documentation and commits requires access to a Git repository and codebase. The workflow needs this development context to update PRD files, log progress, and generate accurate atomic commits for completed stories.

When should I automate project documentation and commit generation in my workflow?

Automate project documentation and commit generation after completing a development sprint or priority group. Invoking the process upon receiving a done signal ensures completed features are accurately reflected in the PRD and commit history.

Can I generate Git commits for individual user stories without manual entry?

Yes, you can generate well-formatted Git commits for individual user stories without manual entry. The workflow creates individual atomic commits for each completed story, automatically including the associated PRD and progress documentation changes.