What is requirements-tracking?

A way to define, track, check, and promote project requirements for SysMLv2 modeling. Requirements are statements of what a system or model must do; EARS is a structured format for writing them.

Use it to work with requirement files, project and modeling rules, validation methods, compliance checks, and design reviews.

It helps keep requirements visible and makes it clearer how they are enforced, validated, reviewed, and changed.

How 1cFE/fusion-tea configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to 1cFE/fusion-tea. 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/1cFE/fusion-tea/main/.agents/skills/requirements-tracking/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/1cFE/fusion-tea

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/1cfe/fusion-tea/requirements-tracking/github.svg)](https://agentmods.dev/skills/1cfe/fusion-tea/requirements-tracking)

Your own site

<a href="https://agentmods.dev/skills/1cfe/fusion-tea/requirements-tracking"><img src="https://agentmods.dev/badge/skills/1cfe/fusion-tea/requirements-tracking/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/1cfe/fusion-tea/requirements-tracking"><img src="https://agentmods.dev/badge/skills/1cfe/fusion-tea/requirements-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,797 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.00106	$0.01797
Opus 5.5	$0.00042	$0.00719
Sonnet 5.5	$0.00021	$0.00359
Haiku 4.5	$0.00011	$0.00180

Measured 24d ago against content hash 8189960e2e3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

requirements-tracking 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 24d 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.

.agents/skills/requirements-tracking/SKILL.md · 141 lines

How it starts

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

Before executing this skill, read .agentic-mbse/claude.md in Claude Code or .agentic-mbse/codex.md in Codex. Resolve supporting paths from this skill’s installed directory; keep generated outputs in the project or a temporary directory. Read referenced skills from .agents/skills/<name>/SKILL.md when their guidance is needed.

Requirements Tracking

Two-tier requirements structure, PR-XXX format, promotion path, and enforcement methods.

Core Principle

Modeling requirements exist at two tiers: tool-owned baseline rules that apply to all projects (MODELING_GUIDE.md, MODELING_PROCESS.md, and the toolkit pattern references they name), and user-owned extensions (REQUIREMENTS.md) that capture project-specific rules. A project rule that applies a baseline rule cites it and states only the project's application. Per-feature MR-XXX requirements are ephemeral — only significant, durable ones are promoted to project-wide PR-XXX entries.

When to Reference

/spec-model — writing per-feature MR-XXX requirements
/design-model — checking compliance against PR-XXX rules
/implement-model — enforcing requirements during implementation, promoting MR-XXX → PR-XXX
/audit-models — verifying compliance across features
/backlog — understanding requirement-linked success criteria

Two-Tier Requirements

Tier	File	Owner	Contains	Stability
Baseline	`modeling_project/MODELING_GUIDE.md`, `modeling_project/MODELING_PROCESS.md`, toolkit `docs/patterns/`	Tool (updated by `agentic-mbse init`)	Universal modeling and process rules, such as design-choice preservation (`design-choices.md`)	Stable across versions
Extensions	`modeling_project/REQUIREMENTS.md`	User	Project-specific rules (PR-XXX)	Grows slowly, deliberately

What belongs in the baseline: Rules correct for all projects. Examples: "calc defs go in library/, not in designs/"; "a binding does not set installed capacity from demand".

Read the full file on GitHub · 141 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.

24d ago Changed · +7 lines 8189960e2e3f
1mo ago First seen · 134 lines · 106 tokens per session scan A b02d870de9cc

Subscribe to this mod's changes

requirements-tracking is a skill published in the GitHub repository 1cFE/fusion-tea (5 stars, last pushed 24d ago), licensed MIT. It adds 106 tokens to every session and 1,797 once invoked, about $0.0004 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-09-29.

Project management

requirements-tracking next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
requirements-tracking1cFE/fusion-tea	Skill	5	24d ago	MIT	A	106	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

fusion-tea: Skill for Claude Code