Agent skill · writing content · aiskillstore
human-docs-generator
Generates role-based human documentation (<1000 words per doc). Use when epics complete, breaking changes occur, or architecture decisions are made. Creates guides for developers, QA, DevOps, and business stakeholders.
Why this skill is useful
Generates role-specific documentation templates and processes that streamline communication for technical changes, which the AI wouldn't reliably create on its own.
What it needs
About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Human Docs Generator Skill Role Automatically generates and maintains role-specific documentation for humans when significant changes occur in the system. Purpose Transform complex AI state and technical implementations into simple, role-specific guides that humans can actually understand and use. Trigger Conditions Automatic Triggers ✅ Epic completed 🔧 Public API modified 🎯 New user feature deployed 💥 Breaking change introduced 🐛 Critical bug fixed 📊 5+ related tasks completed Manual Trigger Document Structure Files Maintained Generation Process 1. Gather Context 2. Extract Role-Relevant Info Frontend Developer Needs Component locations & hierarchy State management patterns Reusable components list Recent UI changes Backend Developer Needs API endpoint documentation Database schema changes Authentication flow Service dependencies End User Needs Screenshots with annotations Step-by-step guides Feature locations Common workflows 3. Transform to Human Format Rules for Human Docs 1. Max 1000 words per document 2. Diagrams over text (Mermaid.js) 3. Examples over explanations 4. Current state only (no history) 5. Quickstart focused 4. Generate Diagrams Component Tree (Frontend) API Flow (Backend) User Flow (End User) Document Templates Frontend Developer Template End User Template Quality Checks Before Publishing [ ] Under 1000 words? [ ] Has diagrams/screenshots? [ ] Includes quickstart? [ ] Examples provided? [ ] No technical jargon? [ ] Tested instructions work? Integration Input Events Output Events Anti-Patterns to Avoid ❌ Writing changelogs (just current state) ❌ Technical deep-dives (keep it simple) ❌ Walls of text (use bullets/diagrams) ❌ Assuming knowledge (explain everything) ❌ Version history (one living document) Success Metrics Reading time < 5 minutes Diagram-to-text ratio > 40% Quickstart success rate > 90% Human confusion tickets < 5% Doc update frequency = feature frequency
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/human-docs-generator