generating-tech-spec SKILL.md skillA
generating-tech-spec from qte77/claude-code-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add qte77/claude-code-plugins/generating-tech-spec@git:20260929.bb41808Pins git:20260929.bb41808 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- qte77/claude-code-plugins
- Path
plugins/docs-generator/skills/generating-tech-spec/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260929.bb41808, committed Sep 29, 2026
- First version recorded
- Mar 1, 2026
- Size
- 2,639 bytes
- Repository stars
- 3
- License
- Apache-2.0
Generates structured technical specifications including ADR (MADR), RFC, design documents, and proposals. Use when writing a spec, creating an ADR, drafting an RFC, or creating a design document.
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
# Technical Specification Generation **Target**: $ARGUMENTS Generate a structured technical specification document based on the requested type and topic. ## References (MUST READ) Read these before proceeding: - `references/tech-spec-formats.md` — ADR (MADR), RFC, design doc, and proposal templates ## Spec Types | Type | Trigger phrases | Output directory | |------|----------------|-----------------| | **ADR** | "adr", "architectural decision record" | `docs/adr/` | | **RFC** | "rfc", "request for comments" | `docs/rfc/` | | **Design Doc** | "design doc", "design document", "tech spec" | `docs/specs/` | | **Proposal** | "proposal", "technical proposal" | `docs/specs/` | ## Workflow 1. **Detect spec type** from arguments — default to Design Doc if ambiguous 2. **Read reference** for the matching template format 3. **Glob for existing specs** in the target directory to determine next sequence number: - ADR: `docs/adr/NNNN-*.md` (four-digit, e.g., `0001-use-postgres.md`) - RFC: `docs/rfc/NNNN-*.md` - Design Doc/Proposal: `docs/specs/<date>-<slug>.md` 4. **WebSearch** for relevant context if the topic references specific technologies …
Read the whole file at its exact version.
How to install
mdr add qte77/claude-code-plugins/generating-tech-spec@sha256:bce609e0ae60d061The line at the top of this page pins the label git:20260929.bb41808, 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_s5rhl7t6lrpnroab)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Mar 1, 2026 and Sep 29, 2026, about one every 71 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260929.bb41808 latest | 2026-09-29 | bb41808 | 2,639 B | A | view · diff |
| git:20260924.f8da1df | 2026-09-24 | f8da1df | 2,635 B | A | view · diff |
| git:20260322.75aadc6 | 2026-03-22 | 75aadc6 | 2,633 B | A | view · diff |
| git:20260301.2e7e6b3 | 2026-03-01 | 2e7e6b3 | 2,490 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 (2639 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
qte77/claude-code-plugins · 3 stars · license Apache-2.0 · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_s5rhl7t6lrpnroab GET https://markdownregistry.com/api/v1/resolve?ref=qte77/claude-code-plugins/generating-tech-spec GET https://markdownregistry.com/api/v1/blob/bce609e0ae60d061b26b54abbdb919f4922b82dd7cf7d2b98deb2ebef224c4db
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.