pm-the-docs

Docs-PM 의사결정 지원 도구로, "Write the docs" 작성 프로세스에서 Frame 및 Shape 단계 중 대상 독자, 단계, 교차 범위 결정을 지원합니다…

npx skills add https://github.com/supabase/supabase --skill pm-the-docs

PM 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).
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) or docs-app architecture/IA placement mechanics (see ask-the-docs).

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.
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-content 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.