iterate-plan 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.
iterate-plan from yonatangross/orchestkit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yonatangross/orchestkit/iterate-plan@v1.0.0Pins v1.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yonatangross/orchestkit
- Path
src/skills/iterate-plan/SKILL.md- Versions recorded
- 1
- Latest version
- v1.0.0, committed Oct 26, 2026
- Size
- 2,721 bytes
- Repository stars
- 299
- License
- MIT
Revises a plan written by create-plan from its review comments or new instructions: rewrites the plan body, leaves each comment intact and bumps the revision. Use when a plan file got feedback or its scope changed; never to start a new plan.
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
# iterate-plan
Revise one plan file. The body is rewritten; the comment block is kept byte for byte, because the
review record must outlive every revision. Layout: the create-plan skill's
`references/artifact-layout.md`.
## Steps
1. **Read the plan in full**, then the rest of its task directory in NN order (research, earlier
plans). List the open comments:
```bash
node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" list --file <plan> --open
```
2. **Check each comment against the code before acting on it.** Open the files it names. A comment
can be wrong; if so, say so in a reply instead of changing the plan.
3. **Write the revised body** to a scratch file: start from the current body (everything between the
front matter and `<!-- ork:comments -->`), apply the changes, keep the phase structure. Do not
copy the comment block into it; the script refuses a body that carries one.
4. **Write it back through the script**, which bumps `revision`, refreshes `sha` and `updated`, and
keeps the comments:
```bash
node "${CLAUDE_SKILL_DIR}/scripts/artifact.mjs" iterate --file <plan> --body /tmp/plan-body.md
# prints <plan> revision N
```
…Read the whole file at its exact version.
How to install
mdr add yonatangross/orchestkit/iterate-plan@sha256:9bfc184174f88daeThe line at the top of this page pins the label v1.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_rxdvz4q4yyuutcks)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 26, 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 (2721 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
yonatangross/orchestkit · 299 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rxdvz4q4yyuutcks GET https://markdownregistry.com/api/v1/resolve?ref=yonatangross/orchestkit/iterate-plan GET https://markdownregistry.com/api/v1/blob/9bfc184174f88dae4d9d93cce4490b3f335274e704ade9a0e7b5e17678ce2ccb
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 yonatangross/orchestkit
Every file in yonatangross/orchestkit