What is trace-requirements?

A requirements-tracing command that maps acceptance criteria to test cases using Given-When-Then descriptions. Given-When-Then is a plain format for stating a starting situation, an action, and the expected result.

Building a requirements traceability matrix from user stories, acceptance criteria, tasks, non-functional requirements, and documented edge cases.

It exposes requirements that do not yet have matching test coverage and makes the connection between a story and its tests easier to check.

How julianobarbosa/azure-finops-mcp-server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to julianobarbosa/azure-finops-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/julianobarbosa/azure-finops-mcp-server/main/.claude/commands/BMad/tasks/trace-requirements.md

Clone the repo

git clone --depth 1 https://github.com/julianobarbosa/azure-finops-mcp-server

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/commands/julianobarbosa/azure-finops-mcp-server/trace-requirements/github.svg)](https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/trace-requirements)

Your own site

<a href="https://agentmods.dev/commands/julianobarbosa/azure-finops-mcp-server/trace-requirements"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/trace-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/commands/julianobarbosa/azure-finops-mcp-server/trace-requirements"><img src="https://agentmods.dev/badge/commands/julianobarbosa/azure-finops-mcp-server/trace-requirements.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,600 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 100% copy Near-identical to another mod 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.00000	$0.01600
Opus 5	$0.00000	$0.00800
Sonnet 5	$0.00000	$0.00320
Haiku 4.5	$0.00000	$0.00160

Measured 12d ago against content hash 427033235151, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

trace-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 12d ago.

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.

Origin

This is a copy

100% identical to trace-requirements — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/BMad/tasks/trace-requirements.md · 271 lines

How it starts

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

/trace-requirements Task

When this command is used, execute the following task:

trace-requirements

Map story requirements to test cases using Given-When-Then patterns for comprehensive traceability.

Purpose

Create a requirements traceability matrix that ensures every acceptance criterion has corresponding test coverage. This task helps identify gaps in testing and ensures all requirements are validated.

IMPORTANT: Given-When-Then is used here for documenting the mapping between requirements and tests, NOT for writing the actual test code. Tests should follow your project's testing standards (no BDD syntax in test code).

Prerequisites

Story file with clear acceptance criteria
Access to test files or test specifications
Understanding of the implementation

Traceability Process

1. Extract Requirements

Identify all testable requirements from:

Acceptance Criteria (primary source)
User story statement
Tasks/subtasks with specific behaviors
Non-functional requirements mentioned
Edge cases documented

2. Map to Test Cases

For each requirement, document which tests validate it. Use Given-When-Then to describe what the test validates (not how it's written):

requirement: 'AC1: User can login with valid credentials'
test_mappings:
  - test_file: 'auth/login.test.ts'
    test_case: 'should successfully login with valid email and password'
    # Given-When-Then describes WHAT the test validates, not HOW it's coded
    given: 'A registered user with valid credentials'
    when: 'They submit the login form'
    then: 'They are redirected to dashboard and session is created'
    coverage: full

  - test_file: 'e2e/auth-flow.test.ts'
    test_case: 'complete login flow'
    given: 'User on login page'
    when: 'Entering valid credentials and submitting'
    then: 'Dashboard loads with user data'
    coverage: integration

3. Coverage Analysis

Evaluate coverage for each requirement:

Read the full file on GitHub · 271 lines

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.

12d ago First seen · 271 lines · 0 tokens per session scan A 427033235151

Subscribe to this mod's changes

trace-requirements is a command published in the GitHub repository julianobarbosa/azure-finops-mcp-server (2 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,600 tokens. A static security scan graded it A with 0 findings. It is 100% identical to trace-requirements, differing in 0 lines, and is treated as a copy.

Testing

prototype

You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.

grainulation/grainulator · 0 tokens

qa-changes

This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…

OpenHands/extensions · 63 tokens

azure-finops-mcp-server: Command for Claude Code