PRD Skill - Product Requirements Document Generator
Overview
This skill transforms natural language app ideas into structured Product Requirements Documents (PRD). It analyzes user requirements and generates comprehensive documentation including functional specifications, user flows, technical requirements, and implementation details.
Workflow
1. Input Analysis
- - Parse natural language requirements
- Identify core features and user needs
- Determine app type and target platform
2. PRD Structure Generation
Generate a structured PRD with the following sections:
2.1 Product Overview
- - App name and description
- Target audience
- Core value proposition
- Success metrics
2.2 Functional Requirements
- - Feature list with priority (P0, P1, P2)
- User stories and acceptance criteria
- Screen-by-screen specifications
2.3 User Flows
- - User journey maps
- Navigation flow diagrams
- Key user interactions
2.4 Technical Specifications
- - Platform requirements (iOS version, device support)
- Architecture decisions
- Third-party integrations
- Data models and APIs
2.5 Non-Functional Requirements
- - Performance requirements
- Security considerations
- Accessibility standards
- Localization needs
3. Output Format
The PRD is generated in markdown format with clear section headers and structured content. After generating the PRD, the skill automatically triggers the dev-skill to begin implementation.
Examples
User Input: "做一个待办事项App，支持分类、提醒和分享功能"
Generated PRD Sections:
- 1. Product Overview: Todo List App with categorization, reminders, and sharing
- Functional Requirements:
- P0: Create/Edit/Delete tasks
- P1: Task categorization with tags
- P1: Push notifications for reminders
- P2: Share tasks via iMessage/Email
- 3. User Flows: Onboarding → Task creation → Categorization → Reminder setup
- Technical Specs: SwiftUI, Core Data, UserNotifications framework
- Non-Functional: Offline support, iCloud sync, accessibility features
Auto-Trigger Next Steps
After generating the PRD, this skill automatically:
- 1. Saves the PRD to
prd-output/ directory with timestamp - Triggers
dev-skill with the PRD as input - Monitors the pipeline progress through session messaging
Integration with Auto-Dev-Pipeline
This skill is designed to work seamlessly with:
- - dev-skill: Receives PRD and generates SwiftUI code
- qa-skill: Receives code and generates test cases
- session coordination: Uses
sessions_send to trigger next steps
Best Practices
- 1. Be specific: Ask clarifying questions if requirements are vague
- Prioritize: Always assign priority levels to features
- Consider constraints: Include iOS platform limitations
- Think MVP: Focus on minimum viable product first
- Document assumptions: Clearly state any assumptions made
PRD技能 - 产品需求文档生成器
概述
该技能将自然语言的应用创意转化为结构化的产品需求文档（PRD）。它分析用户需求并生成全面的文档，包括功能规格、用户流程、技术要求和实现细节。
工作流程
1. 输入分析
- - 解析自然语言需求
- 识别核心功能和用户需求
- 确定应用类型和目标平台
2. PRD结构生成
生成包含以下章节的结构化PRD：
2.1 产品概述
- - 应用名称和描述
- 目标用户群体
- 核心价值主张
- 成功指标
2.2 功能需求
- - 带优先级的功能列表（P0、P1、P2）
- 用户故事和验收标准
- 逐屏规格说明
2.3 用户流程
2.4 技术规格
- - 平台要求（iOS版本、设备支持）
- 架构决策
- 第三方集成
- 数据模型和API
2.5 非功能需求
3. 输出格式
PRD以Markdown格式生成，包含清晰的章节标题和结构化内容。生成PRD后，该技能会自动触发dev-skill开始实现。
示例
用户输入： 做一个待办事项App，支持分类、提醒和分享功能
生成的PRD章节：
- 1. 产品概述：支持分类、提醒和分享的待办事项列表应用
- 功能需求：
- P0：创建/编辑/删除任务
- P1：使用标签对任务进行分类
- P1：提醒的推送通知
- P2：通过iMessage/邮件分享任务
- 3. 用户流程：引导页 → 任务创建 → 分类 → 提醒设置
- 技术规格：SwiftUI、Core Data、UserNotifications框架
- 非功能需求：离线支持、iCloud同步、无障碍功能
自动触发后续步骤
生成PRD后，该技能会自动：
- 1. 将PRD保存到带时间戳的prd-output/目录
- 以PRD作为输入触发dev-skill
- 通过会话消息监控流水线进度
与自动开发流水线的集成
该技能设计用于与以下组件无缝协作：
- - dev-skill：接收PRD并生成SwiftUI代码
- qa-skill：接收代码并生成测试用例
- 会话协调：使用sessions_send触发后续步骤
最佳实践
- 1. 具体明确：如果需求模糊，提出澄清性问题
- 优先级排序：始终为功能分配优先级级别
- 考虑约束：包含iOS平台限制
- 思考MVP：首先关注最小可行产品
- 记录假设：清晰说明所做的任何假设
