phase-orchestrator skillA
phase-orchestrator is agent-read markdown (skill) from hraness/textbutler: Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and phase-final-reviewer skills and consumes plans in the write-phase-plan format. Use when the user provides a plan, checklist, PRD, or phase document and asks for delegated multi-agent execution across 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
# Phase Orchestrator ## Goal Run a phase-based plan through a repeatable delegated workflow. The plan is the source of truth, any PRD/spec is supporting context, and each phase should move through orientation, implementation, validation, review, plan updates, and commits by default. Use this skill only when the user explicitly asks for delegated phase orchestration, invokes this skill, or asks to implement a plan/checklist using subagents. ## Companion Skills This skill is the parent of a five-skill workflow: - `write-phase-plan` — authors plans in the format this skill consumes best. - `phase-implementer` — the delegated worker contract for implementing exactly one phase (Phase Loop step 2). - `phase-reviewer` — the delegated worker contract for the review-and-fix pass on a completed phase (Phase Loop step 4). - `phase-final-reviewer` — the delegated worker contract for the end-to-end review of the whole feature after all phases (Final Whole-Feature Pass). Each worker skill carries that role's standing rules: single-phase or single-pass scope, no-revert discipline, no-commit default, and the required …
Read the whole file at its exact version.
How to install
mdr add hraness/textbutler/phase-orchestrator@git:20260829.ccbdf72mdr add hraness/textbutler/phase-orchestrator@sha256:b6703f1876137272Pin 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_ln4r5rjv4ew4v5f5)
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 (22388 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_ln4r5rjv4ew4v5f5 GET https://markdownregistry.com/api/v1/resolve?ref=hraness/textbutler/phase-orchestrator GET https://markdownregistry.com/api/v1/blob/b6703f1876137272945c43d42e3204b1bfd19e506997242cbfe3daa7e241cefd
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