req-analyze SKILL.md skillA
req-analyze from sd0xdev/sd0x-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add sd0xdev/sd0x-harness/req-analyze@git:20260905.d98c025Pins git:20260905.d98c025 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- sd0xdev/sd0x-harness
- Path
skills/req-analyze/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260905.d98c025, committed Sep 5, 2026
- First version recorded
- Apr 3, 2026
- Size
- 16,471 bytes
- Repository stars
- 194
- License
- MIT
Requirements analysis — problem decomposition, stakeholder scan, requirement structuring. Produces 1-requirements.md (Phase 1 lifecycle doc, NOT the per-task request ticket — for those use /create-request). Use when: analyzing needs before tech spec, decomposing requirements, stakeholder analysis, 需求分析. Not for: solution comparison (use feasibility-study), tech design (use tech-spec), per-task tracking tickets (use create-request), issue root cause (use issue-analyze).
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
# Requirements Analysis Skill ## Trigger - Keywords: requirements analysis, analyze requirements, decompose requirements, stakeholder analysis, 需求分析, requirement decomposition, analyze needs ## When NOT to Use - Solution comparison / feasibility evaluation (use `/feasibility-study`) - Technical specification writing (use `/tech-spec`) - **Per-task tracking tickets** (use `/create-request` — requests are date-prefixed non-lifecycle docs for progress tracking, not feature-level requirements docs; see Relationship section below) - Issue root cause analysis (use `/issue-analyze`) - Architecture design (use `/architecture`) - Implementation (use `/feature-dev`) ## Boundary Contract `/req-analyze` is **problem-space only**: - Defines problems, analyzes stakeholders, decomposes requirements, prioritizes needs - Must NOT rank solutions, estimate implementation effort, or produce feasibility recommendations - Solution-space concerns discovered during analysis → log as Open Questions with suggestion to run `/feasibility-study` ## Relationship with `/create-request` …
Read the whole file at its exact version.
How to install
mdr add sd0xdev/sd0x-harness/req-analyze@sha256:38891738d6a195e0The line at the top of this page pins the label git:20260905.d98c025, 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_b7fe7bqkyg6qz5jc)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 3, 2026 and Sep 5, 2026, about one every 39 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260905.d98c025 latest | 2026-09-05 | d98c025 | 16,471 B | A | view · diff |
| git:20260905.1599675 | 2026-09-05 | 1599675 | 16,515 B | A | view · diff |
| git:20260811.d9a8bca | 2026-08-11 | d9a8bca | 15,486 B | A | view · diff |
| git:20260410.5418082 | 2026-04-10 | 5418082 | 14,157 B | A | view · diff |
| git:20260403.ba4191b | 2026-04-03 | ba4191b | 11,585 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 (16471 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
sd0xdev/sd0x-harness · 194 stars · license MIT · pushed 2026-10-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b7fe7bqkyg6qz5jc GET https://markdownregistry.com/api/v1/resolve?ref=sd0xdev/sd0x-harness/req-analyze GET https://markdownregistry.com/api/v1/blob/38891738d6a195e06b08a4856afc02b74565c628ba1e540521afe796d4ae99cf
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.