Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
rysweet avatar

Documentation Writing

  • 297 installs
  • 70 repo stars
  • Updated July 26, 2026
  • rysweet/amplihack

documentation-writing is a Claude Code skill that authors READMEs, API references, runbooks, and contributor guides for the amplihack project so operational docs stay aligned with code.

About

documentation-writing is a Claude Code skill focused on producing and maintaining amplihack project documentation. It guides agents to write clear README files, API references, operational runbooks, and contributor guides that capture setup steps, service contracts, and day-two procedures. The skill is meant to keep documentation accurate as repositories change, reducing onboarding friction and preventing drift between implemented behavior and published instructions. Developers reach for documentation-writing when amplihack modules need structured docs for new endpoints, environment setup, release steps, or contribution workflows instead of ad hoc markdown patches.

  • Structures README and API reference sections
  • Keeps setup and configuration steps current
  • Documents endpoints, events, and error semantics
  • Writes contributor and operations runbooks
  • Aligns prose tone with amplihack conventions

Documentation Writing by the numbers

  • 297 all-time installs (skills.sh)
  • +1 installs in the week ending Jul 26, 2026 (Skillselion tracking)
  • Ranked #452 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/rysweet/amplihack --skill documentation-writing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs297
repo stars70
Last updatedJuly 26, 2026
Repositoryrysweet/amplihack

How do you keep amplihack docs accurate as code changes?

Author clear READMEs, API references, runbooks, and contributor guides for amplihack so setup, contracts, and operational steps stay accurate as code changes.

Who is it for?

Developers maintaining the amplihack repository who need consistent README, API, runbook, and contributor documentation.

Skip if: Teams seeking generic blog posts or marketing copy unrelated to amplihack setup and operational docs.

When should I use this skill?

The user asks to document amplihack setup, APIs, runbooks, or contribution steps after code changes.

What you get

Updated README files, API reference pages, operational runbooks, and contributor guides aligned to amplihack code.

  • README updates
  • API reference pages
  • runbooks

Files

SKILL.mdMarkdownGitHub ↗

Documentation Writing Skill

Purpose

Creates high-quality, discoverable documentation following the Eight Rules and Diataxis framework. Ensures all docs are properly located, linked, and contain real runnable examples.

When I Activate

I load automatically when you mention:

  • "write documentation" or "create docs"
  • "document this feature/module/API"
  • "create a README" or "write a tutorial"
  • "explain how this works"
  • Any request to create markdown documentation

Core Rules (MANDATORY)

The Eight Rules

1. Location: All docs in docs/ directory 2. Linking: Every doc linked from at least one other doc 3. Simplicity: Plain language, remove unnecessary words 4. Real Examples: Runnable code, not "foo/bar" placeholders 5. Diataxis: One doc type per file (tutorial/howto/reference/explanation) 6. Scanability: Descriptive headings, table of contents for long docs 7. Local Links: Relative paths, context with links 8. Currency: Delete outdated docs, include update metadata

What Stays OUT of Docs

Never put in `docs/`:

  • Status reports or progress updates
  • Test results or benchmarks
  • Meeting notes or decisions
  • Plans with dates
  • Point-in-time snapshots

Where temporal info belongs:

  • Test results → CI logs, GitHub Actions
  • Status updates → GitHub Issues
  • Progress → Pull Request descriptions
  • Decisions → Commit messages

Quick Start

Creating a New Document

# [Feature Name]

Brief one-sentence description of what this is.

## Quick Start

Minimal steps to get started (3-5 steps max).

## Contents

- [Configuration](#configuration)
- [Usage](#usage)
- [Troubleshooting](#troubleshooting)

## Configuration

Step-by-step setup with real examples.

## Usage

Common use cases with runnable code.

## Troubleshooting

Common problems and solutions.

Document Types (Diataxis)

TypePurposeLocationUser Question
TutorialLearningdocs/tutorials/"Teach me how"
How-ToDoingdocs/howto/"Help me do X"
ReferenceInformationdocs/reference/"What are the options?"
ExplanationUnderstandingdocs/concepts/"Why is it this way?"

Workflow

Step 1: Determine Document Type

Ask: What is the reader trying to accomplish?

  • Learning something new → Tutorial
  • Solving a specific problem → How-To
  • Looking up details → Reference
  • Understanding concepts → Explanation

Step 2: Choose Location

docs/
├── tutorials/     # Learning-oriented
├── howto/         # Task-oriented
├── reference/     # Information-oriented
├── concepts/      # Understanding-oriented
└── index.md       # Links to all docs

Step 3: Write with Examples

Every concept needs a runnable example:

# Example: Analyze file complexity
from amplihack import analyze

result = analyze("src/main.py")
print(f"Complexity: {result.score}")
# Output: Complexity: 12.5

Step 4: Link from Index

Add entry to docs/index.md:

- [New Feature Guide](./howto/new-feature.md) - How to configure X

Step 5: Validate

Checklist before completion:

  • [ ] File in docs/ directory
  • [ ] Linked from index or parent doc
  • [ ] No temporal information
  • [ ] All examples tested
  • [ ] Follows one Diataxis type

Navigation Guide

When to Read Supporting Files

reference.md - Read when you need:

  • Complete frontmatter specification
  • Detailed Diataxis type definitions
  • Markdown style conventions
  • Documentation review checklist

examples.md - Read when you need:

  • Full document templates for each type
  • Real-world documentation examples
  • Before/after improvement examples
  • Complex documentation patterns

Anti-Patterns to Avoid

Anti-PatternWhy It's BadBetter Approach
"Click here" linksNo context"See auth config"
foo/bar examplesNot realisticUse real project code
Wall of textHard to scanUse headings and bullets
Orphan docsNever foundLink from index
Status in docsGets staleUse Issues/PRs

Retcon Documentation Exception

When writing documentation BEFORE implementation (document-driven development):

````markdown

[PLANNED - Implementation Pending]

This document describes the intended behavior of Feature X.

Planned Interface

# [PLANNED] - This API will be implemented
def future_function(input: str) -> Result:
    """Process input and return result."""
    pass

````

Once implemented, remove the [PLANNED] markers and update with real examples.


---

**Full reference**: See [reference.md](./reference.md) for complete specification.
**Templates**: See [examples.md](./examples.md) for copy-paste templates.

Related skills

FAQ

What documentation types does documentation-writing cover?

documentation-writing covers READMEs, API references, runbooks, and contributor guides for amplihack. The skill keeps setup instructions, contracts, and operational steps documented as code changes.

When should teams invoke documentation-writing for amplihack?

Teams should invoke documentation-writing when amplihack setup, API contracts, or operational steps change and published docs risk drifting from the repository. The skill targets accurate maintainer-facing documentation.

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.