write-phase-plan SKILL.md skillA
write-phase-plan from hraness/wrench is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hraness/wrench/write-phase-plan@git:20260829.3a8221dPins git:20260829.3a8221d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hraness/wrench
- Path
.agents/skills/write-phase-plan/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260829.3a8221d, committed Aug 29, 2026
- Size
- 5,548 bytes
- Repository stars
- 8
- License
- MIT
Writes or restructures an implementation plan in the format the phase-orchestrator skill consumes: dependency-ordered phases with explicit scope, acceptance criteria, validation commands, and status/log conventions. Use when the user asks to write a plan for phase orchestration, prepare a plan or PRD for delegated multi-agent implementation, or convert a spec, checklist, or design doc into implementable phases.
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
# Write Phase Plan ## Goal Produce a plan document that a phase-orchestrator run can execute without re-deriving structure. Each phase must be implementable by a worker that has no chat history: the phase section is the worker's entire brief, plus repo rules and the code itself. The plan is the source of truth during the run. The orchestrator updates phase status and appends log entries as it goes, so the document must be written to absorb that. When restructuring an existing plan, preserve completed work, current phase statuses, and implementation-log evidence unless the user explicitly asks to reset them. Normalize the remaining work around that history instead of rewriting the plan as a fresh run. ## Where The Plan Lives Follow the repo's convention for design docs (for example `plans/<author>/` in repos that define one). One markdown file per plan. Link out to the PRD/spec rather than duplicating it. ## Document Structure ```markdown # <Feature name> ## Overview One or two paragraphs: what is being built and why. Link the PRD/spec. ## Constraints Repo-wide facts every phase needs: commit/PR policy, validation commands, …
Read the whole file at its exact version.
How to install
mdr add hraness/wrench/write-phase-plan@sha256:878599ec966a17c4The line at the top of this page pins the label git:20260829.3a8221d, 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_w6bvfyskcrkrlufq)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 29, 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 (5548 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
hraness/wrench · 8 stars · license MIT · pushed 2026-10-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_w6bvfyskcrkrlufq GET https://markdownregistry.com/api/v1/resolve?ref=hraness/wrench/write-phase-plan GET https://markdownregistry.com/api/v1/blob/878599ec966a17c4deaaf36ed0f9ce07dc391490489b847b43c86e9f226611c7
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.