one-pager-prd_skill

Overview

This skill creates concise, decision-ready one-page PRDs to align stakeholders on problem, solution, users, success metrics, scope, and constraints. It speeds approvals and reduces back-and-forth by forcing clarity and measurable goals. Use it to scope initiatives before detailed design or to pitch features to leadership.

How this skill works

The skill guides you through a five-step workflow: gather context, choose one-pager vs PRD format, draft the one-pager, validate quality against a rubric, and review with stakeholders. Output is a 1–2 page spec with core sections: problem, solution, users, goals & metrics, scope (in/out), constraints, and open questions. It also offers patterns, guardrails, and templates to keep specs scannable and actionable.

When to use it

• Proposing a new feature or product and seeking quick approval
• Scoping an initiative for resource allocation or planning
• Capturing requirements for engineering handoff or cross-functional work
• Pitching an idea to leadership or aligning sales/marketing
• Documenting decisions and assumptions before detailed design

Best practices

• Lead with a specific, data-backed problem statement (why now?)
• Describe the solution at a high level — what, not how
• Include measurable metrics with baselines and timebound targets
• State crisp in-scope and out-of-scope boundaries; separate MVP vs future phases
• List constraints and open questions to surface risks and dependencies

Example use cases

• One-page pitch for a bulk-edit feature to reduce power-user churn
• PRD for a medium-complexity feature (MVP vs v2 phasing)
• Quick spec to align PM, design, and engineering before kickoff
• Executive one-pager emphasizing business impact and resource needs
• Internal tool spec focused on efficiency gains and adoption metrics