Results for “prd”

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.

The English summary is being prepared. Showing the original description.

DEPRECATED — consolidated into bmad-prd validate intent - this skill will be removed in v7 in favor of `bmad-prd`.

The English summary is being prepared. Showing the original description.

DEPRECATED — consolidated into bmad-prd create intent - this skill will be removed in v7 in favor of `bmad-prd`.

The English summary is being prepared. Showing the original description.

Act as a product-manager copilot that turns evidence into product decisions and artifacts: backlogs and prioritization, PRDs and user stories, metrics and OKRs, experiments, launch plans, feedback triage, and pricing/packaging, kept in a per-product workspace. Use whenever the user wants to decide what to build, spec it, or ship it: "write a PRD for…", "prioritize our backlog", "what should we build next", "plan OKRs", "define our north star metric", "design an A/B test", "plan the launch", "triage this customer feedback", "platform or feature?", in any language ("viết PRD", "ưu tiên tính năng nào", "quản lý sản phẩm", "プロダクト管理", "产品经理"), even when they never say "product manager". Also use when the user returns to a product workspace this skill created (a directory holding `product.md`, `state.md`, and `decisions.md`). Not for deep user discovery (design-thinking), desk market facts (market-researcher), or company-level bets (strategy-board).

The English summary is being prepared. Showing the original description.

编写完整的 Product Requirements Document（PRD）时使用。适用于完整功能模块需求定义、需求评审材料、给下游工作流的交付包。优先输出可开发、可测试、可验收的 14 节标准 PRD。

The English summary is being prepared. Showing the original description.

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD

The English summary is being prepared. Showing the original description.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

The English summary is being prepared. Showing the original description.

Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.

The English summary is being prepared. Showing the original description.

Turn the current conversation context into a PRD and submit it as a GitHub issue. Use when user wants to create a PRD from the current context.

The English summary is being prepared. Showing the original description.

PRD 到高保真 UI 交付对齐 / 桌面工作台 UI mockup：当用户已有 PRD、UI 规范、真实前端项目路径、截图或页面状态清单， 需要先从 PRD 提炼 UI 结构、状态模型和 ASCII 布局，再进入高保真 mockup、项目原生 preview 或开发交付 handoff 时使用。 优先输出项目原生 preview route/component；只有早期概念确认或无法接入真实项目时才输出 standalone HTML。 必须包含结构阶段产物、screen contract、component map、implementation notes、截图/验证结果和 HTML/preview 的迁移边界。

The English summary is being prepared. Showing the original description.

Ticket/PRD intake: product area classification, completeness scoring, RCA, technical assessment. Works with Jira (via mk:jira-issue / jira-as), Linear (via MCP), GitHub (via gh CLI), or manual paste. Triggers: 'analyze ticket', 'intake PRD', 'triage issue', 'classify ticket', 'check ticket'.

The English summary is being prepared. Showing the original description.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

The English summary is being prepared. Showing the original description.

Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.

The English summary is being prepared. Showing the original description.

维护每个功能一份给人看的「需求设计文档」（docs/modules 下，一个功能一份）：待拍板置顶，按需写背景、目标、流程、布局、状态、交互细节、业务规则、召回、AI 生成（prompt）、效果、成本、系统，先图后字，只写当前设计，末尾记关键改动，附出图与上线前检查。新建、更新、同步、补充这份文档都用它，别直接手改——它有固定写法和检查。用户说「出设计文档」「PRD 太长看不懂」「把设计文档同步一下」「重拍截图」「上线前看文档跟上没有」时用；用户抱怨看不到功能现在的设计、不知道最近改了什么时也用；forge 各阶段改了规则、文案、交互、布局、阈值、prompt、模型、架构后收尾也用，哪怕用户没明说。不处理写给 AI 的 PRD/DESIGN（forge-prd、forge-design）、骨架上定布局（forge-design-lab）、改 prompt 本身（prompt-craft）、进度（forge-status）。

