requirements-engineering SKILL.md skillC
requirements-engineering from atnexuslab/tightship is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atnexuslab/tightship/requirements-engineering@git:20261015.8e86e2cPins git:20261015.8e86e2c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- C, 14 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atnexuslab/tightship
- Path
content/skills/requirements-engineering/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261015.8e86e2c, committed Oct 15, 2026
- Size
- 6,800 bytes
- Repository stars
- 4
- License
- MIT
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
+++ name = "requirements-engineering" description = "Use when eliciting, analysing, writing, validating, or changing a project's requirements — the docs/requirements/ SRS folder, its requirement IDs and attributes, its versioning, and change control. Based on ISO/IEC/IEEE 29148 and the ISO/IEC 25010 quality model, run inside Scrum sprints." +++ # Requirements Engineering Requirements are not static. They are elicited, analysed, specified, validated, and then **managed**: every change is proposed, analysed for impact, approved, and versioned. A sprint plans against a known version of them. ## The process | Phase | What happens | Output | | --- | --- | --- | | **Elicitation** | Interview the stakeholders; read the repo, the ADRs, the existing product. Ask only what cannot be inferred. | Raw needs, each with its source | | **Analysis** | Classify each need (functional, non-functional, business rule, constraint), find conflicts, duplicates, and dependencies, check feasibility, prioritise with MoSCoW. | Needs settled with the stakeholder | | **Specification** | Write each need as a requirement with its ID and attributes, into the SRS. | `docs/requirements/` | …
Read the whole file at its exact version.
How to install
mdr add atnexuslab/tightship/requirements-engineering@sha256:7bf1f2263a40c882The line at the top of this page pins the label git:20261015.8e86e2c, 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_kppa3ic2s3wfw2yt)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 15, 2026.
Audit of the latest version
- fail: Frontmatter block present
- fail: Frontmatter declares a name
- fail: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6800 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
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
atnexuslab/tightship · 4 stars · license MIT · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kppa3ic2s3wfw2yt GET https://markdownregistry.com/api/v1/resolve?ref=atnexuslab/tightship/requirements-engineering GET https://markdownregistry.com/api/v1/blob/7bf1f2263a40c882be9bb7e2f39555f2b113608046ffa87cba396a5ecbc5b642
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.