Generate end-user manuals and reference guides for ERP modules. Use when the user asks to document a feature, write a user manual, or sync a reference guide. This skill is explicitly separate from doc-architect (which manages AI guidance docs like AGENTS.md).
Superpowers plugin: MUST be active for all work using this skill. Use throughout the entire build pipeline — design decisions, code generation, debugging, quality checks, and any task where it offers enhanced capabilities. If superpowers provides a better way to accomplish something, prefer it over the default approach.
Create end-user manuals and reference guides. This is not for AI instruction documents. Do not edit or generate AGENTS.md or other AI guidance files when this skill is used.
End-user manuals and system guides are required deliverables for any SaaS application. Features are not considered complete until:
Documentation Standards (MANDATORY): ALL manual files must follow strict formatting rules:
/manuals/ by moduleskills/doc-standards.md for complete requirementsActivate when the user asks to:
Before writing a single word, analyze these four pillars:
docs/plans/**/*.md to understand business intent and user stories.database/schema/*.sql to identify constraints, triggers, and auto-generated fields.src/ or app/ to see actual UI behavior and data flow.docs/* for style guides or technical debt notes.Every guide must include:
Conceptual Overview
Procedural Steps
Technical Reference
Edge Cases
Use these standards to design manuals for SaaS web apps. Summarize and adapt per module.
Organize manuals with a clear hierarchy:
/manuals/ using subdirectories for major areas./public/user-manuals.php based on the standard template (e.g., skeleton.php).user-manuals.php?manual=pos-system./public/user-manuals.php exists./manuals/ exists and contains subdirectories./manuals/AGENTS.md describing the directory purpose and what each subfolder should contain.read_file, list_dir, grep_search, file_search, create_file, apply_patch/public/user-manuals.php scaffolding/manuals/<section>/ and included dynamically by user-manuals.php| Skill | Relationship |
|---|---|
sdlc-user-deploy | SDLC-standard user documentation (User Manual, Training Materials, Ops Guide). This skill produces in-app PHP manuals; sdlc-user-deploy produces SDLC-standard markdown docs. Use both for complete coverage. |
sdlc-planning | SRS defines features that need manuals. Use SRS feature list as manual scope checklist. |
sdlc-design | API docs and SDD inform technical reference sections in manuals. |
sdlc-testing | Test cases reveal edge cases that should be documented in manuals. |
doc-architect | Generates AI guidance docs (AGENTS.md). NOT end-user manuals — use this skill instead. |
feature-planning | Specs include Documentation Impact notes that define manual requirements. |
spec-architect | Specs are "manual-ready" — use their workflow descriptions for manual content. |
project-requirements | User workflows and business rules inform manual content. |
report-print-pdf | Report export patterns — reference in manual sections about report features. |
| Need | Skill |
|---|---|
| In-app PHP manual for ERP module | manual-guide (this skill) |
| SDLC-standard user manual (markdown) | sdlc-user-deploy |
| AI guidance docs (AGENTS.md) | doc-architect |
| Project README and CLAUDE.md updates | update-claude-documentation |
| Feature spec with documentation impact | spec-architect or feature-planning |
Back to: Skills Repository Related: sdlc-user-deploy | doc-architect | feature-planning Last Updated: 2026-02-20