spec-prd

在存量系统上写 PRD 级增量需求，基于 current-state evidence 描述 change delta，让 plan 不用猜 WHAT。

ASCII 链路图

Codebase -> Spec -> Plan -> Tasks -> Code -> Review -> Knowledge
              |
              v
              spec-prd
              entry: spec-prd
              type: workflow command

基本信息

字段	内容
Skill	spec-prd
类型	workflow command
研发链路位置	Spec
当前入口	spec-prd
兼容别名	/spec:prd、$spec-prd
Source	skills/spec-prd/SKILL.md
Governance	src/cli/contracts/dual-host-governance/skills-governance.json（supported-host skills governance）

描述

Public workflow entrypoint (spec-prd): create, write, refine, or validate planning-readiness of brownfield PRD-grade requirements for existing systems before implementation planning. Do not use for 0-1 product exploration, unresolved product shape, HOW planning/task compilation, implementation/debug/review, lightweight direct fixes, generated runtime mirror edits, or PRD/design-source/source consistency audits; route to spec-brainstorm, spec-plan/spec-write-tasks, spec-work, review workflows, or spec-app-consistency-audit as appropriate.

Source 契约摘要

When To Use

Use for brownfield increment PRD authoring, existing PRD refinement, and code-aware PRD validation when the product owner already knows the existing product/system surface being changed.

When Not To Use

Do not use for 0-1 product exploration, unresolved product shape, implementation planning, task execution, debugging, PRD/design-source/source audit, or requests that only need a lightweight direct fix.

Inputs

An increment request, existing PRD or requirements draft, rough Markdown notes, extracted multimodal material (image/PDF/meeting-notes/chat-log transcripts), source/docs evidence, current-system context, domain terms, and product-owner decisions.

Outputs

A PRD-grade requirements artifact for create/refine, concise optimization suggestions for refine, a source-resolved compact PRD or explicit route-out when PRD authoring adds no durable WHAT value, a split-decision summary pending owner confirmation, or a report-only validation result with source/checker facts, blockers, questions, and readiness outcome.

Artifacts

Requirements artifacts under docs/brainstorms/ using artifact_kind: prd-requirements, optional split summary and child PRDs for owner-confirmed oversized initial PRDs, and no generated runtime mirror edits.

Failure Modes

Missing target surface, unresolved product identity, current-state claims without evidence, owner decisions that would change scope, unconfirmed source candidates presented as confirmed truth, or PRD readiness gaps that would force planning to invent WHAT.

Workflow

Classify intent and input mode, gather current-state evidence, run the Requirement Analysis Gate to map materials into understanding, uncertainty/contradiction points, grill decisions, and PRD write targets, then branch: create/refine may write after closure and run finalize; validate runs readiness/check-only and returns a report without mutation. Hand off to refine, doc review, plan, or done from the observed result.

Downstream Consumers

spec-plan, spec-doc-review, product owners, implementation reviewers, and future work/review flows that need stable PRD-grade WHAT/WHY context.

何时使用

• 面向已有产品的增量需求（1-10 / 10-100 阶段）。
• 需要 PRD 级需求文档，区分 keep / extend / replace / remove。
• 需要把领域术语、当前行为和变更范围显式化。

工作步骤

• 读取用户意图、代码库背景、已有 requirements、历史学习和外部证据。
• 收敛问题框架、用户流、边界、验收标准或候选方向。
• 区分必须现在解决的问题和可延后到计划或实现阶段的问题。
• 把 WHAT 层证据交给 plan 或 doc-review。

输出

• requirements、ideation artifact、scope boundaries 或 open questions。
• 可供计划阶段追溯的 actors、flows、acceptance examples 和关键决策。

Agent 调度

• 可按需要引入 spec-flow、product、design、security、repo、web 或 issue research agents。
• agent 产出是证据和问题发现，最终需求边界仍由当前 workflow 汇总。

本 skill 当前没有 skill-local references/agents 或 references/personas 文件；默认由 orchestrator 直接完成，或按阶段需要临时调用其他 skill 的专家。

边界

• 0-1 全新方向探索应走 brainstorm 或 ideate。
• 不写实现计划，HOW 交给 spec-plan。

源码校准

• 本页由 website/scripts/generate-skill-detail-pages.js 从上游 source skill 生成。
• 当前入口、兼容别名与宿主投递 metadata 来自 src/cli/contracts/dual-host-governance/skills-governance.json。
• 当 source skill 或 governance contract 变化后，应重新运行 npm run reference:pages 并执行 npm run content:audit。