Product Management5.0 · 0 ratings

Cross-Functional Spec Review Checklist

Reviews a draft spec against a rigorous checklist spanning UX, data, edge cases, accessibility, and rollout safety.

Role-Based

Prompt

ROLE: You are a meticulous PM doing a final spec review before engineering kickoff, catching gaps now to save weeks later.

CONTEXT: Here is the draft spec to review: [SPEC_TEXT]. Target users: [USERS]. Platform(s): [PLATFORMS]. Risk profile: [RISK].

TASK — review the spec against each dimension and report gaps:
1. Problem & scope: Is the problem clear? Are non-goals stated? Is scope bounded?
2. UX completeness: Are empty, loading, error, and zero-data states covered? Edge cases and limits?
3. Data & analytics: Are success metrics defined and is the needed instrumentation specified?
4. Non-functional: performance, accessibility (WCAG), localization, privacy/compliance, security touchpoints.
5. Rollout & reversibility: feature flag, phased rollout, rollback plan, and migration of existing data/users.
6. Dependencies & open questions: unresolved decisions and external dependencies.

OUTPUT FORMAT: For each dimension: a status (Clear / Gap / Missing) and a specific note. End with a prioritized 'Must-fix before kickoff' list and a 'Nice-to-clarify' list.

CONSTRAINTS: Be specific — point to what's missing, don't just say 'add detail.' Treat unspecified error/empty states and missing rollback plans as must-fix. Do not pass a spec with undefined success metrics.

How to use this prompt

  1. 1

    Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.

  2. 2

    Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.

  3. 3

    Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.

Techniques in this prompt

Role-Based

Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.

Learn this technique

Recommended models

claudegpt-4ogemini

Build on this prompt

Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.

Open in Studio How to prompt AI correctly

More in Product Management

Pressure-Tested Product Requirements Document

Drafts a complete, engineering-ready PRD with problem framing, scope boundaries, success metrics, and explicit non-goals.

Read prompt

RICE Prioritization Scoring Engine

Scores and ranks a backlog using RICE with transparent assumptions, sensitivity flags, and a defensible recommendation.

Read prompt

Jobs-To-Be-Done Interview Synthesis

Turns raw user interview notes into JTBD job statements, forces of progress, and prioritized opportunity areas.

Read prompt

Quarterly Product Roadmap Narrative

Builds an outcome-driven quarterly roadmap organized by themes and bets, with confidence levels and dependencies surfaced.

Read prompt