القائمة
Genera Product Requirement Documents (PRD) strutturati. Usa per: trasformare idee in specifiche dettagliate, creare user stories con acceptance criteria, preparare input per Ralph Loop.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | prd-generator |
| description | Genera Product Requirement Documents (PRD) strutturati. Usa per: trasformare idee in specifiche dettagliate, creare user stories con acceptance criteria, preparare input per Ralph Loop. |
| user-invocable | true |
| disable-model-invocation | false |
| allowed-tools | Read, Write, AskUserQuestion |
Trasforma descrizioni feature in PRD strutturati pronti per implementazione.
Voglio aggiungere una feature di quiz per testare
le conoscenze degli utenti sui comandi Claude Code.
Dovrebbe avere 5 domande, mostrare il punteggio alla fine,
e salvare il best score.
Prima di generare il PRD, chiedi:
# PRD: [Feature Name]
## Overview
[1-2 paragrafi che descrivono la feature]
## Goals
- [Goal 1 misurabile]
- [Goal 2 misurabile]
## Non-Goals
- [Cosa NON faremo in questa versione]
## User Stories
### US-001: [Title]
**As a** [user type]
**I want to** [action]
**So that** [benefit]
**Acceptance Criteria:**
- [ ] [Criterio verificabile 1]
- [ ] [Criterio verificabile 2]
- [ ] typecheck passes
- [ ] tests pass
**Priority:** P0/P1/P2
### US-002: [Title]
...
## Technical Considerations
- [Dipendenze]
- [Rischi tecnici]
- [Decisioni architetturali]
## Success Metrics
- [KPI 1]
- [KPI 2]
## Timeline
- Week 1: [Milestone]
- Week 2: [Milestone]
## Open Questions
- [Domanda da risolvere]
Ogni story deve completarsi in 1 context window Claude.
❌ Troppo grande:
"Build authentication system"
✅ Atomiche:
- "Create User model with email/password"
- "Add password validation"
- "Create login endpoint"
- "Add session management"
Acceptance criteria devono essere testabili automaticamente.
❌ Vago:
- Users can log in
✅ Verificabile:
- Login form has email and password fields
- Email field validates format (regex)
- Password field has minimum 8 chars
- Submit shows loading state
- Success redirects to /dashboard
- Error shows message below form
- typecheck passes
- tests pass
❌ Dipendenza implicita:
US-001: Create login page
US-002: Add password reset (assume login exists)
✅ Dipendenza esplicita:
US-001: Create login page
US-002: Add password reset
Dependencies: US-001
P0: Must have (MVP)
P1: Should have (important)
P2: Nice to have (if time)
Dopo aver creato il PRD markdown, converti per Ralph:
{
"branchName": "ralph/quiz-feature",
"userStories": [
{
"id": "US-001",
"title": "Create quiz intro screen",
"acceptanceCriteria": [
"Screen shows at /quiz route",
"Displays quiz title and description",
"Has 'Start Quiz' button",
"Button navigates to first question",
"typecheck passes"
],
"priority": 1,
"passes": false,
"notes": ""
}
]
}
- US: Product listing page
- US: Product detail page
- US: Add to cart functionality
- US: Cart page with quantities
- US: Checkout flow step 1 (shipping)
- US: Checkout flow step 2 (payment)
- US: Order confirmation
- US: User model and migration
- US: Registration form
- US: Email validation
- US: Password requirements
- US: Login form
- US: Session management
- US: Logout functionality
- US: Password reset request
- US: Password reset execution
- US: List view with pagination
- US: Detail view
- US: Create form
- US: Edit form
- US: Delete with confirmation
- US: Search/filter
Mappa il flusso completo prima di scrivere stories:
Entry → Screen 1 → Screen 2 → Success → Exit
Non solo happy path:
- Cosa succede se l'utente è offline?
- Cosa succede con input invalido?
- Cosa succede se la sessione scade?
Ogni story include SEMPRE:
- typecheck passes
- tests pass
- Verified in browser (se UI)
PRD deve contenere abbastanza contesto che
un developer (o Claude) possa implementare
senza fare altre domande.
tasks/
├── prd-quiz-feature.md # PRD completo
└── prd-quiz-feature.json # Per Ralph Loop
Customize a Claude Code plugin for a specific organization's tools and workflows. Use when: customize plugin, set up plugin, configure plugin, tailor plugin, adjust plugin settings, customize plugin connectors, customize plugin skill, customize plugin command, tweak plugin, modify plugin configuration.
Guide users through creating a new plugin from scratch in a cowork session. Use when users want to create a plugin, build a plugin, make a new plugin, develop a plugin, scaffold a plugin, start a plugin from scratch, or design a plugin. This skill requires Cowork mode with access to the outputs directory for delivering the final .plugin file.
Research customer questions by searching across documentation, knowledge bases, and connected sources, then synthesize a confidence-scored answer. Use when a customer asks a question you need to investigate, when building background on a customer situation, or when you need account context.
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
Write and maintain knowledge base articles from resolved support issues. Use when a ticket has been resolved and the solution should be documented, when updating existing KB articles, or when creating how-to guides, troubleshooting docs, or FAQ entries.
Draft professional, empathetic customer-facing responses adapted to the situation, urgency, and channel. Use when responding to customer tickets, escalations, outage notifications, bug reports, feature requests, or any customer-facing communication.