About pm-the-docs
A skill that helps documentation teams frame and shape new docs work before drafting. It guides decisions about audience, product stage, scope, content type, placement, prerequisites, and when to seek a docs PM decision.
Key features
- 01Frame audience, product stage, and purpose
- 02Choose content type and information placement
- 03Assess cross-repository scope
- 04Separate confirmed facts from inference
- 05Identify when to escalate to a docs PM
Use cases
- 01Scoping a new documentation page or launch
- 02Choosing prerequisites and placement for a page
- 03Checking whether work spans multiple product repositories
- 04Escalating unclear scope or product-stage decisions
Install
Copy the command and run it in a terminal.
npx skills add https:/After installing, type/pm-the-docsin Claude Code to confirm it loaded.
Bundled filesreference/write-the-docs-checklist.mdreference/universe-lookup.md
Details
From the project READMEPM the docs
Backs the Frame and Shape stages of the "Write the docs" checklist (mirrored in reference/write-the-docs-checklist.md) — the audience, product-stage, and cross-cutting scope calls a docs PM would normally make before drafting starts.
When to invoke
- Starting a new docs page or launch and need to state the product stage, audience, and "why" before drafting (Frame).
- Deciding content type, IA placement, or prerequisites for a page (Shape).
- Judging whether a launch spans multiple product repos (CLI, Auth, migrations, platform, …) — see reference/universe-lookup.md.
- Unsure whether a docs question is self-serve or needs a docs PM's sign-off.
Not for drafting content itself (see write-the-docs), restructuring existing pages (see edit-the-docs), running snippets (see test-the-docs), or docs-app architecture/IA placement mechanics (see ask-the-docs).
Reference files
| File | What's inside |
|---|---|
| reference/write-the-docs-checklist.md | Six-stage authoring checklist mirror |
| reference/universe-lookup.md | Cross-repo product lookup: capability gate, universe accelerator, OSS path |
Answering a scope/stage/audience question
- Read the relevant stage in reference/write-the-docs-checklist.md — its checkboxes state exactly what needs deciding.
- Read whatever context exists for the feature: the linked issue/project, the PRD, the shipped code or PR. When code and PRD disagree, the code wins for behavior claims.
- When scope may span services (CLI, Auth, migrations, Dashboard, platform, …), follow reference/universe-lookup.md capability gate before settling Frame/Shape; use universe only if accessible, otherwise the OSS path. Record which repos you searched.
- Answer the checklist's questions directly: product stage, audience and job-to-be-done, the one-line "why," content type, IA placement, prerequisites.
- Distinguish confirmed fact (stated in the ticket/PRD/code) from inference (your best read) — flag inference explicitly rather than presenting it as settled.
- If a decision is genuinely open at the org level (not a docs authoring call), say so and name who should decide instead of inventing an answer to look complete.
Self-serve vs. escalate
Self-serve when the checklist is clear, standards exist, and you already know the stage and audience.
Escalate to your docs team's PM when scope or stage is unclear, you need a review path, the bar is ambiguous, or the launch touches cross-cutting surfaces (quickstarts, API keys, tutorials, onboarding, platform concepts) — see the full "Ask the Docs PM" section in the checklist mirror.
Related skills
ask-the-docs— IA placement and docs-app architecture (Shape stage). Cross-repo product lookup lives here inuniverse-lookup.md, not inask-the-docs.write-the-docs— drafting once Frame/Shape are settledtest-the-docs— run snippets against a Docker-isolated local stack; verification reportedit-the-docs— restructure and improve existing pagesreview-the-docs— self-review and PR review stages