docs-output

What problem does it solve?

Centralizes and enforces a consistent, modular organization for project documentation while creating append-only session progress records to preserve task-level traceability and collaboration history. It prevents scattered files under docs/ and eliminates ambiguous progress tracking by requiring per-module documents and date/session-based progress files managed by a script.

Core Features & Use Cases

• Manage module documents under docs/{module}/ with create and update operations, ensuring one file per feature and kebab-case naming.
• Create and append session progress records under docs/progress/{YYYY-MM-DD}/{username}_{hash}.md with git user attribution, timestamps, decisions, changed files, and remaining todos.
• Validate directory health, list module and recent progress, and archive progress older than N days to progress/archive/YYYY-MM/.
• Use cases: generating deliverable documentation at Deliver stage, recording session summaries after feature development or bug fixes, and validating documentation structure before release.

Quick Start

Use the docs-output skill to create or update a module document and append a session progress entry via the docs_manager CLI.