Prd Skill

Generate structured Product Requirements Documents (PRD) from natural language user requirements. Use when a user provides an app idea or feature request and...

Security Scan

The skill's instructions, scope, and requirements align with its stated purpose of generating PRDs; there are no unexpected credential requests or risky install steps, though it will write output to a local folder and trigger other pipeline skills which you should confirm are intended and trusted.

Purpose & Capability

Name and description match the instructions: the SKILL.md describes parsing requirements and producing a structured PRD. It mentions integration with dev-skill and qa-skill as the next steps, which is a reasonable part of an auto-dev pipeline and consistent with the stated purpose.

Instruction Scope

Instructions are focused on PRD creation. Two runtime behaviors to note: (1) it states it will save the PRD to a local path ('prd-output/' with timestamp) — writing files is not declared elsewhere but is plausible for a document generator; (2) it says it 'triggers dev-skill' and uses 'sessions_send' to coordinate pipeline steps. Those are not inherently malicious but are additional side effects (file writes and cross-skill triggering) beyond mere text generation and should be expected and reviewed prior to use.

Install Mechanism

Instruction-only skill with no install spec and no code files. This is the lowest-risk model for installation because nothing is downloaded or written by an installer.

Credentials

The skill declares no required environment variables, credentials, or config paths. That fits its function of transforming input text into a PRD and handing it off to other pipeline skills; there are no disproportionate secret or credential requests.

Persistence & Privilege

always is false (normal). The skill is user-invocable and may be invoked autonomously per platform defaults. Combined with its explicit auto-triggering of dev-skill and session messaging, this means one invocation can spawn further pipeline actions — confirm you want that automation and that the downstream skills are trusted. The skill does not request persistent presence or modify other skills' configs in the provided instructions.

Assessment

This skill is coherent for generating PRDs. Before installing, confirm two operational details: (1) you are okay with the skill writing PRD files to a local 'prd-output/' directory (check where that folder will be created and who can access it); (2) the skill will automatically trigger downstream pipeline skills (dev-skill, qa-skill) via session messaging—make sure those skills exist and are trusted, otherwise disable or restrict automatic triggering. No credentials or external installs are requested, which reduces risk, but review and test the skill in a safe environment if you want to validate its auto-trigger behavior.

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
2. 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
4. Technical Specs: SwiftUI, Core Data, UserNotifications framework
5. 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
2. Triggers dev-skill with the PRD as input
3. 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
2. Prioritize: Always assign priority levels to features
3. Consider constraints: Include iOS platform limitations
4. Think MVP: Focus on minimum viable product first
5. Document assumptions: Clearly state any assumptions made