Software delivery documentation dispatcher. Routes to the correct document standard for the artifact being written or reviewed, following the BRD -> PRD -> FRD/NFR -> TRD -> SAB -> SAD -> ADR lifecycle. Use whenever creating, reviewing, auditing, or improving any software project document. Trigger on: "write a BRD", "PRD", "product requirements", "functional spec", "FRD", "TRD", "NFR", "document review", "business requirements", "acceptance criteria", "developer handoff", "write an ADR", "architecture decision", "write a SAD", "solution architecture", "traceability", "epic", "user story", "feature list", "roadmap", "release plan", "prioritize features", "MoSCoW", "RICE", "runbook", "postmortem", "go-live checklist", or any request to produce or improve a software delivery document.
Write, review, and organize project documentation, including READMEs, guides, product comparisons, release notes, code comments, TSDoc/JSDoc, and public API reference. Use when editing documentation or comments, writing comparison content, reviewing a diff that touches them, or deciding what to document and where it belongs.
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
Rising+4 new adopters in 4 weeks
42 projects use a version of this
41k21d agoReviewMountCreate a free account to mount
Guidance for structuring Ark documentation using the Diataxis framework. Use this skill when creating new docs, deciding where content belongs, reviewing documentation PRs, or restructuring existing documentation.
4387mo agoReviewMountCreate a free account to mount
Create and update documentation articles for the Heym platform. Use when adding docs pages, writing reference articles from summaries, or when the user provides an outline for a new article.
1.7k7mo agoReviewMountCreate a free account to mount
Go documentation conventions: godoc comments, package docs, testable Example functions, deprecation notices, doc links, and project docs (README, CHANGELOG, llms.txt). Use when: "add godoc", "document this package", "write doc comments", "add examples to docs", "deprecate a function", "write a README", "update the changelog", "improve the docs". Not for: commit messages (git-commit), code style (go-coding-standards).
8531d agoReviewMountCreate a free account to mount
Use when writing a README, documenting a module or component, recording a decision, or deciding whether something needs explaining at all. Also when documentation has drifted from the code.
Documentation suites: audit or plan docs, write with Diátaxis/Info Mapping/EPPO, review for scannability and AI-readiness. Trigger for doc planning, writing, or review. Broken links are doc-link-verifier, not this.
Redaction de documentation technique: README, docs API, guides, changelogs. Use when writing or improving technical documentation, README files, or developer guides.
Rédiger de la documentation technique ou utilisateur. À utiliser pour commencer une fonction ou un script, pour expliquer comment un module fonctionne, pour créer un tutoriel, une notice d'utilisation, ou compléter le README.
After finishing a non-trivial code change (new feature, bug fix, refactor, architecture decision), update the project's root documentation files — CLAUDE.md, SPEC.md, README.md, or whatever equivalent already exists — so a future agent or teammate can open the project cold and understand what it does, what changed, and how to continue. Create these files if none exist. Use at the end of a change, not before or during. Do not use for trivial edits (typo fixes, one-line tweaks, formatting) or read-only/exploratory work with no code change. Works in any conversation language, English or French included — write the documentation in whatever language the existing docs use, or the user's language if there's no precedent.
Write clear, comprehensive documentation with language-specific patterns. Use when writing docstrings, module docs, README files, API references, or architecture decision records. Covers Python, TypeScript, Go, and Rust documentation conventions. Do NOT use for code style (use vibe skill).
Writes and updates docs, READMEs, runbooks, specs, and ADRs. Use when documenting a feature, writing a runbook, updating README/setup docs, or recording decisions. Do not use for competitive research briefs or for code comments that only restate the next line.
Write and maintain technical documentation. Trigger with "write docs for", "document this", "create a README", "write a runbook", "onboarding guide", or when the user needs help with any form of technical writing — API docs, architecture docs, or operational runbooks.
Keeps long-lived project docs from rotting: gives existing docs constitution, map, status, and history roles and wires AGENTS.md or CLAUDE.md to them, plus onboarding guides, CodeTour walkthroughs, domain glossaries with ADR handoff, and growth-log entries. Use when docs drift from code, agents lose context, deleted files come back, you need a project map, status page, delete-zone, or decision log, onboard to a repo, write a starter CLAUDE.md, create a .tour file, define terms in CONTEXT.md, or record lessons. Sub-skills: codebase-onboarding, code-tour, context-and-decisions, growth-log.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
tiago-oliveira-caSkill
