humanify-docslisted

Write Markdown docs that read like a person wrote them, or rewrite AI-generated docs so they do — short sections, lists and tables where they help, minimal formatting, no code unless the doc is genuinely technical. For a broad topic (a codebase overview, how a system works end-to-end) it researches with a small, budgeted set of subagents and writes the doc itself. Updating an existing doc keeps its style by default and only adds what was asked. Use when: "humanify this doc", "/humanify-docs", "make this README readable", "write docs for X", "this doc reads like AI, fix it", "document how Y works", "add X to the docs", "update the docs for Y", "write a README for this project", or the user hands over a Markdown file and wants it human-friendly. Every rule here yields to what the user asks for.
Xenoneqq/claudified-workflow · ★ 1 · Data & Documents · score 74

Install: claude install-skill Xenoneqq/claudified-workflow

# humanify-docs Produce Markdown that a developer can read top to bottom without effort. Either write a new doc or rewrite an existing one. The output is a file on disk, never a push. The rules below are defaults. If the user asks for something else in the prompt — more examples, code snippets, a specific structure, a longer style — do what they ask. Detail that is only needed sometimes lives next to this file. Read a reference when its step says so, not before: | File | Read it when | |---|---| | `references/doc-kinds.md` | You have picked the doc kind in Step 0. Shape, section order and checklist per kind. | | `references/readme.md` | The doc kind is a README. Its own shape, sections and checklist. | | `references/subagent-research.md` | The request is a broad doc (Step 5) or an update that needs research (Step 4). Outline, agent budget, models, prompts. | ## Step 0 — Classify the request Four shapes. Decide which before doing anything else. | Shape | Signal | How it runs | |---|---|---| | Rewrite one doc | A file path or pasted Markdown, "make this readable" | You alone. Read, restructure, rewrite in place. | | Update one doc | An existing doc plus new information to add, "add X to the docs" | Keep its style. Agents confirm the old and research the new (Step 4). | | Write one narrow doc | A topic you can cover from a few files | You alone. Read what you need, write. | | Write a broad doc | A codebase overview, a cross-cutting system, "how X works" spanning many area