Documentation Strategy
Documentation levels and types (README, architecture, API, runbooks), keeping docs current and discoverable.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill documentation-strategygit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/engineer/engineer-toolkit/skills/documentation-strategy ~/.claude/skills/documentation-strategyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Documentation Strategy Planning documentation so engineers can find what they need. ## Context You are planning documentation for a project or team. Multiple levels serve different needs. ## Domain Context - **README**: First thing people read; quick start - **Architecture**: How system is organized; key decisions - **API Docs**: How to use services; generated from schema - **Runbooks**: How to respond to alerts; specific procedures - **ADR**: Why we chose this tech/approach; decisions recorded - **HOWTO**: Step-by-step guides; "how do I deploy?" ## Instructions 1. **README**: Installation, basic usage, links to more docs 2. **Architecture**: System diagram, component responsibilities, data flows 3. **API**: Schema-driven docs; keep in sync automatically 4. **Runbooks**: One per alert; decision trees for diagnosis 5. **ADR**: Decisions recorded; future maintainers understand why 6. **Keep Current**: Outdated docs are worse than no docs 7. **Searchable**: Good naming, cross-links, table of contents ## Anti-Patterns - Documentation in people's heads; knowledge walks out - Scattered docs; team can't find them - Out-of-date docs; misinformation spreads - Too much prose; too little examples - No diagrams; hard to visualize architecture - No maintenance plan; docs decay ## Further Reading - Diátaxis documentation framework (Procida) - Google Technical Writing Course - Write the Docs community
Details
- Skill name
documentation-strategy- Repository
- sethdford/claude-skills
- Path
engineer/engineer-toolkit/skills/documentation-strategy/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the Documentation Strategy skill do?
Documentation levels and types (README, architecture, API, runbooks), keeping docs current and discoverable.
How do I install the Documentation Strategy skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Documentation Strategy popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Documentation Template
48sethdford/claude-skills
Generate structured documentation templates for components, patterns, or guidelines within a design system.
Data Storytelling
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Loading States
48sethdford/claude-skills
Design loading, skeleton, and progressive content reveal patterns.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.