Skip to content
Back to skills

Playbook Technical Writing Docs Overhaul

ASecurity

Sorted page types, working pipelines, and freshness signals readers trust again.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
ai-agentsrustgobashgitsecurity

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add aniruddhaadak80/skills --skill playbook-technical-writing-docs-overhaul --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Playbook Technical Writing Docs Overhaul?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Playbook Technical Writing Docs Overhaul
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aniruddhaadak80-playbook-technical-writing-docs-overhaul/badge)](https://www.skillsdirectory.com/skills/aniruddhaadak80-playbook-technical-writing-docs-overhaul)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: playbook-technical-writing-docs-overhaul
description: "Sorted page types, working pipelines, and freshness signals readers trust again."
---
# Playbook: Overhaul a neglected docs site

> Sorted page types, working pipelines, and freshness signals readers trust again.

**Track:** 🗺️ Technical Writing · **Domain:** Journey Playbooks · **Level:** journey · **~80 min**

**Who this is for:** Technical Writers, Developer Advocates, Engineers Who Document, Content Leads

## When to Use This Skill

Sorted page types, working pipelines, and freshness signals readers trust again.
Use it whenever a matching task appears in conversation — the agent loads these instructions on demand.

## Journey Steps

1. Step 1 — Sort docs into types readers recognize: start with "Label every existing page: learning-journey, task-recipe, information-lookup, or theory"
2. Step 2 — Run docs through the same pipeline as code: start with "Store docs beside code or in sibling repo with same review gates"
3. Step 3 — Write changelogs users read: start with "Categorize: Added / Changed / Fixed / Breaking / Security only"
4. How it fits together: Sort types before rewriting anything. Half the mess resolves itself once modes separate.

### Referenced Skills

- `docs-systems-diataxis-audit`
- `docs-systems-docs-as-code-workflow`
- `dev-content-changelog-users-read`

## Commands

**Install all referenced skills**
```bash
npx skills add aniruddhaadak80/skills --skill docs-systems-diataxis-audit && npx skills add aniruddhaadak80/skills --skill docs-systems-docs-as-code-workflow && npx skills add aniruddhaadak80/skills --skill dev-content-changelog-users-read
```

---

Part of [aniruddhaadak80/skills](https://github.com/aniruddhaadak80/skills) · Browse all at https://skills.sh/aniruddhaadak80/skills

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…