write-phase-plan skillA
write-phase-plan is agent-read markdown (skill) from hraness/textbutler: 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..
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
# 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. ## 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, branch or worktree requirements, anything the orchestrator must not infer. ## Phases A short table or list: phase ID, name, depends-on, parallelizable-with. ## Phase 1: <name> - **Status:** Not started - **Depends on:** none | Phase N - **Objective:** one sentence, the outcome not the activity. …
Read the whole file at its exact version.
How to install
mdr add hraness/textbutler/write-phase-plan@git:20260829.ccbdf72mdr add hraness/textbutler/write-phase-plan@sha256:5fa9521d909c918fPin 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.
[](https://markdownregistry.com/a/art_5gzrfiwh7dem7bom)
1 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 (4767 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/textbutler · 4 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_5gzrfiwh7dem7bom GET https://markdownregistry.com/api/v1/resolve?ref=hraness/textbutler/write-phase-plan GET https://markdownregistry.com/api/v1/blob/5fa9521d909c918f3f78e9cfab487fef6ae71e0f68e6528f5a656eac34247bc0
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.
More from hraness/textbutler
Every file in hraness/textbutler