system-design SKILL.md skillA

system-design from atman-33/workhub is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add atman-33/workhub/system-design@git:20260929.4a49767

Pins git:20260929.4a49767 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: atman-33/workhub
Path: plugins/engineering/skills/system-design/SKILL.md
Versions recorded: 2
Latest version: git:20260929.4a49767, committed Sep 29, 2026
First version recorded: Sep 19, 2026
Size: 6,526 bytes
Repository stars: 3
License: MIT

Design a change or feature with the user and write the design set — proposal, per-capability specs, design (with open questions) and UML diagrams (use case, ER, sequence, file change map) — into a folder they choose. Settles the design first by interviewing the user one round at a time. Use when the user wants to design a system, feature or change before building it, asks for a design doc / spec / proposal, or wants requirements turned into design documents.

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

# System design

Turn a request into a settled design and a set of design documents a human can
review and an agent can implement from. Two phases, in order: **settle the
design with the user**, then **write it down**. Writing is not a substitute for
asking — a document built on guesses reads as settled and is not.

**Planning boundary.** This skill produces documents only. Do not edit
application code, even if the request says "build it". After the documents are
written, stop and wait for a new request to implement.

## Outputs

All files go flat into the output folder — no subfolders, so the set also fits
a workhub backlog item folder:

| File | Holds | Template |
|---|---|---|
| `proposal.md` | Why, what changes, capabilities, impact | `templates/proposal.md` |
| `spec-<capability>.md` | One per capability: requirements with WHEN/THEN scenarios | `templates/spec.md` |
| `design.md` | How: context, goals/non-goals, decisions with alternatives, risks, open questions | `templates/design.md` |
| `uml.md` | Diagrams in Mermaid: use case, ER, sequence, file change map | `templates/uml.md` |

There is deliberately no task list: breaking the work into tasks belongs to
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add atman-33/workhub/system-design@sha256:4d3b08460d855048

The line at the top of this page pins the label git:20260929.4a49767, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_zmbovab3j2vmuql5.svg)](https://markdownregistry.com/a/art_zmbovab3j2vmuql5)

2 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 2 versions of this file, between Sep 19, 2026 and Sep 29, 2026, about one every 10 days.

version	committed	commit	size	audit
git:20260929.4a49767 latest	2026-09-29	4a49767	6,526 B	A	view · diff
git:20260919.90c42cb	2026-09-19	90c42cb	6,527 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6526 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

GitHub

atman-33/workhub · 3 stars · license MIT · pushed 2026-10-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_zmbovab3j2vmuql5
GET https://markdownregistry.com/api/v1/resolve?ref=atman-33/workhub/system-design
GET https://markdownregistry.com/api/v1/blob/4d3b08460d855048cb82fb9ca4c7bb2609f470b3155ab3a435b9774b1e9309a1

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.

More from atman-33/workhub

CLAUDE.md CLAUDE.md file

atman-33/workhub · CLAUDE.md

git:20260929.5a11e52 · audit A · 3 stars

AGENTS.md@demo-vault AGENTS.md file

atman-33/workhub · demo-vault/AGENTS.md

git:20260830.27fbb5d · audit A · 3 stars

CLAUDE.md@demo-vault CLAUDE.md file

atman-33/workhub · demo-vault/CLAUDE.md

git:20260930.4c9347d · audit A · 3 stars

handoff-go SKILL.md skill

atman-33/workhub · plugins/agent-ops/skills/handoff-go/SKILL.md · Write a handoff document and launch the next agent in a split multiplexer pane (herdr or zellij), with new-window and…