requirements-tracking

Name: requirements-tracking
Availability: InStock
Author: 1cFE

Track and enforce two-tier modeling requirements across project workflows.

6|1|Updated Jan 2, 2026

Search Tags:#requirements #traceability #enforcement #two-tier #mr-xxx #pr-xxx

Ready to run

npx skills add https://github.com/1cFE/agentic-mbse --skill requirements-tracking

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: requirements-tracking
Source: https://github.com/1cFE/agentic-mbse/tree/main/claude/skills/requirements-tracking
Command: npx skills add https://github.com/1cFE/agentic-mbse --skill requirements-tracking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Two-tier requirements tracking helps teams separate universal, tool-owned modeling rules from project-specific rules, enabling durable governance and consistent enforcement across design, implement, audit phases.

Core Features & Use Cases

Two-Tier Requirements: Baseline modeling rules live in modeling_project/MODELING_GUIDE.md; project-specific extensions live in modeling_project/REQUIREMENTS.md.
Promotion Path: MR-XXX per-feature requirements can be promoted to PR-XXX project-wide rules during implementation.
Compliance & Validation: Rules are expressed in EARS format and checked via design reviews and automated validation where possible.
Traceability: Each rule links back to goals or insights guiding development.

Quick Start

Create a baseline in modeling_project/MODELING_GUIDE.md and a project-specific set of rules in modeling_project/REQUIREMENTS.md to begin enforcing requirements.

Frequently Asked Questions about requirements-tracking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is two-tier requirements traceability in software modeling?▼

Two-tier requirements traceability separates universal, tool-owned modeling rules from project-specific extensions, enabling durable governance and consistent enforcement across design, implement, and audit phases.

How do I enforce project-wide requirements across design and implementation workflows?▼

You can enforce project-wide requirements by defining baseline modeling rules in MODELING_GUIDE.md and project-specific extensions in REQUIREMENTS.md, which apply validation across design, implement, audit, and backlog workflows.

How do I promote per-feature requirements to project-wide rules during implementation?▼

Per-feature MR-XXX requirements can be promoted to project-wide PR-XXX rules during the implementation phase, ensuring that validated feature-level constraints scale to govern the entire project.

Can I use EARS-style requirements formatting with machine-checkable validation rules?▼

Yes, requirements are expressed in EARS format and checked via design reviews and automated machine-checkable validation rules, ensuring strict compliance and traceability back to guiding development goals.

Do I need separate files to set up baseline and project-specific requirement rules?▼

Yes, you need to create a baseline in modeling_project/MODELING_GUIDE.md and a project-specific set of rules in modeling_project/REQUIREMENTS.md to begin enforcing two-tier requirements across your project.

What is the best way to maintain requirements traceability across audit and backlog workflows?▼

The best way to maintain traceability is using a two-tier modeling system where each PR-XXX rule links back to original goals or insights, applying consistent enforcement across audit and backlog workflows.