development-workflow SKILL.md skillA
development-workflow from will-ness-ai/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add will-ness-ai/skills/development-workflow@git:20261115.cba339bPins git:20261115.cba339b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- will-ness-ai/skills
- Path
skills/development-workflow/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261115.cba339b, committed Nov 15, 2026
- First version recorded
- Nov 6, 2026
- Size
- 6,893 bytes
- Repository stars
- 170
- License
- MIT
Take a task from idea to merged PR through my development workflow — research, alignment, proof, spec, tickets, implement, review, PR — run as a chain of tight loops.
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
This is the development workflow: how a task moves from an idea to a merged PR. It rests on one belief: **an agentic process is a chain of loops**. A **loop** is two segments and a repeat: _do_, _check_, go again. Keep every loop **tight**, with as few segments as possible, so its feedback is fast, its context is small, and it chases one goal. Each loop has **one job and one exit**. When its exit holds, hand off to the next loop and leave the finished loop's context behind. Every loop below names its job, its **check** (what tells you whether this pass worked), the context it loads, and its exit. Load only that loop's context. The check is where the quality comes from, so make it the strongest signal you can get: a tool, a test, a screenshot, a human, a fresh reviewer. ## Scale the chain to the task Run every loop, every time. A small task takes fewer passes through each loop; the shape of the chain stays fixed. A one-line fix still researches (where does it live?), aligns (one playback line), proves (the failing test goes green), specs and tickets itself (a one-ticket spec), and reviews. ## Route back to the owner …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_t6gxksvmodadr42u/20b27ebb124025a332b68910a868b7f51613a49f09e3ed6fc8ea5edf465edff9.json
Then /plugin install development-workflow@markdownregistry-t6gxksvmodadr42u in Claude Code. It installs git:20261115.cba339b, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add will-ness-ai/skills/development-workflow@sha256:20b27ebb124025a3The line at the top of this page pins the label git:20261115.cba339b, 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_t6gxksvmodadr42u)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in will-ness-ai/skills/development-workflow since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of development-workflow from somewhere else? Ask it: where did my development-workflow come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between Nov 6, 2026 and Nov 15, 2026, about one every 4 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261115.cba339b latest | 2026-11-15 | cba339b | 6,893 B | A | view · diff |
| git:20261115.d40d2e7 | 2026-11-15 | d40d2e7 | 7,033 B | A | view · diff |
| git:20261106.9ddd77f | 2026-11-06 | 9ddd77f | 6,346 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/development-workflow/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (6893 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
will-ness-ai/skills · 170 stars · license MIT · pushed 2026-11-15 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_t6gxksvmodadr42u GET https://markdownregistry.com/api/v1/resolve?ref=will-ness-ai/skills/development-workflow GET https://markdownregistry.com/api/v1/blob/20b27ebb124025a332b68910a868b7f51613a49f09e3ed6fc8ea5edf465edff9
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 will-ness-ai/skills
Every file in will-ness-ai/skills