The English summary is being prepared. Showing the original description.

维护每个功能一份给人看的「需求设计文档」（docs/modules 下，一个功能一份）：待拍板置顶，按需写背景、目标、流程、布局、状态、交互细节、业务规则、召回、AI 生成（prompt）、效果、成本、系统，先图后字，只写当前设计，末尾记关键改动，附出图与上线前检查。新建、更新、同步、补充这份文档都用它，别直接手改——它有固定写法和检查。用户说「出设计文档」「PRD 太长看不懂」「把设计文档同步一下」「重拍截图」「上线前看文档跟上没有」时用；用户抱怨看不到功能现在的设计、不知道最近改了什么时也用；forge 各阶段改了规则、文案、交互、布局、阈值、prompt、模型、架构后收尾也用，哪怕用户没明说。不处理写给 AI 的 PRD/DESIGN（forge-prd、forge-design）、骨架上定布局（forge-design-lab）、改 prompt 本身（prompt-craft）、进度（forge-status）。

The English summary is being prepared. Showing the original description.

Edit an existing PRD. Use when the user says "edit this PRD".

The English summary is being prepared. Showing the original description.

Create a PRD from scratch. Use when the user says "lets create a product requirements document" or "I want to create a new PRD"

The English summary is being prepared. Showing the original description.

多格式需求文档分析与整合。自动解析 Markdown、Excel、Word、思维导图文件，智能去重和补充需求信息，生成标准化的 PRD.md 文档。大文件采用分层提取避免上下文溢出；支持用户指定子目录输出；支持完整版/业务摘要版模板。可选集成 pencil-designer 生成可视化原型。适用场景：用户有多个需求来源需要整合、需要从零梳理需求、需要将模糊想法转化为结构化 PRD、需要可视化原型。触发词：需求分析、分析需求、整理需求、PRD、需求文档、需求梳理、梳理需求、可视化原型、页面设计。

The English summary is being prepared. Showing the original description.

Pre-PRD Research methodology combining Business Analysis, Creative Problem-Solving, Brainstorming, and Innovation Strategy. Use before writing any PRD for problem validation, market research, competitive analysis, stakeholder interviews, ideation, root cause analysis.

The English summary is being prepared. Showing the original description.

Per-screen design spec generator for AI design tools (Stitch / Figma AI / Codex artifacts). Consumes per-feature PRDs from kta-prd-pipeline. Emits tool-agnostic markdown specs. Triggers — design spec, AI design prompt, screen mockup brief, Figma AI input, Stitch prompt, design system tokens, post-PRD design phase, generate design specs, design brief, mockup spec. DOES NOT generate Compose code, Kotlin code, or @Preview stubs.

The English summary is being prepared. Showing the original description.

Per-screen design spec generator for AI design tools (Stitch / Figma AI / Claude artifacts). Consumes per-feature PRDs from kta-prd-pipeline. Emits tool-agnostic markdown specs. Triggers — design spec, AI design prompt, screen mockup brief, Figma AI input, Stitch prompt, design system tokens, post-PRD design phase, generate design specs, design brief, mockup spec. DOES NOT generate Compose code, Kotlin code, or @Preview stubs.

The English summary is being prepared. Showing the original description.

Create, update, or validate a PRD. Use when the user wants help producing, editing, or validating a PRD.

The English summary is being prepared. Showing the original description.

Use when the user asks about the pwdev-prd audit trail — 'auditoria do prd', 'eventos', 'decisões registradas', 'audit report', 'exportar relatório de auditoria' — querying the shared SQLite database read-only (summary, events, decisions, artifacts, stats, export, query).

The English summary is being prepared. Showing the original description.

Turn the current conversation context into a PRD draft. Use when user wants to create a PRD from the current context; publish it to an issue tracker only after explicit approval.

The English summary is being prepared. Showing the original description.