Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIGitHub CopilotGitHub CopilotGemini CLIGemini CLI+20 more

    PRD Generator

    1

    Transform feature ideas into engineering-ready PRDs with Given/When/Then criteria and explicit non-goals.

    $9.99

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    0 installsSecurity scanned
    PRD Generator

    PRD Generator

    Example session with this skill installed

    Draft a PRD for adding a 'Password Strength Meter' to our signup page. It should help new users create more secure accounts. We're using React and want to avoid heavy libraries.

    • Read your context and instructions
    • Compiled the prd generator

    I have drafted a technical PRD for the Password Strength Meter. It focuses on client-side validation logic and clear visual feedback for new users while explicitly excluding server-side enforcement from this specific frontend task.

    Product Requirements Document: Password Strength Meter

    SectionDetails
    Problem StatementUsers are creating weak passwords that are vulnerable to credential stuffing. There is currently no feedback during signup to guide them toward secure choices, resulting in a 12% account recovery rate in the first 30 days.
    Target UserNew users during the onboarding/registration flow.
    User StoryAs a new user, I want to see the strength of my password in real-time so that I can ensure my account is secure before submitting the form.
    Acceptance CriteriaGiven I am on the signup page, When I type in the password field, Then a visual indicator (bar) should update its color and width based on complexity (Length, Symbols, Numbers, Mixed Case).
    Non-GoalsImplementing a backend password policy (handled by Auth API). Adding 'Have I Been Pwned' API checks. Password suggestion/generation features.
    Success MetricsMetric: Avg. entropy score of new passwords. Target: Increase by 20% within 30 days. Decision Rule: If entropy does not increase, UI feedback is deemed insufficient.
    Edge CasesEmpty state (no bar visible). Paste behavior (immediate recalculation). Mobile keyboard covering the meter.

    Next steps

    1. Review the 'Non-Goals' to ensure no backend work was secretly expected.
    2. Verify the complexity logic with the security lead.
    3. Pass the Acceptance Criteria to the QA team for test case scaffolding.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Create engineering-ready user stories with Given/When/Then acceptance criteria.Prevent scope creep by defining explicit non-goals for every feature.Define success metrics and rollback plans before development starts.Flag technical edge cases and open questions for engineering review.

    About this skill

    The problem

    Engineering teams often receive vague feature requests that lead to scope creep and misinterpretation. Without specific acceptance criteria and defined non-goals, developers waste time building the wrong thing or guessing at edge cases.

    What it does

    • Converts rough feature notes into engineering-ready specs with Given/When/Then acceptance criteria.
    • Defines explicit non-goals to prevent scope expansion during the build phase.
    • Establishes measurable success metrics and decision rules before a single line of code is written.
    • Flags technical edge cases and open questions instead of making silent assumptions.
    • Generates a structured rollout plan including feature flags and rollback triggers.

    Why this beats prompting it yourself

    General-purpose LLMs tend to write fluffy, prose-heavy product docs that lack technical rigor. This skill enforces a strict Given/When/Then format for user stories and requires explicit non-goals, ensuring the output is actually actionable for developers and QA engineers.

    Use cases

    • Turning a Slack thread or brainstorm session into a formal technical specification.
    • Defining MVP scope for a new product module while documenting out-of-scope items.
    • Standardizing PRD quality across a product team to reduce back-and-forth during grooming.
    • Scaffolding acceptance tests for QA automation based on the PRD output.

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 13 days ago

    • Passed all security checks, Safe to install

    Listed13 days ago

    What's inside

    Frequently Asked Questions