Requirements maintenance

Skill jt55401/requirements-skill/.codex/skills/requirements-maintenance

Maintain product requirements docs as source-of-truth artifacts, including story decomposition, link hygiene, conflict detection, and changelog-ready summaries. Use when adding/changing/removing requirements, fixing requirement drift, or preparing requirements-focused commit summaries.From its SKILL.md

Install

npx -y skills add jt55401/requirements-skill --skill requirements-maintenance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
runs commandsInstructs the agent to run 4 commands, including `python3 .claude/scripts/check_requirements_conflicts.py --root <requirements-root>` and 3 more.

SKILL.md

2.7 KB, 527 tokens by cl100k_base, as published. Nobody here has run it

Requirements Maintenance

Use this skill to keep requirements docs coherent, navigable, and aligned with implementation evidence.

When To Use

Add or revise requirement stories
Break down vague requirements into single-behavior stories
Repair relative links between requirements and tickets
Detect overlap, duplication, and contradictions before merge
Prepare requirement changelog summaries from conventional commits

Path Setup

Choose paths before editing:

<requirements-register>: top-level register markdown
<requirements-root>: requirements tree root
<tickets-root>: ticket folder linked by requirement stories

For this repository's example:

<requirements-register>: examples/saas-webapp/requirements.md
<requirements-root>: examples/saas-webapp/requirements
<tickets-root>: examples/saas-webapp/tickets

Workflow

Identify impacted area folder(s) in <requirements-root>/.
Edit story files first (smallest unit, one behavior each).
Refresh area indexes and navigation links.
Run conflict detection gate.
Resolve errors; document intentional overlap when warnings are expected.
Update changelog content when requested.
Provide commit-ready requirement summaries with traceable refs.

Authoring Rules

Preserve 4-digit spaced numbering (0110, 0120, ...).
Keep one behavior per story file.
Include these sections in each story:
- User Story
- Key Fields/Parameters
- Acceptance Criteria
- Evidence
- Linked Tickets

Command Gate

Run conflict detection:

python3 .claude/scripts/check_requirements_conflicts.py --root <requirements-root>

PR-focused mode:

python3 .claude/scripts/check_requirements_conflicts.py --root <requirements-root> --changed-only --range HEAD~1..HEAD

Generate changelog snippet:

python3 .claude/scripts/extract_requirements_changelog.py --range HEAD --changelog-file <requirements-root>/CHANGELOG.md

Apply changelog snippet:

python3 .claude/scripts/extract_requirements_changelog.py --range HEAD --changelog-file <requirements-root>/CHANGELOG.md --apply

Commit Convention

Use conventional commit subject:

docs(requirements-<area>): <short requirement summary>

Recommended footers:

Req-Refs: <ids/files>
Changelog: requirements
Req-Summary: <single sentence>

What ships with it: 1 file

351 B alongside SKILL.md

agents/

openai.yaml351 B