trd skillA
trd is agent-read markdown (skill) from ulises-jeremias/agent-toolkit: WHAT — Draft and review a Technical Requirements Document (TRD) using the template, typically.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# TRD — Technical Requirements (WHAT) **Template:** `references/default-template.md` — local reference, kept up to date with the standard structure. ## Default guardrails (before any final content) 1. Apply **`output-handshake`**: confirm **where** the final TRD will live and that a **human** will review. 2. Then follow the steps below. ## When to use - A **PRD is approved** (or the task is technical-only) and the team needs design-level agreement before build. - You need **API/data contracts**, component boundaries, and **test strategy** aligned to standards. - A client doc hub with PRD/TRD cross-links requires **matching** document structure. ## Instructions 1. **Open the TRD template** (`references/default-template.md`). Align sections: Scope, Architecture overview, Data model / API contracts, Technical decisions (link **ADRs** and spikes), Dependencies, Risks & constraints, Testing strategy, Implementation plan. 2. **Map from PRD:** user stories and AC from the PRD should appear as **addressed** in the TRD with clear technical response; if no PRD exists, state that explicitly and list assumptions. …
Read the whole file at its exact version.
How to install
mdr add ulises-jeremias/agent-toolkit/trd@git:20260831.856ee57mdr add ulises-jeremias/agent-toolkit/trd@sha256:0b8cafc07d701e3fPin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_xrer27htjrkxjlhs)
1 badge views in 30 days
Versions
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 (2897 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
ulises-jeremias/agent-toolkit · 18 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xrer27htjrkxjlhs GET https://markdownregistry.com/api/v1/resolve?ref=ulises-jeremias/agent-toolkit/trd GET https://markdownregistry.com/api/v1/blob/0b8cafc07d701e3f98e0967c8ee83800f7e9a0bb3fffc6b8c793727bdf582ffb
Your agent 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.