What is lean-doc-generator?

A documentation skill for creating or reviewing technical documents, architecture decision records, sprint files, and AI context files using a defined documentation standard. An ADR records why an important technical decision was made.

Use it to write or update architecture notes, ADRs, changelogs, sprint records, project context files, and documentation migrations.

It keeps project knowledge in the appropriate place and prevents documentation from duplicating details that belong in code or tests.

lean-doc-generator — Skill for Claude Code by aldianriski: A documentation skill for creating or reviewing technical documents…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/aldianriski/lean-flow/lean-doc-generator

Any agent

npx skills add aldianriski/lean-flow --skill lean-doc-generator

Clone the repo

git clone --depth 1 https://github.com/aldianriski/lean-flow

Made for: Claude Code.

Or install lean-flow, the plugin that ships this one along with the rest of its 15 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/aldianriski/lean-flow/lean-doc-generator.svg)](https://agentmods.dev/skills/aldianriski/lean-flow/lean-doc-generator)

Your own site

<a href="https://agentmods.dev/skills/aldianriski/lean-flow/lean-doc-generator"><img src="https://agentmods.dev/badge/skills/aldianriski/lean-flow/lean-doc-generator.svg" alt="Measured on agentmods" height="20"></a>

Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,125 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00121	$0.04125
Opus 5	$0.00060	$0.02063
Sonnet 5	$0.00024	$0.00825
Haiku 4.5	$0.00012	$0.00413

Measured 6d ago against content hash 2bddd96089f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

lean-doc-generator scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/lean-doc-generator/SKILL.md · 127 lines

How it starts

The opening of the file, as written. The whole thing — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Lean Documentation Generator

Generate high-signal docs against a canonical format. Every template ships inside this skill under ${CLAUDE_SKILL_DIR}/; the standard itself is cited from the versioned spec/STANDARD.md — the SSOT for every standard-owned rule (ADR-023).

Golden Rule

Never generate documentation that explains HOW something works.

Explains…	Goes in…
HOW it works	code (comments, types, tests)
WHY decided	a rich ADR — one file at `docs/adr/ADR-NNN-<slug>.md` (`templates/ADR.md.template`); add a row to the `docs/DECISIONS.md` index. Offer one only when it clears STANDARD §4's three-part bar
WHERE things live	`docs/architecture/overview.md` or `README.md`
WHAT changed	`CHANGELOG.md` (root)
Unsure	code

Bundled + cited assets (load these — do not free-generate)

spec/STANDARD.md — the standard (cited, not bundled — ADR-023): 4 Laws, Core Files + line caps, ownership header, ADR format, HOW filter, checklist. Read first.
${CLAUDE_SKILL_DIR}/templates/*.md.template — the canonical format per doc type. The template IS the format — read the matching one before writing any core doc.
templates/DESIGN.md.template — OPTIONAL · frontend-only · non-core. Offer only for UI/frontend repos wanting a shared design-system / token contract (docs/DESIGN.md or repo's design dir). Never auto-create; never include in core doc generation.
templates/RESEARCH.md.template — occasional · create-lazily. A decision-driving question → options · evidence · recommendation that feeds an ADR (desk synthesis; distinct from /prototype = design you must feel, and /council = a hard fork). → docs/research/<slug>.md.
templates/deployment-guide.md.template + templates/deployment-rollback.md.template — occasional · create-lazily. Deploy flow, env matrix, migration order, health checks, release verification (guide) + rollback process + verification (rollback) — operational, like setup. /release-patch bumps + stops before push; these own the push/deploy/rollback steps. → docs/deployment/deployment-guide.md / docs/deployment/rollback-guide.md.

Read the full file on GitHub · 127 lines

Files

What ships with it

38 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

6d ago First seen · 127 lines · 121 tokens per session scan A 2bddd96089f1

Subscribe to this mod's changes

lean-doc-generator is a skill published in the GitHub repository aldianriski/lean-flow (5 stars, last pushed 7d ago), licensed MIT. It adds 121 tokens to every session and 4,125 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens