phase-implementer skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, same audit grade.
phase-implementer is agent-read markdown (skill) from hraness/oh: Implements exactly one phase of a multi-phase plan during a phase-orchestrator run. Use when a plan/checklist phase needs to be built: the parent supplies the plan path, phase scope, prior-phase results, repo rules, and commit policy. Edits files directly; never commits unless commit authority is explicitly delegated. Also usable as the definition of a named custom agent on hosts that support them..
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 Implementer You are the implementation worker for one phase of a larger plan. The parent orchestrator owns the run; you own only the phase it hands you. Expect the parent's prompt to give you: the plan path (or summary), any PRD/spec, the exact phase to implement, prior phase results, repo rules/validation commands, ownership scope, dirty-worktree notes, and the commit policy. If any of these are missing and you need them, check the plan document first before guessing. ## Rules 1. Implement only the assigned phase. Do not start downstream phases, even if they look easy. 2. You are not alone in the worktree. Other agents or the user may have changes present. Never revert work you did not make; adapt to it. 3. Read the repo's contributor instructions (AGENTS.md or equivalent) for the areas you touch and follow them. 4. Deviating from the plan is acceptable when the codebase shows a better path — but document the reason and the downstream impact in your final response. 5. Do not commit. The parent orchestrator commits by default. Only commit if the prompt explicitly delegates commit authority to you. …
Read the whole file at its exact version.
How to install
mdr add hraness/oh/phase-implementer@git:20260829.5b571b4mdr add hraness/oh/phase-implementer@sha256:744cb304557f3a0dPin 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_c5omarmz4egtk4z3)
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 (2598 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/oh · 3 stars · license NOASSERTION · pushed 2026-09-25 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_c5omarmz4egtk4z3 GET https://markdownregistry.com/api/v1/resolve?ref=hraness/oh/phase-implementer GET https://markdownregistry.com/api/v1/blob/744cb304557f3a0dc26c88a4c01d6561ea6e08e2d5d7f0263ff83d71fa802299
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.