plan-deliver SKILL.md skillA
plan-deliver 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-deliver@git:20261019.2df68b2Pins git:20261019.2df68b2 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-deliver/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261019.2df68b2, committed Oct 19, 2026
- First version recorded
- Oct 17, 2026
- Size
- 9,899 bytes
- Repository stars
- 3
- License
- MIT
Autonomously deliver an approved implementation plan to a ready GitHub pull request. Use when the user supplies a plan in the conversation or a file and authorizes implementation, commits, pushes, PR state changes, CI remediation, and resolution of requested automated review feedback; use jira-issue-deliver when the contract is a Jira issue.
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 Delivery Own one approved plan from first read to a ready, green, reviewed pull request. Use the plan as the behavior contract, the repository as the implementation authority, and fresh evidence from the current remote PR head for completion. ## Establish authority and completion Confirm the plan source (the latest approved plan in the conversation or a named file), repository, base branch, requested review systems, and terminal condition. Proceed only when the request authorizes edits, commits, pushes, PR creation and ready-state changes, CI fixes, review replies, and thread resolution. This skill never merges, deploys, releases, or creates or changes a Jira issue. Finish only when current evidence proves that: - one PR implements every in-scope plan deliverable and acceptance criterion; - `code-review` ran on the final complete diff, and each verified finding is fixed or recorded with a reason; - the PR is open and ready for review, not a draft; - the remote PR head matches the validated commit; - every required check for that head passed or has a neutral result allowed by repository rules; - each requested automated reviewer completed its review of that head; …
Read the whole file at its exact version.
How to install
mdr add yarlson/yarstack/plan-deliver@sha256:127edd81706893cbThe line at the top of this page pins the label git:20261019.2df68b2, 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_2wb7eo27nwg32ubi)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 17, 2026 and Oct 19, 2026, about one every 2 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261019.2df68b2 latest | 2026-10-19 | 2df68b2 | 9,899 B | A | view · diff |
| git:20261017.4c49dea | 2026-10-17 | 4c49dea | 9,333 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 (9899 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_2wb7eo27nwg32ubi GET https://markdownregistry.com/api/v1/resolve?ref=yarlson/yarstack/plan-deliver GET https://markdownregistry.com/api/v1/blob/127edd81706893cbc6b1327b1c3c56b24c4a12e89ebd31b2c673203be85ba85c
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.