Quick Prd

Quick PRD Skill

Overview

This skill generates a structured Quick PRD from a feature idea or product context provided by the user. The output follows a strict format with four sections: Problem Context, Solution and Workflow, Strategic Principles, and Acceptance Criteria.

Input

Ask the user to provide:

• A description of the feature or product idea
• Any relevant customer context, personas, or real-life usage scenarios (optional but encouraged)
• Any known constraints or competitive context (optional)

If the user hasn't provided enough context, ask one focused follow-up question before proceeding. Don't ask more than one question.

Output Format

Ask the user whether they want the PRD as:

• A Markdown file (.md) — clean, portable, easy to paste into Notion/Linear/GitHub
• A Word document (.docx) — formatted, ready to share or print
• A PDF document (.pdf) - formatted, ready to share or print

If the user doesn't specify, default to Markdown.

For .docx output, read /mnt/skills/public/docx/SKILL.md before generating.

PRD Structure

Generate the PRD using the following four sections exactly. Always include today's date in MM/DD/YY format at the top.

Header

Create Quick PRD

# Updated: [today's date in MM/DD/YY]

1. Problem Context

• Write one paragraph, maximum 3 sentences
• Must be detailed and actionable enough to stand alone without additional context
• Lead with the most relevant customer persona (e.g. "Business owners need...") — never use real person or company names
• Articulate: what is the core problem, why now, and why this product deserves to win with this feature

2. Solution and Workflow

• Provide a comprehensive but concise overview of what the feature does and how it solves the user's pain points
• Walk through the user journey step by step: interface design, each interaction, usability improvements
• Anchor to a real-life usage narrative at a specific moment in time (e.g. "When Maria was onboarding her team on a Monday morning, she used [feature X] to...")
• Highlight what makes this solution unique or differentiated from competitors
• Apply the ICE framework: maximize Impact, Confidence, and minimize Effort
• Break into multiple paragraphs, each separated by a visible line break
• Do NOT write paragraph labels like "Paragraph 1" — just write the content with clear breaks between them

3. Strategic Principles

When deciding on the solution, apply at least one of the following strategic lenses (do not list them explicitly — weave them into the rationale):

• Economies of scale / cost advantages
• Network effects
• Counterpositioning against competitors
• Improving customer switching costs
• Brand strengthening
• Cornered resources (proprietary data, exclusive partnerships)
• Superior processes or proprietary workflows

4. Acceptance Criteria

• Define clear, detailed bullet-point acceptance criteria
• Each criterion must be: MECE, testable, measurable, and outcome-focused (not implementation-focused)
• Cover happy path, edge cases, error states, and any UX/performance expectations
• Write in plain language with a clear condition and expected result

Examples of good acceptance criteria:

• Search results display product name, image, and price in a consistent grid layout.
• Users can edit their first name, last name, email, and phone number from the Account Settings page.
• An error message reads "Sorry, something went wrong. Please try again." if the service times out.

UX Principles to Apply Silently

When designing the solution and workflow, incorporate these principles without mentioning them explicitly:

• Simplify relentlessly — remove unnecessary steps
• Seamless continuity — guide users naturally with minimal cognitive load
• Meticulous craftsmanship — every detail matters
• Delight with small memorable touches
• Balance functionality and beauty
• Consistent aesthetics across all touchpoints

Reminders

• Never mention the strategic or UX principles by name in the output
• Always use a real-sounding but fictional persona name in the Solution narrative
• Keep Problem Context to 3 sentences max — no exceptions
• Separate Solution paragraphs with visible line breaks
• Acceptance Criteria must be MECE and comprehensive