菜单
Requirements authoring guide for BRD and PRD across Discover, Define, and Govern with canonical templates and handoff contracts
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/microsoft/hve-core --skill requirements-author命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Canonical documentation capability for audit, drift, validate, and author modes in hve-core.
Author, review, or validate Copilot prompt-engineering artifacts through independent review, behavior testing, and host checks.
Decision-driven HVE-Core installer with multiple clone-based and extension install methods, environment detection, and selective component installation
基于 SOC 职业分类
正在显示 SKILL.md
| name | requirements-author |
| description | Requirements authoring guide for BRD and PRD across Discover, Define, and Govern with canonical templates and handoff contracts |
| license | CC-BY-4.0 |
| user-invocable | false |
| metadata | {"authors":"microsoft/hve-core","spec_version":"1.1","last_updated":"2026-06-14"} |
This skill defines how to produce and evolve requirements documents across the project lifecycle for two document types: the Business Requirements Document (BRD) and the Product Requirements Document (PRD). Shared requirements-engineering knowledge lives in references/_shared/, while BRD-specific and PRD-specific knowledge live in references/brd/ and references/prd/ so each consuming agent loads only what its document needs.
The canonical BRD template is brd-full.md with its brd-frontmatter-overlay.md, and the canonical PRD template is prd-full.md. The BRD Builder dispatches into the BRD phase anchors (#discover, #define, #govern); the PRD Builder dispatches into the PRD phase anchors ( through ).
#prd-assess#prd-finalizeUse this skill with the references for the active document scope:
Shared (references/_shared/):
BRD scope (references/brd/):
PRD scope (references/prd/):
| Phase | Primary objective | Entry condition | Exit condition |
|---|---|---|---|
| Discover | Establish business context, stakeholder scope, and problem framing | Request or initiative is in intake | Discover hard gate passes and artifacts are complete |
| Define | Produce complete, testable, and traceable requirements content | Discover artifacts are approved for elaboration | Define hard gate passes with quality evidence |
| Govern | Finalize, approve, and supersede BRD versions under lineage controls | Define package is approved for governance review | Govern hard gate passes and publication artifacts are recorded |
Discover exits only when:
Define exits only when:
fr_to_ac_coverage_threshold_pct or has a recorded blocker.0.x.y versions to 1.0.0 or higher.Before emitting BRD_TO_PRD_HANDOFF_V1, the BRD Builder applies the coverage and waiver validation rules in BRD-to-PRD Handoff, including zero-FR coverage handling. It records the following values from the signed-off BRD and final quality review:
BRD_QUALITY_REPORT_V1 reference, overall status, and Govern decision.Govern exits only when:
Use the following status values for BRD lifecycle tracking:
draft: Actively authored or revised.in-review: Under formal review and gate validation.approved: Accepted for governed use.superseded: Replaced by a newer approved BRD.Apply the BRD quality rubric and payload contracts from BRD Quality Formats together with guidance in Requirements Definition. Treat rubric results as gate evidence for Define and Govern decisions. The BRD Quality Reviewer emits both standard findings and the consolidated quality report.
supersedes and superseded_by links.The PRD Builder agent runs a seven-phase lifecycle. Each phase has its own section anchor below so the agent loads only the guidance for the active phase.
| Phase | Section anchor | Primary objective |
|---|---|---|
| Assess | #prd-assess | Determine whether enough context exists to create PRD files. |
| Discover | #prd-discover | Establish the PRD title, scope, and product goals. |
| Create | #prd-create | Generate the PRD file and state file once context is clear. |
| Build | #prd-build | Gather detailed requirements iteratively. |
| Integrate | #prd-integrate | Incorporate references, documents, and external materials. |
| Validate | #prd-validate | Ensure completeness and quality before approval. |
| Finalize | #prd-finalize | Deliver the complete, actionable PRD. |
BRD_TO_PRD_HANDOFF_V1 payload and ingest its coverage and waiver context when present.kind, verify required metadata, verdict field presence, and a readable workspace-relative study path. Treat feasibility as supplementary evidence and preserve approved BRD scope.Assess exits only when:
kind, has readable workspace-relative paths, a valid verdict shape, and normalized metadata ready for Create or persisted in existing state.Discover exits only when:
feasibilityHandoff, carrying kind, path, ingestedAt, verdict, and studyRevisionId. State written before this contract may carry schemaVersion instead of kind; read it without error and rewrite the object to the current shape on the next feasibility metadata update. Do not persist raw candidate content.Create exits only when:
feasibilityHandoff is present, read candidate content from its workspace-relative path. Stop if ingestion was reported but metadata is absent or the path is unreadable.accepted-fr, accepted-nfr, accepted-constraint, retained-gap, rejected, or deferred. Treat concern hints as advisory evidence only.FR-###, NFR-###, or CON-### identifiers only after authoring and accepting the PRD statement. Preserve source handoff ID, source candidate ID, evidence references, disposition, rationale, and resulting PRD ID in the Feasibility Candidate Disposition register.Build exits only when:
Integrate exits only when:
PRD_STANDARD_FINDINGS_V1 and PRD_QUALITY_REPORT_V1 per PRD Quality Formats.Validate exits only when:
gate_decisions.validate_exit.Finalize exits only when:
gate_decisions.finalize_exit.The skill bundles reference documents under references/, organized into three scopes: shared requirements-engineering knowledge in references/_shared/, BRD-specific knowledge in references/brd/, and PRD-specific knowledge in references/prd/. Load a reference body only when its phase activity requires it; each body links to its own sub-references (standards pointers, scoring sheets, and worked examples).
references/_shared/)DD-### design decision codes.RISK / CAUTION / COVERED / NOT_APPLICABLE) and the gate decision rule.references/brd/)references/prd/)Templates under templates/ are selected by the document frontmatter and canonical document shape.
diagram_format, lineage, coverage thresholds, and requirement-prefix overrides.Payload contracts govern quality assessment and downstream handoff for each document type. The quality and BRD handoff payloads carry a fixed schema_version; consumers fail fast on any other value, so those constants MUST NOT change. The feasibility-to-PRD handoff instead carries a plain kind marker, because its producer and consumer ship together and no version negotiation applies.
BRD data contracts:
| Contract | schema_version | Reference |
|---|---|---|
| Standard findings | BRD_STANDARD_FINDINGS_V1 | brd-standard-findings-v1.md |
| Quality report | BRD_QUALITY_REPORT_V1 | brd-quality-report-v1.md |
| BRD-to-PRD handoff | BRD_TO_PRD_HANDOFF_V1 | brd-to-prd-handoff-v1.md |
PRD data contracts:
| Contract | schema_version | Reference |
|---|---|---|
| Standard findings | PRD_STANDARD_FINDINGS_V1 | prd-standard-findings-v1.md |
| Quality report | PRD_QUALITY_REPORT_V1 | prd-quality-report-v1.md |
Upstream PRD input contracts:
| Contract | Identifier | Reference |
|---|---|---|
| BRD-to-PRD handoff | schema_version: BRD_TO_PRD_HANDOFF_V1 | brd-to-prd-handoff-v1.md |
| Feasibility-to-PRD handoff | kind: feasibility-to-prd-handoff | feasibility-to-prd-handoff.md |
The PRD lifecycle consumes both upstream contracts during Assess. BRD input supplies approved business context, coverage, and waivers. Feasibility input supplies a confirmed verdict, evidence, constraints, gaps, and candidate proposals for PRD Build. Neither contract bypasses PRD authoring.
The BRD Builder and PRD Builder agents each enforce a phase → section load contract. Each phase MUST load its section of this skill before executing phase work, and MUST append the section anchor to state.phaseSkillsLoaded.
BRD Builder directives:
| Phase | Section anchor | Required phaseSkillsLoaded entry |
|---|---|---|
| Discover | #discover | brd-author#discover |
| Define | #define | brd-author#define |
| Govern | #govern | brd-author#govern |
PRD Builder directives:
| Phase | Section anchor | Required phaseSkillsLoaded entry |
|---|---|---|
| Assess | #prd-assess | prd-author#assess |
| Discover | #prd-discover | prd-author#discover |
| Create | #prd-create | prd-author#create |
| Build | #prd-build | prd-author#build |
| Integrate | #prd-integrate | prd-author#integrate |
| Validate | #prd-validate | prd-author#validate |
| Finalize | #prd-finalize | prd-author#finalize |
The agent loads sections via read_file against this skill file and records the entry in state.phaseSkillsLoaded before any phase work executes. Re-entering a previously loaded phase does not require reloading; the agent checks phaseSkillsLoaded first.
The bundled reference bodies cite third-party standards and frameworks by name and clause only; no upstream prose is reproduced or paraphrased. Where a reference names a standard's characteristics or categories, the accompanying review criteria, anchors, and indicators are original Microsoft content under CC BY 4.0, not reproductions of the standard's definitions; the authoritative definitions live in the cited standards. The cite-only registry in standards-excerpts.md is the single place new standards citations are added. Standards referenced by name include ISO/IEC/IEEE 29148:2018, ISO/IEC 25010:2023, IIBA BABOK v3, PMI Business Analysis for Practitioners, the ISTQB Glossary, OMG BPMN / DMN / UML, the Cucumber Gherkin pattern, and MoSCoW prioritization, each the property of its respective rights holder.
This skill is original Microsoft content licensed under CC BY 4.0.