pm-the-docs

Soporte de decisiones de Docs-PM para el proceso de autoría de "Write the docs": toma decisiones sobre audiencia, etapa y alcance transversal durante las etapas de Frame y 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

Más skills de supabase

studio-e2e-tests
supabase
Escribe y ejecuta pruebas E2E con Playwright para Supabase Studio. Úsalo cuando te lo pidan.
studio-best-practices
supabase
Prácticas recomendadas de React y TypeScript para Supabase Studio. Úsalo al escribir o revisar componentes de Studio: cubre la nomenclatura de booleanos, la estructura de componentes,…
docs-content
supabase
Redacta, edita, organiza y revisa contenido de Supabase en cualquier parte de apps/docs: guías, explicaciones, tutoriales, entradas de solución de problemas, documentos de referencia y…
studio-mock-api-tests
supabase
Pruebas de componentes para Supabase Studio que simulan solicitudes de API en la capa de red con MSW. Úsalo al escribir o revisar una prueba de componentes que ejercite un React…
studio-ui-patterns
supabase
Patrones de UI del sistema de diseño para Supabase Studio. Úsalo al crear o actualizar páginas, formularios, tablas, gráficos, estados vacíos, navegación, tarjetas, alertas o barra lateral…
react-hook-form
supabase
Uso correcto de React Hook Form en cualquier parte del monorepo — flujo de datos, suscripciones, reset, estado sucio, entradas numéricas y reglas de entradas controladas. Cargar esto…
studio-queries
supabase
Convenciones de React Query para la obtención de datos en Supabase Studio. Úsalo al escribir o revisar hooks de consulta, hooks de mutación o claves de consulta en apps/studio/data/ —…
studio-testing
supabase
Estrategia de pruebas para Supabase Studio. Úsala al escribir pruebas, al decidir si un cambio necesita pruebas y de qué tipo, al extraer lógica de componentes en…