What is requirements-author?

A guide for writing Business Requirements Documents and Product Requirements Documents. These documents explain what a business or product needs, why it needs it, and how the work is checked across discovery, definition, and governance.

Use it to create or update BRDs and PRDs, define product requirements, record acceptance criteria, and hand work from business analysis to product planning.

It provides shared templates and handoff rules so requirements remain clear and traceable as they move from an idea to product development.

requirements-author — Skill for Claude Code by microsoft/hve-core

About the project

HVE Core is a collection of agents, prompts, coding instructions, and skills for building repeatable software-development workflows with GitHub Copilot. It is intended for individuals and teams that want structured AI-assisted research, planning, implementation, and review, while the catalogue entries provide many of its reusable workflow components.

microsoft/hve-core · 1,606 stars · on GitHub

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add microsoft/hve-core --skill requirements-author

Clone the repo

git clone --depth 1 https://github.com/microsoft/hve-core

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/microsoft/hve-core/requirements-author/github.svg)](https://agentmods.dev/skills/microsoft/hve-core/requirements-author)

Your own site

<a href="https://agentmods.dev/skills/microsoft/hve-core/requirements-author"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/requirements-author/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/microsoft/hve-core/requirements-author"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/requirements-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 6,144 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00027	$0.06144
Opus 5.5	$0.00011	$0.02458
Sonnet 5.5	$0.00005	$0.01229
Haiku 4.5	$0.00003	$0.00614

Measured yesterday against content hash 139251eafb79, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

requirements-author scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/skills/project-planning/requirements-author/SKILL.md · 487 lines

How it starts

The opening of the file, as written. The whole thing — 487 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Requirements Author Skill

Overview

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 (#prd-assess through #prd-finalize).

Use this skill with the references for the active document scope:

Shared (references/_shared/):

BRD scope (references/brd/):

PRD scope (references/prd/):

Handoff Transport Convention

The producing workflow owns each handoff's canonical transport, and the consumer validates the complete payload regardless of transport. An outcome hypothesis returns OUTCOME_HYPOTHESIS_TO_BRD_HANDOFF_V1 inline by default because it is a one-time seed derived from an already persisted source artifact; the user may instead supply a separately persisted payload path. BRD Govern persists BRD_TO_PRD_HANDOFF_V1 and returns its path because that payload is a durable governance record consumed across agent sessions. This asymmetry is intentional and does not change payload authority or validation.

Read the full file on GitHub · 487 lines

Files

What ships with it

45 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

yesterday Changed 139251eafb79
1mo ago Changed 5bdda423e71e
1mo ago Changed · +1 lines 567c468b57d9
2mo ago First seen · 486 lines · 27 tokens per session scan A 971e34e139b6

Subscribe to this mod's changes

requirements-author is a skill published in the GitHub repository microsoft/hve-core (1,606 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 6,144 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Planning Writing and docs

requirements-author next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
requirements-authormicrosoft/hve-core	Skill	1.6k	today	MIT	A	27	Claude Code
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code