What is generate-docs?

A documentation generator for software projects. It creates runbooks, architecture guides, architecture decision records, and incident-response playbooks from project information.

Use it to generate deployment procedures, architecture explanations and diagrams, records of major design choices, or incident procedures for different audiences.

It turns scattered technical details into documents people can use to operate the system, understand its design, record important choices, and handle failures.

generate-docs — Command for Claude Code by navraj007in

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.

Clone the repo

git clone --depth 1 https://github.com/navraj007in/architecture-cowork-plugin

Made for: Claude Code.

Or install architect, the plugin that ships this one along with the rest of its 48 skills, 63 commands, 19 agents, 7 MCP servers.

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/commands/navraj007in/architecture-cowork-plugin/generate-docs/github.svg)](https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/generate-docs)

Your own site

<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/generate-docs"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/generate-docs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/generate-docs"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/generate-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.00011	$0.01386
Opus 5	$0.00005	$0.00693
Sonnet 5	$0.00002	$0.00277
Haiku 4.5	$0.00001	$0.00139

Measured 11d ago against content hash 8af2f893c74d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

generate-docs 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 11d 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.

commands/generate-docs.md · 182 lines

How it starts

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

/architect:generate-docs

Trigger

/architect:generate-docs — generate all documentation modes (default).

/architect:generate-docs [mode:X] — generate one mode only.

/architect:generate-docs [modes:X,Y] — generate a named subset.

Modes

Mode	What it generates
`runbook`	Deployment & operational runbooks
`architecture`	Architecture guide with narrative + diagrams
`adr`	Architecture Decision Records for major choices
`incident`	Incident response playbooks

Examples:

/architect:generate-docs [mode:runbook]
/architect:generate-docs [modes:adr,incident]
/architect:generate-docs [mode:architecture] [audience:stakeholders]

When a [mode:...] or [modes:...] tag is present, generate only the named modes and skip all others. When absent, generate all modes.

Options

[non_interactive:true] — skip questions, derive from SDL and activity log
[audience:engineers|operators|stakeholders] — adjust technical depth

Purpose

Production systems need runbooks, architecture guides, and decision records. This command generates deployment procedures, C4 diagrams with narrative, Architecture Decision Records (ADRs) for why key choices were made, and incident response playbooks. Output is Markdown suitable for wikis (Notion, Confluence, GitHub wiki) or standalone.

Workflow

Phase	Steps
Setup	Step 1
Configuration	Step 2
Generation	Step 3 · Step 4
Completion	Step 5 · Step 6 · Step 7

Step 1: Read Context

ℹ️ CONTEXT LOADING: _state.json → SDL → activity log

Read:

_state.json for full project state (all completed commands)
SDL for architecture decisions
_activity.jsonl for deployment history and timelines
Existing docs in docs/ (to avoid duplication)
Scaffolded project structure (for runbook paths)

Read the full file on GitHub · 182 lines

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.

11d ago First seen · 182 lines · 11 tokens per session scan A 8af2f893c74d

Subscribe to this mod's changes

generate-docs is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,386 once invoked, about $0.0001 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 ai-agent architecture claude-code-plugin developer-tool scaffolding sdl

nyann:doctor

Run nyann's read-only hygiene + documentation audit on the current repo. Emits the same drift sections retrofit uses, but never offers remediation or writes to the filesystem. Use this on session start, in CI, or any time you want to sanity-check a repo without risking mutations.

thettwe/nyann · 61 tokens

nyann:retrofit

Audit an existing repo against a profile and fix what's drifted. Unlike doctor (read-only), retrofit detects missing hooks, misconfigured gitignore, documentation gaps, and non-compliant history, then offers to remediate via bootstrap. Idempotent — safe to re-run.

thettwe/nyann · 61 tokens

nyann:apply

Apply an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can change real cloud infrastructure. Re-runs the plan, shows it, confirms, then applies. Unmistakably opt-in: apply is never the default and destructive applies require a second explicit confirm. For IaC apply intent only (not "apply a…

thettwe/nyann · 85 tokens

generate-docs