plan is agent-read markdown (skill) from ronaknnathani/relay: Turn a clarified requirements artifact into a concrete, executable implementation plan — a decisive architecture blueprint and a phased build sequence with exact file paths. Use after requirements are pinned down (e.g. by `clarify`) and before writing code, whenever a multi-step change needs a design and a task breakdown. Its output feeds `implement`..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Plan
Given a clarified requirements artifact, produce an implementation plan concrete enough that someone
with no prior context could execute it. The bar: exact file paths and names, one committed
architecture decision, and a phased build sequence `implement` consumes step by step — no abstract
advice, no "add appropriate error handling". This is a peer phase: it grounds itself in the code via
`explore`, picks ONE approach and commits, then hands a plan to `implement`. It does **not** clarify
requirements (that's `clarify`, upstream) and does **not** write production code (that's `implement`,
downstream). It does not invoke either.
## Process
1. **Ground in the codebase first.** Read the clarified artifact (`clarify`'s requirements + success
criteria), then call `explore` (dispatch a sub-agent when available; otherwise inline) and consume
its **essential-files list and `file:line` citations** as the starting set for the existing
patterns, conventions, and integration points this work touches. Cite each finding as
`path/to/file.ext:line` — the blueprint
is built on what's actually there, not what you assume.
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
A 17 of 17 checks passed. Deterministic, no model, same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6109 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
GitHub
ronaknnathani/relay · 3 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ahzx47c6kx4ikrbx
GET https://markdownregistry.com/api/v1/resolve?ref=ronaknnathani/relay/plan
GET https://markdownregistry.com/api/v1/blob/4d5915923831acb890c2929926829e19bb2658c858aa04e97e53d0e9df41a9a4
Your agent 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.
ronaknnathani/relay · skills/build-write-like-me/SKILL.md · Use this skill whenever the user wants to capture, clone, or codify their own (or someone's) writing voice into a…
ronaknnathani/relay · skills/clarify/SKILL.md · Turn a vague or underspecified task into a crisp requirements + testable acceptance-criteria document by closing the…
ronaknnathani/relay · skills/commit/SKILL.md · Create a single well-formed git commit from the working changes, following the repo's AGENTS.md and recent…
ronaknnathani/relay · skills/deliver-pr/SKILL.md · Deliver one change end to end as a single pull request — clarify → plan → implement → simplify → review → validate →…
ronaknnathani/relay · skills/explore/SKILL.md · Build a verified, read-only understanding of a codebase or a slice of it — entry points, code flow, architecture…
ronaknnathani/relay · skills/implement/SKILL.md · Execute an implementation plan (from `plan`) task by task, writing the code and tests and leaving the system green at…
ronaknnathani/relay · skills/open-pr/SKILL.md · Stage, commit, push, and open a pull request following the author's repository and AGENTS.md conventions — repo-style…
ronaknnathani/relay · skills/pr-fix/SKILL.md · Bring a PR to mergeable — fix CI failures, address review comments, and resolve merge conflicts. Runs either from a…
ronaknnathani/relay · skills/pr-monitor/SKILL.md · Handle one pull request attention event end to end — read the watcher digest, triage it, delegate the fixing to pr-fix…
ronaknnathani/relay · skills/relay-archive/SKILL.md · Use when a project's PR is merged and you want to clean up the worktree while preserving notes and plans
jeremylongshore/tons-of-skills-marketplace · plugins/ai-agency/hyperflow/skills/plan/SKILL.md · Use when a request needs shaping before any code is written — a rough or vague prompt to sharpen, an ambiguous idea to…
suboss87/fdeops · skills/plan/SKILL.md · Sequence an understood outcome into verifiable delivery slices with dependencies, ownership and acceptance checks. Use…
dcouple/pane · .codex/skills/plan/SKILL.md · Create a detailed implementation plan for a feature or significant change, grounded in codebase research and external…
greenfield-inc/pane · .codex/skills/plan/SKILL.md · Creates a reconciled implementation plan by combining a structured plan draft with a normalized intent brief and a…
