Guide for authoring comprehensive PRDs with parallel planning support. Use for drafting technical specifications, defining requirements, and synthesizing planner outputs.
Erstellt Product-Requirements-Dokumente vor Design/Code. Trigger: PRD/Anforderungen.
Bewertet ein PRD auf Vollständigkeit, Klarheit, Machbarkeit und Testbarkeit und erzeugt ein strukturiertes Review-Artefakt mit konkreten Überarbeitungsanweisungen.
根据用户描述的业务场景，生成完整的企业级 PRD 文档，并为每个业务单元生成可在浏览器中打开的 HTML 交互原型页面。PRD 包含：文档背景与目标、角色权限、业务流程总览（多层级业务单元的流转关系与触发条件）、每个业务单元的详细规格（输入/输出/步骤/业务规则/异常处理），以及每个业务单元对应的系统页面交互要求（含 ASCII…
Use when turning a conversation or idea into a PRD file. Synthesizes existing context into a structured product requirements document with user stories, module design, and testing…
Run 6 critique checks on a PRD — metric validity, NFR specificity, failure-mode coverage, assumption traceability, rollback plan, intent clarity. Reports severity-tagged findings.
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
Create a PRD (product requirements document) for features and initiatives. Guides through clarifying questions, generates a structured draft with hypothesis, strategic fit,…
Use when 用户需要编写产品需求文档、整理功能需求、拆解 GitHub Issues 或制定实施计划时。触发场景：写PRD、产品需求、需求文档、prd、需求分析、功能设计、产品设计、需求评审、需求拆解、issue拆解、帮我写需求、整理功能点、我有个想法要落地、新功能规划。
Compétence pour la production complète d’un PRD : validation croisée des spécifications, vérification de la cohérence OKR, guide de rédaction selon le format canonique (sections…
Gunakan skill ini untuk membuat, mengulas, atau memperbarui dokumen Feature PRD dalam Bahasa Indonesia.
Generates professional PRD (Product Requirements Document) files optimized for AI coding tools. Takes a rough product idea, asks clarifying questions, and outputs a structured PDF…
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD.
PRD writing and product definition expert. Use when writing PRDs, user stories, acceptance criteria, or prioritizing features.
Create implementation phase PRDs from pre-existing research for the telemetry agent. Translates already-complete research into focused, bounded PRDs.
PRD-to-code conflict detection. Activate when: (1) user asks to audit/check/validate a PRD against existing code, (2) user says "prd:audit", "审 PRD", "需求冲突检测", "PRD 审查", (3) user…
Create or audit a Product Requirements Document — the master plan that all sprints trace back to. Required before any sprint can be generated.
Critical review of PRDs, feature specs, and product decision documents — acts as a devil's advocate to surface weak assumptions, missing requirements, implementation risks, and…
Schrijf een PRD dat engineering, design en stakeholders op één lijn brengt via een 8-sectie structuur met aannames en hypotheses.
Defines PRD structure, user story format with 4 Risks assessment, EARS-format acceptance criteria, and delivery readiness thresholds.
Check and update PRD status through lifecycle
PRD structure, writing patterns, and success metric definition. Use when authoring a product requirements document, writing a PRFAQ, or defining success criteria for a development…
Transform PRDs (Product Requirements Documents) into structured XML app specifications optimized for AI coding agents.
Generate a production-grade architecture diagram for Excalidraw from a PRD, focusing on services, data flow, dependencies, observability, security boundaries, and deployment…
Primary pipeline decomposition step after /write-a-prd. Use when a shaped PRD is ready to become implementation-ready slices with boundary maps and dependency order.
Decompose large PRDs, specs, or requirements documents into phased development plans with a master checklist and per-stage implementation files.
Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/.
Use when translating a PRD, feature spec, or raw product idea into screen-level prompts for web UX generators (Google Stitch, Figma AI, Pencil.dev, Claude Design, v0, or similar).
Skill untuk membuat PRD dan User Story untuk fitur baru. Output wajib direview PM sebelum lanjut ke Engineering Task.
Break a PRD in .cursor/plans/ into vertical slice markdown issues (tracer bullets), not horizontal layers.
When the user needs to define a product feature, write a product requirements document, or translate an idea into a structured spec. — from h-maki2/claude_sample
Lists all PRDs in .plans/ directory with their status and associated task files.
Gate 9 (Full Track) / Gate 4 (Small Track): Delivery roadmap and timeline planning. Transforms tasks into realistic delivery schedule with critical path analysis, resource…
Gate 2: Feature relationship map - visualizes feature landscape, groupings, and interactions at business level before technical architecture.
Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then…
Drafts U.S. civil/commercial pre-trial statements that narrow issues, fix trial assumptions, and prevent evidentiary surprises.
Principal-level UI/UX design and implementation skill for modern professional web platforms. Covers design system architecture, Tailwind token usage, component patterns, aesthetic…
Use when preparing an application for review by starting services and ensuring accessibility for testing.
Creates credit investment memos with borrower analysis, structural assessment, risk evaluation, and relative value positioning.
Compose a finished run's social SHARE CARD (the chart background + dark scrim + hero headline) and rasterize it to PNG so it can be eyeballed without opening the report GUI in a…
Tactical PM PRD for pricing experiments and pricing-page launches. Pairs with business-growth/pricing-strategy.
Analyze pricing strategy with competitive positioning, packaging, and revenue modeling. Use when: analyze pricing strategy, pricing strategy, analyze pricing, pricing analysis,…
Value-based pricing framework with Van Westendorp PSM analysis. Designs tier structure, packaging strategy, and unit economics.
Prepare PRINCE2 Managing Product Delivery material: work package acceptance, team plans, checkpoint reports, quality evidence, delivery confirmation, and handback notes.
Accessibility (a11y) principles — WCAG 2.2 AA conformance, semantic HTML, ARIA roles/properties/states, keyboard navigation, focus management, focus traps, color contrast, alt…
Clean Architecture, hexagonal architecture, ports and adapters, dependency rule, and domain-centric layering.
Clean code, DRY, KISS, YAGNI, function length, naming, abstraction level, error handling. Auto-load when writing functions, naming variables, reviewing code clarity, discussing…
Version control & collaboration hygiene — atomic commits (one logical change), commit-message quality (imperative subject, body explains why), branching strategy (feature-branch…
Choose a prioritization framework based on stage, team context, and stakeholder needs. Use when deciding between RICE, ICE, value/effort, or another scoring approach.
Use when ranking backlogs, deciding what to do first based on effort vs impact (quick wins vs big bets), prioritizing feature roadmaps, triaging bugs or technical debt, allocating…
Prioritize a set of CX initiatives, ideas, or opportunity areas into an actionable strategic roadmap.
Help users prioritize product roadmaps and backlogs. Use when someone is deciding what to build next, sequencing features, allocating resources across projects, handling…
Frontend audit — bundle size, dependencies, accessibility, performance, component quality. Use when asked for "frontend review", "performance audit", "accessibility check", or…
Guides privacy program maturity assessment using the AICPA/CIPT Privacy Maturity Model with five levels: Ad Hoc, Repeating, Defined, Managed, and Optimized.
Den Laufzeitzustand eines benannten Feature-Flags in einem CLI-Binary prüfen. Behandelt das vierzweigige Evidenzprotokoll (Binary-Strings, Live-Aufruf, On-Disk-Zustand,…
Use when writing a spec for a feature or a one-way-door decision — a Working-Backwards PRD whose whole top half is WHY before any WHAT.
Step-back protocol — restate, generalise, specialise, invert, ask why, pre-mortem, check stakeholders, and audit framings before solving
Use when locating a bug in an unfamiliar codebase, tracing a failure from symptom to source, or choosing between candidate fixes after the symptom is observed but before a patch…
Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.