القائمة
Generates a structured PRD from a feature description or brief. Use when asked to write, draft, or create a PRD.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/hamzafarooq/claude-code-starter --skill prd-generatorيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Research emerging trends in a market or technology space. Returns signal vs noise breakdown with evidence. Use when the user asks what's changing in a market, what trends to watch, or what's coming next.
Turn any document, proposal, report, or outline into a stunning single-file HTML presentation using 34 pre-built professional templates. Use when the user wants to convert a markdown file, proposal, or written content into a beautiful visual HTML document ready to share or convert to PDF.
Semantic Design System Skill for Google Stitch. Generates agent-friendly DESIGN.md files that enforce premium, anti-generic UI standards — strict typography, calibrated color, asymmetric layouts, perpetual micro-motion, and hardware-accelerated performance.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | prd-generator |
| description | Generates a structured PRD from a feature description or brief. Use when asked to write, draft, or create a PRD. |
When triggered, ask the user for:
Then generate a full PRD using the structure below.
What pain are we solving and for whom? Why does this matter now?
3-5 measurable outcomes we want to achieve with this feature. Format: "Increase [metric] by [amount] within [timeframe]"
What this feature explicitly will NOT do. Be specific. This section prevents scope creep.
Who uses this feature and in what context? Include 2-3 concrete scenarios (short narrative, not bullets).
Written as: "As a [user type], I want to [action] so that [outcome]." Group into: Must-have / Should-have / Nice-to-have
Written in Given/When/Then format for each must-have story. Should be specific enough that a QA engineer can write a test.
Two columns:
What must be decided before engineering starts? Format as questions, not statements. Assign an owner if known.
How will we measure whether this feature succeeded? Include leading indicators (early signals) and lagging indicators (final outcomes).
[ASSUMPTION][NEEDS INPUT]docs/prd.md