AGENT SKILL

prd

Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

适用职业产品经理
License 许可
MIT
最近更新
2026-11-03
Stars
★ 0
Forks
0

01 前言 Front Matter

name
prd
tags
[ "domain/agents", "artifact/skill", "source/skills-copilot" ]
license
MIT
description
Generate high-quality Product Requirements Documents (PRDs) for software systems and AI-powered features. Includes executive summaries, user stories, technical specifications, and risk analysis.

03 SKILL.md 正文

Product Requirements Document (PRD)

Overview

Design comprehensive, production-grade Product Requirements Documents (PRDs) that bridge the gap between business vision and technical execution. This skill works for modern software systems, ensuring that requirements are clearly defined.

When to Use

Use this skill when:

  • Starting a new product or feature development cycle
  • Translating a vague idea into a concrete technical specification
  • Defining requirements for AI-powered features
  • Stakeholders need a unified "source of truth" for project scope
  • User asks to "write a PRD", "document requirements", or "plan a feature"

Operational Workflow

Phase 1: Discovery (The Interview)

Before writing a single line of the PRD, you MUST interrogate the user to fill knowledge gaps. Do not assume context.

Ask about:

  • The Core Problem: Why are we building this now?
  • Success Metrics: How do we know it worked?
  • Constraints: Budget, tech stack, or deadline?

Phase 2: Analysis & Scoping

Synthesize the user's input. Identify dependencies and hidden complexities.

  • Map out the User Flow.
  • Define Non-Goals to protect the timeline.

Phase 3: Technical Drafting

Generate the document using the Strict PRD Schema below.


PRD Quality Standards

Requirements Quality

Use concrete, measurable criteria. Avoid "fast", "easy", or "intuitive".

# Vague (BAD)
- The search should be fast and return relevant results.
- The UI must look modern and be easy to use.

# Concrete (GOOD)
+ The search must return results within 200ms for a 10k record dataset.
+ The search algorithm must achieve >= 85% Precision@10 in benchmark evals.
+ The UI must follow the 'Vercel/Next.js' design system and achieve 100% Lighthouse Accessibility score.

Strict PRD Schema

You MUST follow this exact structure for the output:

1. Executive Summary

  • Problem Statement: 1-2 sentences on the pain point.
  • Proposed Solution: 1-2 sentences on the fix.
  • Success Criteria: 3-5 measurable KPIs.

2. User Experience & Functionality

  • User Personas: Who is this for?
  • User Stories: As a [user], I want to [action] so that [benefit].
  • Acceptance Criteria: Bulleted list of "Done" definitions for each story.
  • Non-Goals: What are we NOT building?

3. AI System Requirements (If Applicable)

  • Tool Requirements: What tools and APIs are needed?
  • Evaluation Strategy: How to measure output quality and accuracy.

4. Technical Specifications

  • Architecture Overview: Data flow and component interaction.
  • Integration Points: APIs, DBs, and Auth.
  • Security & Privacy: Data handling and compliance.

5. Risks & Roadmap

  • Phased Rollout: MVP -> v1.1 -> v2.0.
  • Technical Risks: Latency, cost, or dependency failures.

Implementation Guidelines

DO (Always)

  • Define Testing: For AI systems, specify how to test and validate output quality.
  • Iterate: Present a draft and ask for feedback on specific sections.

DON'T (Avoid)

  • Skip Discovery: Never write a PRD without asking at least 2 clarifying questions first.
  • Hallucinate Constraints: If the user didn't specify a tech stack, ask or label it as TBD.

Example: Intelligent Search System

1. Executive Summary

Problem: Users struggle to find specific documentation snippets in massive repositories. Solution: An intelligent search system that provides direct answers with source citations. Success:

  • Reduce search time by 50%.
  • Citation accuracy >= 95%.

2. User Stories

  • Story: As a developer, I want to ask natural language questions so I don't have to guess keywords.
  • AC:
    • Supports multi-turn clarification.
    • Returns code blocks with "Copy" button.

3. AI System Architecture

  • Tools Required: codesearch, grep, webfetch.

4. Evaluation

  • Benchmark: Test with 50 common developer questions.
  • Pass Rate: 90% must match expected citations.

? Связи

  • [[MOC - Skills]] — Skills library
  • [[skills/skills-copilot]] — Category: skills-copilot
  • [[MOC - Agents]] — Copilot agents

04 同仓库更多 Skills

ibragimov-oasis
ibragimov-oasis/name-navigator

transloadit-media-processing

Process media files (video, audio, images, documents) using Transloadit. Use when asked to encode video to HLS/MP4, generate thumbnails, resize or watermark images, extract audio, concatenate clips, add subtitles, OCR documents, or run any media processing pipeline. Covers 86+ processing robots for file transformation at scale.

图像与多媒体Skill与智能体开发
★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

terraform-azurerm-set-diff-analyzer

Analyze Terraform plan JSON output for AzureRM Provider to distinguish between false-positive diffs (order-only changes in Set-type attributes) and actual resource changes. Use when reviewing terraform plan output for Azure resources like Application Gateway, Load Balancer, Firewall, Front Door, NSG, and other resources with Set-type attributes that cause spurious diffs due to internal ordering changes.

运维与部署
★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

refactor

Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

代码审查视觉设计
★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

plantuml-ascii

Generate ASCII art diagrams using PlantUML text mode. Use when user asks to create ASCII diagrams, text-based diagrams, terminal-friendly diagrams, or mentions plantuml ascii, text diagram, ascii art diagram. Supports: Converting PlantUML diagrams to ASCII art, Creating sequence diagrams, class diagrams, flowcharts in ASCII format, Generating Unicode-enhanced ASCII art with -utxt flag

★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

msstore-cli

Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.

开发工程师运维与部署Skill与智能体开发
★ 0
ibragimov-oasis
ibragimov-oasis/name-navigator

mentoring-juniors

Socratic mentoring for junior developers and AI newcomers. Guides through questions, never answers. Triggers: "help me understand", "explain this code", "I'm stuck", "Im stuck", "I'm confused", "Im confused", "I don't understand", "I dont understand", "can you teach me", "teach me", "mentor me", "guide me", "what does this error mean", "why doesn't this work", "why does not this work", "I'm a beginner", "Im a beginner", "I'm learning", "Im learning", "I'm new to this", "Im new to this", "walk me through", "how does this work", "what's wrong with my code", "what's wrong", "can you break this down", "ELI5", "step by step", "where do I start", "what am I missing", "newbie here", "junior dev", "first time using", "how do I", "what is", "is this right", "not sure", "need help", "struggling", "show me", "help me debug", "best practice", "too complex", "overwhelmed", "lost", "debug this", "/socratic", "/hint", "/concept", "/pseudocode". Progressive clue systems, teaching techniques, and success metrics.

开发工程师教师与教育Skill与智能体开发
★ 0