create-srs

Compile an IEEE 29148:2018 Software Requirements Specification from approved elicitation documents and accepted epics.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/4797pnkkx5-gif/AI-Augmented-RE --skill create-srs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-srs
Source: https://github.com/4797pnkkx5-gif/AI-Augmented-RE/tree/main/skills/create-srs
Command: npx skills add https://github.com/4797pnkkx5-gif/AI-Augmented-RE --skill create-srs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns an Approved elicitation model plus Accepted epics and stories into a single, implementation-ready Software Requirements Specification (SRS) that teams can review and sign off—while preserving traceability and preventing accidental changes to already Accepted specifications.

Core Features & Use Cases

  • Review-gated SRS compilation: Blocks compilation unless every Story under every Accepted Epic is Accepted, ensuring the SRS is a settled contract.
  • IEEE 29148:2018 structure with partial-by-Epic scope: Generates Introduction, Overall Description, System Features (per epic), FR/NFR/CON consolidation, External Interfaces, Acceptance Criteria, and an always-rebuilt Traceability Matrix.
  • Idempotent reruns with immutability rules: Regenerates freely when Pending; when Accepted, it keeps Sections 1–8 unchanged and refreshes only Traceability/Revision notes to reflect upstream changes.

Quick Start

Run the create-srs skill to compile artifacts/04-srs/srs.md from the approved elicitation document and the Accepted epic/story set.

Frequently Asked Questions about create-srs

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

FAQPage Schema
How do I compile an IEEE 29148 software requirements specification from elicited epics and stories?▼

To compile an IEEE 29148 software requirements specification, you need an Approved elicitation document plus Accepted epics and stories. The skill consolidates FR, NFR, constraints, and acceptance criteria into a single implementation-ready SRS document.

How does traceability matrix generation work during SRS compilation?▼

Traceability matrix generation works by automatically rebuilding the matrix during SRS compilation. It maps consolidated functional requirements, non-functional requirements, and constraints back to their source epics and stories to ensure full requirements traceability.

Can I regenerate an already Accepted software requirements specification without losing previous approvals?▼

You cannot change Accepted software requirements specifications freely. Immutability rules keep SRS sections 1 through 8 unchanged while refreshing only the Traceability Matrix and Revision notes to reflect upstream changes.

What happens if some stories under an Accepted epic are still pending during SRS generation?▼

SRS generation is blocked if stories under an Accepted epic are still pending. Strict review-gating ensures every story is Accepted before consolidating the software requirements specification into a settled contract.

Does the SRS compilation process support idempotent reruns for pending requirements?▼

The SRS compilation process supports idempotent reruns for pending requirements. You can regenerate the specification freely while in a Pending state without duplicating content or breaking existing traceability links.

When do I need an IEEE-ready SRS with a rebuilt traceability matrix for my AI agent workflow?▼

You need an IEEE-ready SRS with a rebuilt traceability matrix for your AI agent workflow when consolidating iteratively elicited requirements. It provides a reviewable contract ensuring all functional and non-functional requirements are validated and traced.