docs-output

Manage modular project documentation and session progress records via CLI.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/YuluoY/nimis --skill docs-output
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs-output
Source: https://github.com/YuluoY/nimis/tree/main/skills-en/docs-output
Command: npx skills add https://github.com/YuluoY/nimis --skill docs-output

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about docs-output

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

FAQPage Schema
How do I organize project documentation by module and track session progress?

You can organize project documentation by module and track session progress by structuring files under docs/{module}/ and appending session records to docs/progress/{YYYY-MM-DD}/{username}_{hash}.md. This enforces modular docs and append-only session tracking for feature development traceability.

What is the best way to record daily session progress for bug fixes using git?

The best way to record daily session progress for bug fixes is using session-based files named by git username and session hash. These append-only records capture timestamps, decisions, changed files, and remaining todos to preserve task-level traceability and collaboration history.

How do I validate my docs directory structure before a software release?

You validate your docs directory structure before a software release by running a CLI validate operation. This checks directory health, enforces module-by-module organization under docs/{module}/, and verifies kebab-case naming for feature documents.

Can I automate archiving old session progress records by month?

Yes, you can automate archiving old session progress records by month. The CLI archive operation moves progress files older than N days to progress/archive/YYYY-MM/, keeping your active progress directory clean while preserving historical session data.

Does this documentation management approach work without external dependencies?

Yes, this documentation management approach works without external dependencies. It relies solely on a CLI script to manage create, update, list, validate, progress, and archive operations for modular docs and session tracking within your software project.