“prd”的搜索结果

Create, update, or review a product requirements document, or PRD. Organize product goals, features, and quality requirements through guided discussion or a faster draft, with detail matched to the project's needs and stakes.

中文简介正在准备中。当前显示英语简介。

• Turn a product concept and source materials into a PRD
• Choose suitable detail for an internal tool or product launch
• Update a PRD while checking earlier decisions

Convert an existing product requirements document into Ralph’s prd.json format. Break large features into small implementation tasks, order them by dependencies, and define checkable completion criteria so Ralph can work through them in sequence.

中文简介正在准备中。当前显示英语简介。

• Convert a requirements document into Ralph JSON
• Split large features into small implementation tasks
• Order tasks by their dependencies

PRD 架构师 / 需求文档起草：当用户要把一个产品想法、需求草稿、脑暴结果或功能说明整理成 PRD 时使用。 可用中文唤起：“帮我写 PRD”“帮我选 PRD 模板”“把这个需求整理成 PRD”“判断该用轻量 PRD 还是标准 PRD” “补一张可编辑 Draw.io 核心流程图”“PRD 里加架构图”。 会在 PRD-lite、PRD-standard、PRD-ai-native 中选择一个模板资产按需加载，并在需要时加载 mockup handoff、 Draw.io 图示或开发 handoff 附录；页面型 PRD 默认联动生成项目 UI 对齐的 HTML、关键截图和正文证据。 不用于直接编码、单纯画 UI，或评审一份已经写好的 PRD。

中文简介正在准备中。当前显示原文说明。

Turn a product idea into a PRD, a product requirements document, through focused questions about the problem, scope, success, and user journeys. Record whether to proceed and produce a Markdown file before technical design begins.

中文简介正在准备中。当前显示英语简介。

• Clarifying the problem behind a product idea
• Documenting requirements for an agreed feature
• Deciding whether to build, postpone, or stop

Turn feature requirements into a PRD, a document defining what to build, then organize development plans and GitHub Issues. Coordinate parallel agents and track progress, blockers, and next priorities through delivery.

中文简介正在准备中。当前显示英语简介。

• Define feature requirements and scope in a PRD
• Split development plans into tasks and sync them to GitHub
• Coordinate parallel agents working on issues

Work with John, a product manager persona, to clarify requirements through user interviews and stakeholder alignment. Turn a product vision into a PRD, a product requirements document, and small, validated increments for development.

中文简介正在准备中。当前显示英语简介。

• Turning a product idea into a PRD
• Discovering requirements through user interviews
• Aligning stakeholders on product requirements

PRD 到研发 Issue 拆解 / implementation issues：当用户已有 PRD、需求文档、handoff、产品方案或 GitHub PRD issue， 需要拆成可独立领取、可验收、适合 GitHub Issues 承接的开发任务时使用。可用中文唤起： “把 PRD 拆成 issue”“需求文档拆任务”“生成 GitHub issues”“PRD 拆工单”“拆 implementation issues” “按 vertical slice 拆开发票”。不用于从零写 PRD；那类请求用 prd-architect。不用于评审 PRD 是否完整； 那类请求先用 prd-review。

中文简介正在准备中。当前显示原文说明。

Create a feature PRD, a product requirements document, from a parent Epic. Turns a feature idea into user stories, explicit requirements, acceptance criteria, and scope boundaries that engineering teams can use to prepare a technical specification.

中文简介正在准备中。当前显示英语简介。

• Turn a feature within an Epic into a detailed PRD
• Describe primary user paths and edge cases
• Define acceptance criteria for feature completion

Turn product or feature ideas into a concise product requirements document that helps teams decide what to build first. Connect target customers, customer value, success measures, and release scope, or review an existing document for gaps.

中文简介正在准备中。当前显示英语简介。

• Drafting requirements for a new product or feature
• Agreeing on the scope of a first release
• Reviewing an existing product requirements document

Turn a feature idea into a structured product requirements document. Clarify goals and scope through multiple-choice questions, then produce a Markdown file with small implementation tasks, checkable completion criteria, functional requirements, and success measures.

中文简介正在准备中。当前显示英语简介。

• Plan requirements for a new feature
• Clarify goals and scope before development
• Prepare specifications for developers or AI agents

与えられた企画・機能アイデアに対して不明点をユーザーへ質問し、合意した内容を PRD（プロダクト要求仕様）として確定させ、GitHub Issue として作成するスキル。「PRDを作って」「要求仕様をまとめて」「この企画をPRD化して」といったリクエストで使用する。作成した PRD Issue は `/breakdown-issues <番号>` へ渡してタスク分解できる。

中文简介正在准备中。当前显示原文说明。

Evaluate code against a product requirements document, scoring implementation and tests separately for each acceptance criterion. Produce an evidence-backed final grade, identify gaps, and compare implementations using a fixed checklist and scoring method.

中文简介正在准备中。当前显示英语简介。

• Checking whether a feature fulfills its requirements
• Comparing implementations of the same specification
• Auditing unit and end-to-end test coverage

