srs-generation SKILL.md skillA
srs-generation from tercel/spec-forge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tercel/spec-forge/srs-generation@git:20260916.268f496Pins git:20260916.268f496 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tercel/spec-forge
- Path
skills/srs-generation/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260916.268f496, committed Sep 16, 2026
- First version recorded
- Mar 25, 2026
- Size
- 23,793 bytes
- Repository stars
- 10
- License
- MIT
Generates professional Software Requirements Specification (SRS) documents based on IEEE 830, ISO/IEC/IEEE 29148, and Amazon technical specification standards. This skill activates when the user needs a requirements document, requirements specification, SRS, functional requirements, non-functional requirements, software requirements, requirements analysis, or requirements engineering. It formalizes product needs into structured, testable, and traceable requirements with unique IDs, acceptance…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# SRS Generation Skill ## What Is a Software Requirements Specification? A Software Requirements Specification (SRS) is a formal document that describes exactly what a software system must do and the constraints under which it must operate. It serves as the contractual bridge between stakeholders who define the product vision (captured in a PRD) and the engineering team that designs, builds, and tests the system. A well-written SRS eliminates ambiguity, reduces rework, and provides a single source of truth for every requirement the system must satisfy. The two foundational standards for SRS documents are **IEEE 830** (IEEE Recommended Practice for Software Requirements Specifications) and **ISO/IEC/IEEE 29148** (Systems and Software Engineering -- Life Cycle Processes -- Requirements Engineering). IEEE 830 established the canonical section structure -- introduction, overall description, specific requirements -- and defined the quality attributes every requirement must exhibit: correctness, unambiguity, completeness, consistency, ranking for importance, verifiability, modifiability, and traceability. ISO/IEC/IEEE 29148 modernized this foundation by integrating requirements… …
Read the whole file at its exact version.
How to install
mdr add tercel/spec-forge/srs-generation@sha256:738f2ce781a933e0The line at the top of this page pins the label git:20260916.268f496, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_brtdkbqjdwza6ry5)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Mar 25, 2026 and Sep 16, 2026, about one every 44 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260916.268f496 latest | 2026-09-16 | 268f496 | 23,793 B | A | view · diff |
| git:20260719.c80ca98 | 2026-07-19 | c80ca98 | 18,984 B | A | view · diff |
| git:20260409.440560b | 2026-04-09 | 440560b | 17,460 B | A | view · diff |
| git:20260325.bda334c | 2026-03-25 | bda334c | 15,421 B | A | view · diff |
| git:20260325.a3aa0f8 | 2026-03-25 | a3aa0f8 | 15,420 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (23793 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tercel/spec-forge · 10 stars · license MIT · pushed 2026-09-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_brtdkbqjdwza6ry5 GET https://markdownregistry.com/api/v1/resolve?ref=tercel/spec-forge/srs-generation GET https://markdownregistry.com/api/v1/blob/738f2ce781a933e02ec9895ec490e2c00958b514600699866b83afc0f0c9a82c
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.