🗺️ Technical Writing · Journey Playbooks
Playbook: Overhaul a neglected docs site
Sorted page types, working pipelines, and freshness signals readers trust again.
journey~80 minTechnical WritersDeveloper AdvocatesEngineers Who Document
Journey Steps
- 1Step 1 — Sort docs into types readers recognize: start with "Label every existing page: learning-journey, task-recipe, information-lookup, or theory"
- 2Step 2 — Run docs through the same pipeline as code: start with "Store docs beside code or in sibling repo with same review gates"
- 3Step 3 — Write changelogs users read: start with "Categorize: Added / Changed / Fixed / Breaking / Security only"
- 4How it fits together: Sort types before rewriting anything. Half the mess resolves itself once modes separate.
Commands
Install all referenced skills
$ 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-readTags
#playbook#journey#technical-writing