tl-docs-create

Generate project documentation from code using SSOT-driven templates.

Updated Feb 14, 2026
One-click install
npx skills add https://github.com/toddlevy/tl-agent-skills --skill tl-docs-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tl-docs-create
Source: https://github.com/toddlevy/tl-agent-skills/tree/main/skills/tl-docs-create
Command: npx skills add https://github.com/toddlevy/tl-agent-skills --skill tl-docs-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Documentation often drifts from code and requires manual drafting, leading to onboarding friction and maintenance overhead. This skill provides SSOT-driven templates to generate consistent READMEs, AGENTS.md, CHANGELOG, and a structured docs layout directly from the codebase.

Core Features & Use Cases

  • SSOT-driven templates enable automatic generation of documentation from source code, ensuring alignment with the codebase.
  • Supports standard templates for README, AGENTS.md, CHANGELOG, and a docs/ folder, with optional references, scripts, and assets for enrichment.
  • Ideal for new projects or when documenting an undocumented codebase, enabling rapid setup and consistent documentation across teams.

Quick Start

Generate standardized documentation from your codebase using SSOT-driven templates.

Frequently Asked Questions about tl-docs-create

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

FAQPage Schema
How do I generate a README and CHANGELOG directly from my source code?

You can generate a README and CHANGELOG directly from source code using SSOT-driven templates. This approach automatically extracts project details and renders structured documentation, ensuring your files stay aligned with the codebase.

What is the best way to create structured documentation for an undocumented codebase?

The best way to document an undocumented codebase is applying SSOT-driven templates that automatically render a structured docs layout. This rapidly establishes consistent project documentation without manual drafting overhead.

Does SSOT-driven documentation generation track when files were last updated?

Yes, SSOT-driven documentation generation explicitly satisfies last-updated tracking. It automatically embeds source attribution and metadata into the rendered templates to maintain historical accuracy.

Can I include optional scripts and references when generating project docs?

Yes, you can include optional references, scripts, and assets for enrichment when generating project docs. The template-driven system integrates these supplementary files into the final structured documentation output.

Why does manually drafted documentation drift from the actual codebase?

Documentation drifts from the codebase because manual drafting requires continuous synchronization that is often neglected. SSOT-driven templates solve this by automatically generating docs from source code, ensuring alignment.