Back to marketplace

Create PRD

Generates structured PRDs from feature request transcripts or plain-language descriptions.

Product Managementproduct-managementstandard
by AgentVoltv1.0.0Published 1y ago1 install
Free to sign up · every skill included with AgentVolt Pro

Before & after

Same prompt, same agent — the only difference is the skill.

Prompt“Turn this feature request into a PRD”
Beforegeneric AI agent
I can definitely help you write a PRD from a feature request. That's a useful way to clarify scope and get alignment across your team. To make a good PRD, I'll need to understand the request in detail. What's the feature trying to solve? Who asked for it, and what's the business context? Are there any competitive products doing something similar? What does success look like — what metric or outcome should this drive? Also, do you know what the technical constraints are, or should I research the codebase to understand what's feasible? PRDs usually include things like user flows, wireframes, acceptance criteria, dependencies, and timelines. How much of that detail do you have already? Should I also create Linear tickets for the dev team, or just the PRD document? And what's your timeline — when would you want this to start building?
Afterwith Create PRD
PRODUCT REQUIREMENTS DOCUMENT - API RATE LIMITING FEATURE

OVERVIEW
Title: Implement per-user API rate limiting
Priority: P1 (blocks 3 enterprise deals)
OwnedBy: Platform team
DueDate: September 15, 2026

BACKGROUND
Enterprise customers report API overages (4 per week avg). Current system has no per-user limits. Competitors Stripe and Twilio enforce rate limits at signup. Without this, we risk SLA breaches and support escalations.

GOAL
Enable fine-grained rate limiting: different tiers get different limits. Free: 100 req/min. Pro: 1000 req/min. Enterprise: custom. Block requests gracefully with 429 status code.

USER STORY
As an API consumer, I want to know my rate limit status (headers: X-RateLimit-Remaining) so I can build resilient applications.

ACCEPTANCE CRITERIA
1. Rate limits enforced per API key (not IP)
2. Limits reset hourly
3. Responses include X-RateLimit-Limit, X-RateLimit-Remaining headers
4. Dashboard shows current usage + historical trend
5. Email alert when usage hits 80% threshold
6. 48h grace period before hard enforcement (soft warning first)

TECHNICAL SCOPE
Implementation: middleware in API layer (Redis counter). Database: track per-key limits + overages. Metrics: Prometheus gauge for usage by tier.

DEPENDENCIES
• Redis cluster ops (existing)
• Dashboard UI team (2 days)
• Billing team (true-up logic)

NON-SCOPE
• Burst allowance (future)
• Cost reporting per endpoint

RISK: Enterprise customers may hit limits unexpectedly. MITIGATION: 48h soft warning + email.

About this skill

name: create-prd description: Use when Generates structured PRDs from feature request transcripts or plain-language descriptions.

Create PRD

Researches the actual codebase for accurate technical scoping before writing the PRD, and can optionally create the corresponding Linear project and issues.

What you get

  • A structured PRD document, optionally with Linear issues created.

Customize your output

  • Source transcript/description
  • whether to auto-create Linear issues.

Example output

A complete PRD with technical scoping pulled from the real codebase.

Best for

Product managers and founders turning requests into scoped specs.

SKILL.md preview

SKILL.md
---
name: create-prd
description: Use this skill when generating a structured PRD from a feature request transcript or a plain-language description.
version: 1.0.0
category: Product Management
author: AgentVolt
license: proprietary
tags:
  - product-management
  - standard
---

# Create PRD

Turns a rough feature request into a structured, technically-grounded PRD by researching the actual codebase for scoping accuracy, and can optionally create the matching Linear project and issues.

## When to use

… (sign up to view the full skill)
Sign up to view, copy, and install the full skill