design SKILL.md skillA
design from dataart/artisyn-implementation-harness is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dataart/artisyn-implementation-harness/design@v6.0.0Pins v6.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dataart/artisyn-implementation-harness
- Path
.harness/evolve/20261102T140000Z-design-stage-tasks-first-action/candidate/SKILL.md- Versions recorded
- 1
- Latest version
- v6.0.0, committed Nov 2, 2026
- Size
- 19,239 bytes
- Repository stars
- 8
- License
- MIT
Full design lifecycle (/design {ticket}): Context Gathering → Ceremony → Frame → Research → Evaluate → Solution → Review Gate → Address Feedback → Publish → Completion, or a single stage via /design context-gathering|ceremony|frame|research|evaluate|solution|review-gate|address-feedback|publish|complete {ticket}. Trigger: "design ND-XX", "run the design for ND-XX".
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
The developer wants to run the design workflow for a ticket. Here is their input:
---
## $ARGUMENTS
---
> ⚠️ Follow every step in order. Do not skip, summarize, or improvise. If you are unsure, ask before deviating.
> 🗂 **Two-track design** — Product (`docs/Harness/`) or Project (`docs/Target Architecture (HLD)/`). Resolved once in Context Gathering Step 3 (`patterns/context-resolution.md`) and recorded in `design/Report.md`'s `## Context` section; every later phase reads it from there.
## How approvals work
A request to run the design lifecycle authorises everything routine: context
inspection, drafting, delegating to `{resolved architect agent}`/`@docs-writer`,
reversible local writes in scope, running non-guarded checks, updating the
report, moving between stages. That authorisation holds for the whole ticket.
Do not ask again per file, per finding, per step, or per phase.
The developer should feel like they are reviewing a senior colleague's work, not
approving every move of a junior one. So:
- **Two stops per phase, both at its end.** The sign-off
(`patterns/phase-sign-off.md`) and then the commit: proposed, run by the
…Read the whole file at its exact version.
How to install
mdr add dataart/artisyn-implementation-harness/design@sha256:96856fdb23de739fThe line at the top of this page pins the label v6.0.0, 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_d6qpy6eearvvafrr)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Nov 2, 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 (19239 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
dataart/artisyn-implementation-harness · 8 stars · license MIT · pushed 2026-11-09 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_d6qpy6eearvvafrr GET https://markdownregistry.com/api/v1/resolve?ref=dataart/artisyn-implementation-harness/design GET https://markdownregistry.com/api/v1/blob/96856fdb23de739fca8fe8d67c1fa12025e7c757b87d3ab9725c5ee5d3ce3649
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 dataart/artisyn-implementation-harness
Every file in dataart/artisyn-implementation-harness