PRD 评审 / 需求评审：当用户已有 PRD 初稿、handoff、需求文档或产品方案，需要从 PM、研发、测试视角找缺口、 冲突、不可实现点和不可测试点时使用。可用中文唤起：“帮我审 PRD”“从研发和测试视角挑问题” “这个需求文档能不能交付开发”“帮我给 PRD 出修改草案”“检查 PRD 图示是否缺失或不可编辑”。 不用于凭空生成 PRD 初稿、直接写代码，或对 PRD 背后的成熟方案做一问一答压力测试；方案压测用 grill-me。

中文简介正在准备中。当前显示原文说明。

Use when the user wants to set up pwdev-prd in a project — 'inicializar o pwdev-prd', 'init prd', 'configurar PRDs' — creating the .planning/prds/ workspace and choosing language and the optional SQLite audit trail. Do NOT use to write a PRD (prd-create).

中文简介正在准备中。当前显示原文说明。

Turn a broad product idea into an Epic PRD, a requirements document for a large initiative. Defines users, workflows, business requirements, success metrics, and scope to give engineering teams a basis for technical architecture planning.

中文简介正在准备中。当前显示英语简介。

• Turn a broad SaaS idea into an Epic PRD
• Define target users and their main workflows
• Clarify requirements, success metrics, and exclusions

Turn user research and complaints into a clear problem statement. Identify who is struggling, their desired outcome, barriers, root causes, constraints, and emotional impact, then summarize the problem in one sentence for team discussions or product planning.

中文简介正在准备中。当前显示英语简介。

• Agreeing on the user problem before proposing solutions
• Writing a concise problem statement for a PRD
• Finding the underlying problem behind feature requests

Turn research notes and discussions into a PRD, a product requirements document for development teams. Connect customer problems, target users, proposed solutions, and success metrics, while documenting acceptance criteria, excluded work, dependencies, and unresolved questions.

中文简介正在准备中。当前显示英语简介。

• Writing requirements for a major new feature
• Turning discovery findings into an engineering handoff
• Aligning teams on scope and success metrics

Seed a fresh (greenfield) repository with the PRD-Driven Context Engineering scaffold — PRD.md, SoT/ knowledge files, EPIC templates, domain-profile config, and agent MEMORY starters. Invoked as /prd-ce:init when the plugin is installed. The framework itself (skills, agents, hooks, scripts) ships LIVE in the plugin; this skill only plants the consumer-owned files the plugin cannot carry as behavior. Triggers on "/prd-ce:init", "set up PRD lifecycle here", "scaffold a new PRD-CE project", "initialize the methodology". Outputs a seeded scaffold + a verification report.

中文简介正在准备中。当前显示原文说明。

产品诊断与 PRD 迭代：诊断根因（设计缺陷/实现偏离/PRD 遗漏），必要时反驳需求，更新 PRD 并生成带异常态门禁的 Feature Spec。 触发方式：用户说"更新PRD"、"调整需求"、"迭代PRD"、"forge-prd"、描述产品问题、需要修改产品需求时。

中文简介正在准备中。当前显示原文说明。

Create or revise the problem-first SDD Composy PRD (tasks/prd-SLUG/prd.md) with stable RF/CA identifiers, stopping at the human approval gate. Use when a user problem needs a product contract — 'criar o PRD', 'documento de requisitos', 'revisar o PRD do slug X', 'write the requirements for…'. Do NOT use for user stories (sdd-stories), technical design (sdd-techspec), or PRDs outside an initialized SDD workspace.

中文简介正在准备中。当前显示原文说明。

Use when the user wants a PRD exported — 'exportar o PRD', 'gerar o prd.json', 'criar issue com o PRD', 'export PRD to GitHub' — as canonical JSON or as a single GitHub issue. Do NOT use to publish a roadmap with many issues (prd-publish).

中文简介正在准备中。当前显示原文说明。

Use when an approved PRD must become an executable roadmap — 'gerar roadmap do PRD', 'quebrar o PRD em épicos e features', 'cadeia de dependências', 'roadmap with dependencies' — Phase/Epic/Feature/Task with explicit dependencies, waves and critical path, validated by a deterministic checker, with an approval gate. Do NOT use for a PRD that is not approved (prd- create/prd-refine first).

中文简介正在准备中。当前显示原文说明。

Use when the user wants to change an existing PRD — 'refinar o PRD', 'adicionar requisito', 'atualizar escopo do PRD', 'update the PRD' — through targeted questions, bumping the version and re-opening approval. Do NOT use to create a PRD (prd-create).

中文简介正在准备中。当前显示原文说明。

Run a structured discovery interview and produce a complete, developer-ready Product Requirements Document. Load when the user asks to write a PRD, create product requirements, document a feature, define user stories with acceptance criteria, or turn a rough idea into a formal product requirements document. Also triggers on "document this feature", "write requirements for", "create a one-pager", "turn this into a PRD", "I need a PRD for", or any request to produce a structured product document for stakeholder alignment or engineering handoff. Supports Full PRD, Lean PRD, and One-Pager formats. Note: for executable feature specifications (FRs, NFRs, ACs as Given/When/Then consumable by AI coding agents), route to `feature-spec` instead — PRDs frame the product, feature-specs encode the implementable contract.

中文简介正在准备中。当前显示原文说明。