req-add

Mint a new REQ ID and append it to the requirements-spec.

41|6|Updated Jul 12, 2025
One-click install
npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill req-add
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: req-add
Source: https://github.com/SteveGJones/ai-first-sdlc-practices/tree/main/plugins/sdlc-assured/skills/req-add
Command: npx skills add https://github.com/SteveGJones/ai-first-sdlc-practices --skill req-add

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mint a new REQ ID in the Assured project's namespace, with module assignment, and append it to the requirements-spec.

Core Features & Use Cases

  • Compute the next sequential REQ number by scanning existing ### REQ-... sections and pad to 3 digits.
  • Append a properly formatted REQ entry including the Module field, ensuring consistency with the requirements-spec structure.
  • Show a diff before saving and remind the user to add a corresponding DES in design-spec.md (use req-link) and a TEST in test-spec.md.

Quick Start

Mint a new REQ ID in the Assured project's namespace, assign it to the target module, and append it to the requirements-spec.

Frequently Asked Questions about req-add

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

FAQPage Schema
How do I generate the next requirement ID in a requirements-spec file?

To generate a requirement ID, the Skill scans existing REQ sections to compute the next sequential number, zero-pads it to 3 digits, appends the formatted entry to your requirements-spec, and presents a diff for confirmation.

What is the correct format for appending requirements to a module-level spec?

The correct format involves appending a properly formatted REQ section that includes the Module field, ensuring structural consistency within the requirements-spec file for your target module.

Can I automatically assign module information when adding new requirements?

Yes, you can assign module information during requirement ID generation, as the Skill mints the new REQ ID within the project namespace and includes the module assignment directly in the appended specification text.

Does generating requirement IDs require an existing requirements-spec document?

Generating requirement IDs requires an existing spec document, because the Skill reads docs/specs/<feature-id>/requirements-spec.md or the corresponding module-level spec to locate the correct file and compute the next sequence.

What should I do after adding a new REQ entry to the requirements-spec?

After adding a new REQ entry, you should add a corresponding DES in design-spec.md using req-link and a TEST in test-spec.md to maintain full specification traceability across your documentation.