spec-design SKILL.md skillA
spec-design from kamioj/spec-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kamioj/spec-workflow/spec-design@git:20260709.322dd02Pins git:20260709.322dd02 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kamioj/spec-workflow
- Path
codex/skills/spec-design/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260709.322dd02, committed Jul 9, 2026
- Size
- 2,606 bytes
- Repository stars
- 20
- License
- a license file GitHub does not identify
Technical design elaboration. Trigger on demand — use when the architecture is complex, there are more than 3 interfaces, sequence/data-flow diagrams are needed, or a decision requires more than 300 words of deep argumentation. Produces design.md.
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
<!-- GENERATED from core/commands/design.md — edit the core file and run node tools/generate.mjs; hand edits will be overwritten --> # $spec-design Focus: $ARGUMENTS ## When to use Trigger if any one of the following applies: - **Cross-cutting frontend + backend** (touching both UI and server side, including interface contracts) ← **in this scenario design is MANDATORY, not optional** - More than 3 interfaces - Architecture diagram / data-flow diagram / sequence diagram needed (mermaid / ASCII) - Deep decision argumentation exceeding 300 words (benchmarks / limit comparisons / performance models) - Cross-service / cross-process protocol design **Pure frontend or pure backend simple tasks**: go directly research → propose; do not open a design for the sake of opening one. **Why cross-cutting frontend + backend tasks MUST have a design**: - The interface contract is the **only coordination medium that lets frontend and backend implement in parallel** - No contract → frontend and backend must serialize (backend finishes first, frontend integrates after), wasting 50% of the time …
Read the whole file at its exact version.
How to install
mdr add kamioj/spec-workflow/spec-design@sha256:01e292f252f9469bThe line at the top of this page pins the label git:20260709.322dd02, 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_yq5mdpzgmwx447u2)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 9, 2026.
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 (2606 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
kamioj/spec-workflow · 20 stars · license a license file GitHub does not identify · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yq5mdpzgmwx447u2 GET https://markdownregistry.com/api/v1/resolve?ref=kamioj/spec-workflow/spec-design GET https://markdownregistry.com/api/v1/blob/01e292f252f9469b306a18379b9b54ff5294f2d10f13fb97e161b0133c7d1946
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 kamioj/spec-workflow
Every file in kamioj/spec-workflow