Cross-Functional Spec Review Checklist

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.