2

    PRD Writer

    by Indy Agent

    From feature idea to 10-section engineering-ready PRD — with anti-goals, success metrics, and open questions.

    Updated Jun 2026
    Security scanned

    $9

    · or 45 credits

    30-day refund guarantee

    Secure checkout via Stripe

    Included in download

    • Draft engineering-ready PRDs from rough feature notes
    • Identify missing success metrics and risks in project specs
    • Instant install

    Sample input

    I need a PRD for an in-app notification system. Users should be able to receive notifications when their reports are ready, when someone mentions them in a comment, and when a task is assigned to them.

    Sample output

    PRD: In-App Notification System

    Status: Draft Last updated: June 2026


    1. Overview

    A notification system that alerts users to relevant in-product events (report completion, mentions, task assignments) without requiring them to check back manually. Reduces time-to-awareness for time-sensitive actions.


    2. Problem Statement

    The problem

    Users miss important events (completed reports, task assignments, mentions) because they have no in-product notification mechanism. They rely on email or manual polling.

    Evidence

    TBD — to be defined before engineering kickoff. Suggested: support ticket volume for "I didn't know X happened", DAU data showing return visit patterns.

    Impact of not solving

    Users continue to miss time-sensitive events, increasing reliance on email and reducing in-product engagement.


    3. Goals & Success Metrics

    Goals

    • Reduce time between event and user action for high-priority notifications
    • Increase daily active usage by surfacing relevant in-product events

    Anti-goals

    • This is NOT a marketing notification system (no promotional content)
    • This is NOT an email notification replacement
    • This is NOT a real-time chat or messaging system

    Success metrics

    | Metric | Baseline | Target | Timeframe | |---|---|---|---| | Notification open rate | — (new) | >40% | 30 days post-launch | | Time-to-action on task assignments | TBD | -30% | 60 days post-launch |

    [... continues for all 10 sections ...]

    About This Skill

    A Claude Code skill that produces complete Product Requirements Documents. Gathers problem statement, goals with measurable metrics, user use cases, solution overview, scope (in and out), constraints, risks, and open questions. Enforces anti-goals. Flags all assumptions explicitly. Install SKILL.md in your Claude Code project. Triggers on: "write a PRD", "spec this out", "I need a PRD for", "help me write requirements", "document this feature". The 10-section structure it produces: Overview · Problem Statement · Goals & Success Metrics · Users & Use Cases · Proposed Solution · Scope (in/out) · Constraints & Dependencies · Risks · Open Questions · Appendix What it enforces: - Every goal must have a measurable metric - Anti-goals are required (the section most PRDs skip) - At least one risk identified - Assumptions flagged explicitly when writing from incomplete input What's included: SKILL.md + installation instructions.

    Reviews

    No reviews yet - be the first to share your experience.

    Only users who have downloaded or purchased this skill can leave a review.

    Frequently Asked Questions

    More Premium Skills