plan-update SKILL.md skillA
plan-update from yarlson/yarstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yarlson/yarstack/plan-update@git:20260911.d385958Pins git:20260911.d385958 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yarlson/yarstack
- Path
plugins/yarstack/skills/plan-update/SKILL.md- Versions recorded
- 4
- Latest version
- git:20260911.d385958, committed Sep 11, 2026
- First version recorded
- Jul 17, 2026
- Size
- 1,251 bytes
- Repository stars
- 3
- License
- MIT
Make the smallest evidence-backed correction to implementation-plan mechanics. Use when implementation or validation proves incorrect ordering, prerequisites, phase scope, dependencies, steps, or validation gates.
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
# Plan Update Correct an implementation plan without making product, architecture, or behavior decisions. ## Workflow 1. Identify the authoritative plan, exact mechanical defect, evidence, and affected phases. 2. Confirm that the correction is local. Use `plan-create` when multiple phases require broad replanning. 3. Use `spec-update` when the defect concerns product behavior, architecture semantics, a public contract, or acceptance meaning. 4. Stop for user direction when the correction materially expands authorized scope. 5. Apply the smallest correction in the plan's existing structure and style. 6. Verify affected dependencies, cross-references, acceptance criteria, and downstream phases remain consistent. Do not use plans as progress logs, add speculative roadmap work, rewrite unrelated phases, or disguise scope expansion as maintenance. Finish by reporting the defect, evidence, exact correction, affected phases, and whether implementation or validation can safely resume.
Read the whole file at its exact version.
How to install
mdr add yarlson/yarstack/plan-update@sha256:f46459ef15da1f87The line at the top of this page pins the label git:20260911.d385958, 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_wsufdwc6ux5vfmfs)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Jul 17, 2026 and Sep 11, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260911.d385958 latest | 2026-09-11 | d385958 | 1,251 B | A | view · diff |
| git:20260720.2e4f3b4 | 2026-07-20 | 2e4f3b4 | 1,677 B | A | view · diff |
| git:20260717.e1d5341 | 2026-07-17 | e1d5341 | 1,383 B | A | view · diff |
| git:20260717.dc9a72d | 2026-07-17 | dc9a72d | 1,260 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 (1251 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
yarlson/yarstack · 3 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wsufdwc6ux5vfmfs GET https://markdownregistry.com/api/v1/resolve?ref=yarlson/yarstack/plan-update GET https://markdownregistry.com/api/v1/blob/f46459ef15da1f87275e5f179f335f4875a66f8087e258c21ebbc721784b659b
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.