— No reviews yet
0 installs
11 views
0.0% view→install
Install
$ agentstack add skill-doncheli-don-cheli-sdd-doncheli-prd ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Are you the author of Doncheli Prd? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claimAbout
Don Cheli: PRD Generator
Instructions
- Discover sources — Identify all available inputs:
- Figma links: analyze screens, flows, components, missing states
- Brief documents: extract objectives, audience, problems
- User research: identify personas, JTBD, pain points
- Existing code: detect technical constraints
- Conversation context: extract requirements mentioned by the user
- Analyze Figma (if provided):
- Count screens/frames and map navigation flow
- Extract texts, labels, form fields, interactions
- Detect missing UI states: loading, empty, error, success, offline
- Identify gaps: flows not designed, edge cases missing
- Convert each screen → user stories → acceptance criteria
- Risk analysis — For each feature, evaluate 7 risk categories:
- Technical (complexity, integrations, tech debt)
- Product (market fit, adoption, competition)
- UX (usability, accessibility, learning curve)
- Business (revenue, cost, time-to-market)
- Legal (GDPR, compliance, ToS)
- Security (OWASP, sensitive data, auth)
- Operational (support, scalability, monitoring)
- Assign probability (Low/Medium/High) and impact (Low/Medium/High/Critical)
- Propose mitigation for each risk
- Prioritize features using MoSCoW + RICE:
- MoSCoW: Must / Should / Could / Won't
- RICE: (Reach × Impact × Confidence) / Effort
- Rank features by RICE score
- Generate PRD with 13 sections:
- Executive Summary
- Problem (context, pain points, evidence)
- Objectives & Success Metrics (KPIs, North Star)
- Target Audience (personas, JTBD, user journey)
- Proposed Solution (overview, main flow, features by priority)
- Detailed Requirements (functional with Gherkin, non-functional, integrations, data model)
- Design & UX (Figma analysis, UI states, responsive, accessibility)
- Risk Analysis (matrix, mitigations, dependencies)
- Scope (in scope, out of scope, future iterations)
- Timeline & Milestones
- Competitive Analysis
- Launch Plan (rollout, monitoring, rollback)
- Appendices (glossary, references, change history)
- Validate PRD quality:
- Every requirement must be verifiable/testable
- Success metrics must be defined with baseline and target
- Every risk must have a mitigation
- Scope must be realistic for the timeline
- Anti-scope (out of scope) must be explicit
Output Format
# PRD: [Product/Feature Name]
## Metadata
| Field | Value |
|-------|-------|
| Version | 1.0 |
| Author | [name] |
| Status | Draft / In Review / Approved |
| Date | [date] |
## 1. Executive Summary
...
(continue with all 13 sections)
Save output to:
.dc/prd/prd-v1.0.md— Full PRD.dc/prd/prd-risks.md— Expanded risk matrix.dc/prd/prd-figma-analysis.md— Figma analysis (if applicable)
Integration with SDD Pipeline
After generating the PRD, suggest:
/dc:specify → Convert user stories into Gherkin specs
/dc:tech-plan → Generate blueprint from the PRD
/dc:breakdown → Create TDD tasks from the stories
Templates
Select based on product type:
saas— B2B platforms, dashboards, multi-tenantmobile— Native iOS/Android, PWAecommerce— Online stores, marketplacesapi— Public APIs, SDKs, developer platformsinternal— Internal team toolslanding— Landing pages, conversion funnels
Quality Gate
- Never generate a PRD without at least 1 verifiable success metric
- Never omit the risk section — if no risks are visible, dig deeper
- Never leave scope ambiguous — mark unclear items as
[NEEDS CLARIFICATION] - Always include explicit anti-scope (what will NOT be built)
- Always generate user stories in Gherkin format for SDD integration
- Always version the PRD (v1.0, v1.1) with change history
Do not use this skill when
- The task is a simple bug fix or hotfix — use
/dc:quickinstead - The user only needs technical specs — use
/dc:specifydirectly - The requirement is already well-defined in Gherkin — skip PRD, go to plan
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: doncheli
- Source: doncheli/don-cheli-sdd
- License: Apache-2.0
- Homepage: https://doncheli.tv
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.