write-plan skillA
write-plan is agent-read markdown (skill) from teambrilliant/dev-skills: Write a technical implementation plan to thoughts/plans/ before coding starts (separate from the harness's plan mode). Use when someone says "create a plan", "plan this", "plan this ticket", "how should we implement this", "technical design", "architect this", "plan the migration", "refactor plan", or when a shape or groomed ticket needs phases, layers, and agent-runnable checks..
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 before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Write Plan Turn a shape, ticket, or technical challenge into a plan that any developer or agent can execute with `/dev-skills:execute-plan` — and that a human can read, understand, and defend. ## Workflow Every plan follows the same arc: **research → validate → write → present**. 1. **Research** the codebase until grounded — never plan from assumptions (see Process). 2. **Write** the plan to `thoughts/plans/YYYY-MM-DD-descriptive-name.md`, using today's date from context. 3. **Present** it for approval, closing with the ★ Plan View block. This skill is independent of any harness plan mode — always write the `thoughts/plans/` file. The gate is the user's approval of that file. Approval hands `execute-plan` a contract: it runs every phase to DONE or stops BLOCKED, without check-ins — so the plan must contain everything needed to get there unattended. ## Design Philosophy Before writing plans, read [references/software-design-philosophy.md](references/software-design-philosophy.md). Apply it to module boundaries, interfaces, and decomposition. Key checks: deep modules, information hiding, define errors out of existence, design it twice. ## Rollout & Rollback …
Read the whole file at its exact version.
How to install
mdr add teambrilliant/dev-skills/write-plan@git:20260927.b9558d0mdr add teambrilliant/dev-skills/write-plan@sha256:009dd4fee16a0011Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
[](https://markdownregistry.com/a/art_e2rfkn2n7phzut7f)
0 badge views in 30 days
Versions
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 (17164 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
teambrilliant/dev-skills · 6 stars · license none · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e2rfkn2n7phzut7f GET https://markdownregistry.com/api/v1/resolve?ref=teambrilliant/dev-skills/write-plan GET https://markdownregistry.com/api/v1/blob/009dd4fee16a00111d56195891b8757b5a3cd010a90167a8e5b9320c899cafb6
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.