메뉴
Generates structured Product Requirements Documents with user stories, acceptance criteria, and stakeholder alignment.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Estándares y validación para scripts Python cross-platform (Windows/Linux/macOS). Esta skill debe usarse cuando se escriban scripts Python en el framework para garantizar compatibilidad multi-SO, evitar problemas de encoding (emojis en Windows), y asegurar calidad consistente en todo el código.
Procesa archivos CSV para limpieza, transformación y análisis de datos tabulares. Esta skill debe usarse cuando el usuario necesite manipular datos CSV, incluyendo limpieza de datos, transformaciones (filtros, agregaciones, joins), conversión a otros formatos, o análisis exploratorio de datasets en formato CSV.
Genera visualizaciones de datos (gráficos de barras, líneas, etc.) usando Matplotlib y Seaborn.
Comprehensive document creation, editing, and analysis with support for tracked changes, formatting preservation, and text extraction. Use when working with Word documents (.docx).
Genera prompts JSON estructurados a partir de una idea inicial para IA, con objetivos y entregables claros.
Guía para escribir documentación Markdown de alta calidad siguiendo el principio MVI del framework FreakingJSON. Esta skill debe usarse cuando el usuario necesite crear o editar archivos .md en el framework, asegurando consistencia, claridad y adherencia al principio de Minimal Viable Information.
| name | prd-generator |
| description | Generates structured Product Requirements Documents with user stories, acceptance criteria, and stakeholder alignment. |
| license | MIT |
| metadata | {"author":"opencode","version":"1.1"} |
| compatibility | OpenCode, Claude Code, Gemini CLI, Codex |
Convert product ideas into clear, actionable requirements that engineering teams can build from.
Use the standard structure and fill each section with concise, testable statements.
TITLE: [Feature Name]
Author: [Owner] | Status: [Draft/Review/Approved]
Last Updated: [Date]
Agents: [Roles + owners]
Backlog IDs: [BL-###, BL-###]
1. OVERVIEW
- Problem Statement
- Proposed Solution
- Success Metrics
2. GOALS & NON-GOALS
- Goals
- Non-Goals
3. USERS & CONTEXT
- Primary Users
- Usage Context
- Constraints
4. REQUIREMENTS
- User Stories
- Functional Requirements
- Non-Functional Requirements
- Acceptance Criteria (per story)
5. DESIGN & TECH
- User Flows
- Wireframes/Mockups
- Technical Considerations
6. BACKLOG TRACEABILITY
- BL-### -> Requirement/Story mapping
- Out-of-scope items linked to backlog if deferred
7. DELIVERY
- Milestones
- Dependencies
- Risks
- Rollout/Release plan
8. APPENDIX
- Research Data
- Open Questions
As a [user type]
I want to [action]
So that [benefit]
Acceptance Criteria (Given-When-Then):
Given [context]
When [action]
Then [expected result]
Functional example: "System shall send an email confirmation within 30 seconds of order completion."
Non-functional examples:
List stakeholders with interest, decision rights, and sign-off requirement.