ClaudeSuperPower

documentation-strategy

Skill

Design and run a documentation system for a team or product. Use this skill when planning what to document, choosing a documentation tool, organizing existing docs, fixing stale documentation, designing a maintenance cadence, or scoping technical writing work. Triggers on documentation, docs, tech w

Install

git clone https://github.com/rampstackco/claude-skills.git ~/.claude/skills/documentation-strategy

What is documentation-strategy?

Design and run a documentation system for a team or product. Use this skill when planning what to document, choosing a documentation tool, organizing existing docs, fixing stale documentation, designing a maintenance cadence, or scoping technical writing work. Triggers on documentation, docs, tech writing, knowledge base, wiki, runbook, README, internal docs, doc audit, doc maintenance, stale docs, where do we document. Also triggers when the team is repeatedly answering the same questions or when onboarding takes too long.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~132 tokens of context used while enabled, before you invoke anything

Documentation

README · ~9 min read

Documentation Strategy

Decide what gets documented, where, by whom, and how it stays fresh. Stack-agnostic. Applies to internal team docs, product docs, runbooks, READMEs, and knowledge bases.


When to use

  • Setting up documentation for a new team or product
  • Auditing existing documentation
  • Fixing stale or scattered docs
  • Choosing a documentation tool or platform
  • Defining what gets documented and what doesn't
  • Establishing maintenance cadence

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.