plan-work-items SKILL.md skillA
plan-work-items from testdouble/han is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add testdouble/han/plan-work-items@git:20260908.1dc72b1Pins git:20260908.1dc72b1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- testdouble/han
- Path
han-planning/skills/plan-work-items/SKILL.md- Versions recorded
- 7
- Latest version
- git:20260908.1dc72b1, committed Sep 8, 2026
- First version recorded
- Jul 31, 2026
- Size
- 25,981 bytes
- Repository stars
- 338
- License
- MIT
Break a trusted implementation plan (or other provided context) into independently-grabbable, atomic work items, written to a single work-items.md file. Use when the user wants to convert a plan into work items, create implementation tickets or tasks, divide a plan into work units, or break the plan down into grabbable pieces. Do not use when there is no implementation plan yet or the plan is not yet trusted — use plan-implementation to produce the plan or iterative-plan-review to harden it…
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
## Project Context
- CLAUDE.md: !`find . -maxdepth 1 -name "CLAUDE.md" -type f`
- project-discovery.md: !`find . -maxdepth 3 -name "project-discovery.md" -type f`
- feature-implementation-plan.md: !`find . -maxdepth 5 -name "feature-implementation-plan.md" -type f`
- personal config directory: !`bash "${CLAUDE_PLUGIN_ROOT}/scripts/han-config-dir.sh" 2>/dev/null || echo "$HOME/.claude"`
- project .han/config.md: !`cat .han/config.md 2>/dev/null || echo ""`
As your first action, use the Read tool on `.han/config.md` inside the `personal config directory` path above. A read
that returns no file is no personal configuration: continue silently. When that file or the `project .han/config.md`
probe supplies content, apply it per [config-rule.md](../../references/config-rule.md), which governs precedence
between the two files, relative-path resolution, and what to do with a file that reads but cannot be used.
# Plan Work Items
Break an implementation plan into vertical slices (tracer bullets) and write them as work items to a single
`work-items.md` file.
This skill mostly coordinates: reading the boundary this work descends from, locating the plan or context, resolving
…Read the whole file at its exact version.
How to install
mdr add testdouble/han/plan-work-items@sha256:776e44a647f5ec03The line at the top of this page pins the label git:20260908.1dc72b1, 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_jrpaf4br4b3ccn5u)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jul 31, 2026 and Sep 8, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260908.1dc72b1 latest | 2026-09-08 | 1dc72b1 | 25,981 B | A | view · diff |
| git:20260908.a00b81f | 2026-09-08 | a00b81f | 25,949 B | A | view · diff |
| git:20260819.cdb751e | 2026-08-19 | cdb751e | 24,092 B | A | view · diff |
| git:20260818.55bdb1d | 2026-08-18 | 55bdb1d | 23,998 B | A | view · diff |
| git:20260803.1cda9cd | 2026-08-03 | 1cda9cd | 23,884 B | A | view · diff |
| git:20260731.e79299f | 2026-07-31 | e79299f | 23,881 B | A | view · diff |
| git:20260731.d95412f | 2026-07-31 | d95412f | 24,086 B | A | view |
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 (25981 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
testdouble/han · 338 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jrpaf4br4b3ccn5u GET https://markdownregistry.com/api/v1/resolve?ref=testdouble/han/plan-work-items GET https://markdownregistry.com/api/v1/blob/776e44a647f5ec032d7421bd2248cf7e5225344688b9e821cfa9b8cfc991a13f
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.