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…
Collaboratively author a Product Requirements Document with the user, acting as a senior PM. Output is the input to spec-kit's /specify.
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…
От идеи к PRD/EARS через интервью в несколько раундов. Ресёрч кодбазы, неудобные вопросы, подсветка граничных случаев, визуализация (widget или ASCII).
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.
PRD creation and PRD execution operating system. Use when the founder asks to turn a rough idea into a PRD, run a Codex review on a PRD or issue, decompose an approved PRD into…
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.
Use when the user needs a PRD, requirements document, product spec, user stories, acceptance criteria, success metrics, UI flow, wireframe, mockup, HTML prototype, or prototype…
Use when the user wants every open question in a PRD resolved interactively — "ask me all questions", "/prd-questions", "let's resolve the open questions".
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…
Use when turning a PRD or requirements document into a first pass information architecture. Triggers on a pasted or linked PRD plus a request for an IA, sitemap, screen list, or…
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/.
Convert an approved PRD into a phase-gated implementation SPEC. User-facing entry point that dispatches to the prd-to-spec babysitter process via /babysitter:call (interactive) or…
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).
Разбить план, спецификацию или PRD на независимые задачи для реализации с помощью вертикальных срезов.
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
把 PRD 第四章「产品范围」按模块拆成禅道研发需求(SR),通过禅道 API 在浏览器会话里批量创建/更新。触发场景:同步禅道 / 建禅道需求 / 把 PRD 提到禅道 / 批量提研发需求 / PRD to zentao / 需求落禅道。关键词:禅道、研发需求、SR、同步需求、批量建需求、提研发需求、zentao。配套姐妹…
Gate 1: Business requirements document - defines WHAT/WHY before HOW. Creates PRD with problem definition, user stories, success metrics.
Explore intent and shape ideas before implementation planning. Use when Codex is asked to brainstorm, ideate, plan a feature/product/workflow, clarify a vague idea, compare…
中文优先：用于产品能力相关任务，帮助识别、设计、实现或验证对应工作流。English keywords: Translate PRD intent, roadmap asks, or product discussions into an implementation-ready capability plan that exposes…
Use for product development work from PRD to implementation: make technical decisions, stress-test plans, document ADRs or spike/POC findings, break down engineering work, plan…
Write structured product requirements documents (PRDs) with problem statements, user stories, requirements, and success metrics.
Create a new project with name and description and a somewhat fixed tech stack based on user's requirements
Product consultation for Conductor orchestrator. Clarifies scope, interprets ambiguous requirements, prioritizes features within a track.
Workflow to generate a comprehensive Product Requirements Document (PRD) detailing user stories, acceptance criteria, technical considerations, and metrics.
Strategic product leadership specializing in product strategy, roadmap development, feature prioritization, and cross-functional coordination.
AI product photography with studio lighting, lifestyle shots, and packshot conventions. Covers angles, backgrounds, shadow types, hero shots, and e-commerce image require — from…
AI product photography with studio lighting, lifestyle shots, and packshot conventions. Covers angles, backgrounds, shadow types, hero shots, and e-commerce image require — from…
Write a Product Requirements Document — functional requirements, non-functional requirements, epics, and success metrics.
Defines 4 Risks confidence thresholds, OST hierarchy levels, Knowledge Pyramid tiers, and state design requirements.
Design or audit a product-level user-data durability and recovery contract spanning backup, restore, same-product export/re-import, device replacement, version compatibility,…
Comprehensive product requirements documentation from problem definition through launch planning. Supports both enterprise PRD (full specs, cross-functional alignment) and…
Optional PRD methodology — loaded by the questioner agent when a feature request is vague or complex enough to warrant a structured product spec alongside task.md.
Writes product sourcing briefs with specifications, quality requirements, MOQs, supplier evaluation criteria, and negotiation guidelines.
Convert a rough idea, meeting notes, or shorthand into a structured Product Requirements Document. Use when the user mentions PRD, requirements, spec, or wants to formalize an…
Use when the task is to operationalize analytics for repeatable, scheduled, or monitored production use.
Senior Architect methodology for greenfield projects — collects business requirements through 1-3 chat phases, then produces 6+1 artifacts in docs/plans/
/ (brief,…