What is handoff-requirements?

A guide for writing structured software requirements, specifications, acceptance criteria, and test items in V-model documents. The V-model is a development approach that links requirements to verification and testing.

It is for creating requirement trees, acceptance criteria, test items, traceability links, and documented exceptions.

It helps teams write consistent requirement records and keep each requirement linked to the tests or checks that verify it.

handoff-requirements — Skill by alphaelements/handoff-mcp

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 alphaelements/handoff-mcp --skill handoff-requirements

Clone the repo

git clone --depth 1 https://github.com/alphaelements/handoff-mcp

Made for: Claude Code, Codex.

Or install handoff-mcp, the plugin that ships this one along with the rest of its 8 skills.

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/alphaelements/handoff-mcp/handoff-requirements/github.svg)](https://agentmods.dev/skills/alphaelements/handoff-mcp/handoff-requirements)

Your own site

<a href="https://agentmods.dev/skills/alphaelements/handoff-mcp/handoff-requirements"><img src="https://agentmods.dev/badge/skills/alphaelements/handoff-mcp/handoff-requirements/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/alphaelements/handoff-mcp/handoff-requirements"><img src="https://agentmods.dev/badge/skills/alphaelements/handoff-mcp/handoff-requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 5,440 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.

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.00155	$0.05440
Opus 5.5	$0.00062	$0.02176
Sonnet 5.5	$0.00031	$0.01088
Haiku 4.5	$0.00015	$0.00544

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

Security

Grade A, and why

handoff-requirements 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.

plugin/skills/handoff-requirements/SKILL.md · 331 lines

How it starts

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

Handoff Requirements Skill (authoring V-model items)

How to write items in V-model layer documents so the traceability engine reads them the way you intend. For the system overview, setup, verification, change tracking and the full tool reference, see the handoff-trace skill.

Per-layer copy-paste templates: references/templates.md
Decomposing requirements into a tree (parent / kind / condition / order, decision and select branches): references/requirement-tree.md
Finding non-functional requirements systematically (ISO/IEC 25010 checklist, questions per quality characteristic, how to file NFR-nnn items): references/nfr-checklist.md
Gate checklists to pass before moving to the next requirements phase (six gates, deliverables, quality bar, tool commands): references/preflight-checklists.md

0. Before you write

Is the V-model on? A fresh handoff_init writes no [trace] section. Check handoff_get_config (or .handoff/config.toml) for [trace] profile / layers. If neither is set, follow the handoff-trace skill's "First-time setup" first — otherwise the item you write may be counted against the wrong set of layers.

Which profile? It decides which layers you must fill:

profile	layers you write	acceptance criteria become verification items automatically?
`minimal`	requirement (+ acceptance)	yes
`standard`	requirement, basic_spec, acceptance, system_test	no — write explicit test items
`full`	all six	no
`bugfix`	requirement ("再現条件"), acceptance ("回帰テスト")	yes

Check for duplicates first: handoff_trace_propose(title: "...") returns similar existing items (candidates) and a ready template (proposal.markdown, proposal.next_ids) sized to the profile. It writes nothing. The proposed ID uses the layer's default prefix (REQ-001); for a scope prefix you registered (CART, PAY) pass prefix: "CART" to get the next free CART-nnn, or use trace_propose(parent: ...), which numbers children after their parent (CART-001-003; under a decision/select parent the template carries a - condition: TBD line to give a label). Every fill-in slot in the template is the marker TBD — replace them.

Read the full file on GitHub · 331 lines

Files

What ships with it

5 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 · +29 lines 9d153117df9c
3d ago First seen · 302 lines · 155 tokens per session scan A 3d5714803e8b

Subscribe to this mod's changes

handoff-requirements is a skill published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 155 tokens to every session and 5,440 once invoked, about $0.0006 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-10-19.

Planning Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

handoff-requirements