requirements-status-tracking

Track requirements through lifecycle states and generate status distribution dashboards with progress metrics.

23|1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-status-tracking-jdm4pku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-status-tracking
Source: https://github.com/jdm4pku/RE-Skills/tree/main/skills/requirements-status-tracking
Command: npx skills add https://github.com/jdm4pku/RE-Skills --skill requirements-status-tracking-jdm4pku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project teams often cannot answer "how far along are we with the requirements?" with data. This Skill establishes a requirements status tracking system that shows where every requirement sits in its lifecycle, exposes bottlenecks, and produces stakeholder-ready progress reports. ## Core Features & Use Cases - Lifecycle State Management: Defines traditional (Proposed to Verified) and agile (Backlog to Accepted) status lifecycles with entry criteria and allowed transition rules. - Status Distribution Dashboards: Generates snapshot reports showing requirement counts and percentages per status, plus progress metrics like specification completeness, implementation progress, verification progress, and churn rate. - Bottleneck and Staleness Detection: Identifies requirements piling up in one status or stuck for multiple sprints, with recommended corrective actions. - Use Case: A project manager preparing for a steering committee uses this Skill to produce a Sprint 6 dashboard showing 85% implementation progress, a verification bottleneck, and two stale requirements with assigned owners. ## Quick Start Ask the agent to build a requirements status dashboard for your project using the current requirement list and report progress metrics with bottleneck analysis.

Frequently Asked Questions about requirements-status-tracking

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

FAQPage Schema
How do I track requirements status across a project lifecycle?▼

Define a status lifecycle (Proposed, In Progress, Drafted, Approved, Implemented, Verified, plus terminal states), assign each requirement an initial status, and update statuses at standups, sprint reviews, and CCB meetings. Generate periodic distribution snapshots and progress metrics.

What metrics should a requirements progress report include?▼

Include specification completeness, implementation progress, verification progress, churn rate, and blocked item counts. Pair each metric with trend direction and a target so stakeholders can judge whether the project is on track.

How is requirements status tracking different in agile projects?▼

Agile teams use a backlog-oriented lifecycle: In Backlog, Defined, In Progress, Completed, Accepted, and Blocked. Statuses update through refinement sessions, sprint planning, and product owner acceptance rather than formal reviews and baselines.

Why do requirements get stuck in one status?▼

Pile-ups usually indicate a process bottleneck: Drafted buildup means reviews are slow, Implemented buildup means testing capacity is insufficient. Requirements unchanged for two or more sprints should be investigated individually.

When should deferred or rejected requirements be removed from tracking?▼

Never remove them. Keep Deferred, Deleted, and Rejected requirements in the register with their terminal status so totals remain consistent and stakeholders can see what happened to previously discussed features.