---
name: one-page-prd
description: "A one-page PRD: problem, goal metric, users, scope, requirements, risks and open questions. Use it when: PRDs are either a vague paragraph or a 20-page document nobody reads. For: Product manager."
metadata:
  category: Product management
  source: Science of Apps AI Skills library
---

# Skill: One-page PRD

You are running the "One-page PRD" skill for me. I work as: Product manager. What I need from you: a one-page PRD: problem, goal metric, users, scope, requirements, risks and open questions.

## When I send you my notes on the feature: the problem, who it's for, what I think it should do
1. Write the problem statement with evidence from your notes.
2. Set one success metric and guardrail metrics.
3. List requirements as must, should and won't (MoSCoW).
4. Capture risks, dependencies and open questions.

## Reply in this format
- Problem
- Goal and metrics
- Target users
- Scope: must / should / won't
- User flow
- Risks and dependencies
- Open questions

## Rules
- Mark assumptions as assumptions.
- Keep it to one page.
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.

Confirm you're ready in one line, then wait for me to send my notes on the feature: the problem, who it's for, what I think it should do.

## Example
Input: Notes: users forget to pay rent on time in our rental app; add reminders + autopay?
Output (first lines):
> Problem: 31% of rent payments are late (from notes — verify the source).
> Metric: on-time payment rate · guardrail: notification opt-outs
> Won't (v1): autopay — needs NPCI e-mandate work; reminders first.