Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From user-manual
Generate individual documentation sections using a writing agent (Step 2 of 4)
npx claudepluginhub danielrosehill/user-manual-pluginHow this command is triggered — by the user, by Claude, or both
Slash command
/user-manual:generate-partsThe summary Claude sees in its command listing — used to decide when to auto-load this command
# Task 2: Generating Documentation Parts Now that the documentation folder structure is in place, please generate the individual documentation sections. ## Agent Instructions Engage a documentation writing agent and provide it with the following context: The instructions provided to the documentation generation subagent should explain why this distinction and context are being provided: Private documentation may contain feature outlines, specific code snippets, or credentials that would otherwise never be included in public documentation. ## Formatting and Tone of Voice Guidelines Rel...
/generate-documentationGenerates or rewrites technical documentation for a file or folder, creating README.md, architecture docs, and Mermaid diagrams.
/documentGenerates documentation for features, APIs, components, specs, or guides with sections like overview, architecture, examples, and diagrams, saving Markdown files to .claude/logs/documents/.
Share bugs, ideas, or general feedback.
Now that the documentation folder structure is in place, please generate the individual documentation sections.
Engage a documentation writing agent and provide it with the following context:
The instructions provided to the documentation generation subagent should explain why this distinction and context are being provided: Private documentation may contain feature outlines, specific code snippets, or credentials that would otherwise never be included in public documentation.
Relative to public-facing documentation, the documentation can be written in a friendlier tone of voice while still adhering to best standards of technical documentation writing.
Assuming you know my name, you can include it in the documentation, such as "Homebox Backup Script Operation User Manual for Daniel's Attention," and reference the date of creation.
The documentation should be generated in an organized and planned manner:
docs/sections/ directory with clear, numbered filenames (e.g., 01-introduction.md, 02-installation.md, etc.).docs/assets/ and reference them from the relevant sections.Once all sections have been generated, confirm completion and provide a summary of the sections created. Await the next task instruction for PDF compilation.