parallel-work SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
parallel-work from ddd-ts-kit/ddd-ts-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ddd-ts-kit/ddd-ts-kit/parallel-work@git:20261117.f80fbfdPins git:20261117.f80fbfd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ddd-ts-kit/ddd-ts-kit
- Path
plugin/skills/parallel-work/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261117.f80fbfd, committed Nov 17, 2026
- First version recorded
- Nov 12, 2026
- Size
- 23,305 bytes
- Repository stars
- 24
- License
- MIT
Use when the user wants several agents or developers to build at the same time, asks how to parallelise or share the work, or before launching more than one context-builder agent. One worker per bounded context, a git worktree each, contracts first.
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
# Work in parallel without collisions Contexts asked for: `$ARGUMENTS` You are the conductor: you own the trunk, the shared files and the merges. Workers own one bounded context each. Input: `docs/architecture/slices.md` (skill `ddd-ts-kit:plan-slices` orders it). Launch nothing before the owner approved the split. ## 1. Decide whether it pays Work cut by user story rather than by context is `/ddd-ts-kit:story`, run by the owner, one session and one terminal per story: it reuses the worktrees, the briefings and the merge rules below. This skill splits one plan between workers of different contexts. Parallel work pays when at least two contexts each have three or more ready slices and their contracts are settled. It does not when: there is one context; a boundary or a payload is still debated; the slices form one chain; the walking skeleton is not merged yet (build it alone first, it proves the stack for everyone). Workers: one per context, **two or three at a time**, four at most. Each has its own worktree, dependencies and test runs, and every merge is read by one conductor: past that, the merges become the bottleneck. Inside one context, two workers only on two different …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ehszpsonztyn2mu2/de2f2d4edad306e8ce2c63d3ae18025a16381017279dcc6e2069fb05cf4ab10d.json
Then /plugin install parallel-work@markdownregistry-ehszpsonztyn2mu2 in Claude Code. It installs git:20261117.f80fbfd, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add ddd-ts-kit/ddd-ts-kit/parallel-work@sha256:de2f2d4edad306e8The line at the top of this page pins the label git:20261117.f80fbfd, 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_ehszpsonztyn2mu2)
0 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 ddd-ts-kit/ddd-ts-kit/parallel-work 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 parallel-work from somewhere else? Ask it: where did my parallel-work 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 5 versions of this file, between Nov 12, 2026 and Nov 17, 2026, about one every day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261117.f80fbfd latest | 2026-11-17 | f80fbfd | 23,305 B | A | view · diff |
| git:20261116.b0e37d1 | 2026-11-16 | b0e37d1 | 22,861 B | A | view · diff |
| git:20261116.253b0f1 | 2026-11-16 | 253b0f1 | 22,696 B | A | view · diff |
| git:20261113.e118a05 | 2026-11-13 | e118a05 | 21,375 B | A | view · diff |
| git:20261112.1432f21 | 2026-11-12 | 1432f21 | 21,286 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/parallel-work/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 (23305 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
ddd-ts-kit/ddd-ts-kit · 24 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ehszpsonztyn2mu2 GET https://markdownregistry.com/api/v1/resolve?ref=ddd-ts-kit/ddd-ts-kit/parallel-work GET https://markdownregistry.com/api/v1/blob/de2f2d4edad306e8ce2c63d3ae18025a16381017279dcc6e2069fb05cf4ab10d
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 ddd-ts-kit/ddd-ts-kit
Every file in ddd-ts-kit/ddd-ts-kit