pm-the-docs

Suporte à decisão de Docs-PM para o processo de autoria "Write the docs" — faz chamadas de escopo sobre público, estágio e questões transversais durante as etapas Frame e 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

  1. Read the relevant stage in reference/write-the-docs-checklist.md — its checkboxes state exactly what needs deciding.
  2. 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.
  3. Answer the checklist's questions directly: product stage, audience and job-to-be-done, the one-line "why," content type, IA placement, prerequisites.
  4. Distinguish confirmed fact (stated in the ticket/PRD/code) from inference (your best read) — flag inference explicitly rather than presenting it as settled.
  5. 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.

Related skills

Mais skills de supabase

studio-e2e-tests
supabase
Escreva e execute testes E2E com Playwright para o Supabase Studio. Use quando solicitado.
studio-best-practices
supabase
Práticas recomendadas de React e TypeScript para o Supabase Studio. Use ao escrever ou revisar componentes do Studio — abrange nomenclatura booleana, estrutura de componentes,…
docs-content
supabase
Escreva, edite, organize e revise conteúdo da Supabase em qualquer lugar em apps/docs — guias, explicações, tutoriais, entradas de solução de problemas, documentação de referência e…
studio-mock-api-tests
supabase
Testes de componentes para o Supabase Studio que simulam requisições de API na camada de rede com MSW. Use ao escrever ou revisar um teste de componente que exercita um React…
studio-ui-patterns
supabase
Padrões de UI do design system para o Supabase Studio. Use ao construir ou atualizar páginas, formulários, tabelas, gráficos, estados vazios, navegação, cartões, alertas ou side…
react-hook-form
supabase
Uso correto do React Hook Form em qualquer lugar do monorepo — fluxo de dados, assinaturas, reset, estado dirty, inputs numéricos e regras de inputs controlados. Carregar isto…
studio-queries
supabase
Convenções do React Query para busca de dados no Supabase Studio. Use ao escrever ou revisar hooks de consulta, hooks de mutação ou chaves de consulta em apps/studio/data/ —…
studio-testing
supabase
Estratégia de testes para o Supabase Studio. Use ao escrever testes, ao decidir se uma alteração precisa de testes e de qual tipo, ao extrair lógica de componentes para…