docs

Plan and implement documentation changes for a codebase.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CuongTran69/tramthientra --skill docs-cuongtran69
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: docs
Source: https://github.com/CuongTran69/tramthientra/tree/main/.augment/skills/docs
Command: npx skills add https://github.com/CuongTran69/tramthientra --skill docs-cuongtran69

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and individuals scope, plan, and implement documentation work so that documentation is targeted, maintainable, and aligned with audience needs rather than ad-hoc or incomplete.

Core Features & Use Cases

  • Discovery & Scoping: Restate the documentation need (Feynman Echo), clarify audience, and define what is in/out of scope.
  • Investigation: Map existing docs in the codebase, surface dependencies and hidden complexity, and identify gaps and outdated content.
  • Options & Decisioning: Compare formats and maintenance approaches, recommend paths (e.g., auto-generated reference vs manual guides), and optionally produce a spec for implementation.
  • Use Case: Run a documentation audit for a repository to decide whether to add user guides, inline examples, or an auto-generated API reference and produce an implementation plan.

Quick Start

Start by invoking the docs skill with the explore command to map scope, audience, and preferred formats before asking for an implementation plan.

Frequently Asked Questions about docs

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

FAQPage Schema
How do I plan and scope documentation changes for a codebase?

A documentation audit maps existing docs across repositories, surfaces hidden complexity, and identifies outdated content. It compares formats and maintenance approaches, such as auto-generated references versus manual guides, to recommend a clear implementation path.

How do I decide between auto-generated API references and manual user guides?

Run a documentation audit to map existing docs, surface dependencies, and identify content gaps. The audit compares formats and maintenance approaches to recommend implementation paths and optionally produces a spec for adding user guides or auto-generated references.

What is audience analysis in the context of documentation strategy?

Yes, this approach applies to documentation maintenance workflows across repositories and components. It helps identify outdated content, gaps, and hidden complexity, ensuring ongoing documentation remains aligned with audience needs and maintainable over time.

Can I create an implementation spec for new documentation?

Documentation planning applies to audits, audience and format discovery, guide and API reference planning, and maintenance workflows across repositories. It satisfies requirements for scope analysis, gap identification, optional spec creation, and delegation to research tooling.