Create a concrete plan before starting a multi-file refactor. Use when the user asks to plan, sequence, scope, or safely execute a refactor across multiple files; always investigate first, output the plan, and wait for confirmation before making code changes.
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
# Refactor Plan
Create a detailed plan before making any code changes.
## Instructions
1. Do not edit files while preparing the plan.
2. Search the codebase to understand the current state. Read enough implementation, tests, configuration, and docs to make the plan specific to the repository.
3. Identify affected files, ownership boundaries, dependencies, and likely hidden coupling.
4. Plan changes in a safe sequence. Prefer contracts and types first, then implementations, then callers, then tests, then cleanup.
5. Include verification steps between phases and a final validation command.
6. Include rollback or recovery steps for the riskiest phases.
7. Output the complete plan using the format below.
8. Stop after the plan and ask for confirmation before implementing. If the user already asked you to implement, still produce the plan first and wait for confirmation unless they explicitly said to continue without review after the plan.
If the request is too ambiguous to plan safely, ask concise clarifying questions instead of editing files.
## Output Format
```markdown
## Refactor Plan: [title]
### Current State
[Brief description of how things work now]
### Target State
…
The line at the top of this page pins the label git:20260828.866dec6, 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.
A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (2289 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
GitHub
okhp3/skillz · 3 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_khq7hjajfm6ltqxf
GET https://markdownregistry.com/api/v1/resolve?ref=okhp3/skillz/refactor-plan
GET https://markdownregistry.com/api/v1/blob/93741df0042a15c01ae8589e72014dcf53c557c11ca1df69c29737534c312c29
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.
okhp3/skillz · .agents/skills/architecture-decision-records/SKILL.md · Write and maintain Architecture Decision Records (ADRs) following best practices for technical decision documentation…
okhp3/skillz · .agents/skills/frontend-design/SKILL.md · Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to…
okhp3/skillz · .agents/skills/okhp3-artifact-validation/SKILL.md · Validate a project change, draft, research packet, skill, promotion package, or handoff before it is treated as…
okhp3/skillz · .agents/skills/okhp3-as-is-process-capture/SKILL.md · Capture and normalise a current-state process description into a structured as-is process YAML with stable step…
okhp3/skillz · .agents/skills/okhp3-brand-style-registry/SKILL.md · OverKill Hill P³ visual style registry and application workflow. Use when a user wants to extract a reusable brand…
okhp3/skillz · .agents/skills/okhp3-capture-intake/SKILL.md · Preserve one raw idea, file, link, transcript, or request in a project inbox with provenance and minimal handling. Use…
okhp3/skillz · .agents/skills/okhp3-custom-gpt-builder/SKILL.md · Build, audit, and improve OpenAI Custom GPTs with production-grade methodology. Use this skill when the user asks to…
okhp3/skillz · .agents/skills/okhp3-custom-gpt-readiness/SKILL.md · Assess an incomplete or newly proposed Custom GPT concept for build readiness. Use when a user has a GPT idea, partial…
okhp3/skillz · .agents/skills/okhp3-decision-model-authoring/SKILL.md · Author and validate decision models from PNS decision points using DMN-aligned rule tables. Use this skill when the PNS…
okhp3/skillz · .agents/skills/okhp3-elicitation-interviews/SKILL.md · Plan and facilitate structured elicitation sessions using BABOK v3 interview and workshop techniques. Use this skill…
archubbuck/workspace-architect · assets/plugins/context-engineering/skills/refactor-plan/SKILL.md · Plan a multi-file refactor with proper sequencing and rollback steps
aboudjem/ui-ux-suite · skills/refactor-plan/SKILL.md · Prioritized redesign action plan covering quick wins, medium effort, and major rework. Use when the user asks for a…
gangjaeyu/harness_loop_full_korean · skills/refactor-plan/SKILL.md · 동작을 보존하는 코드 정리·의존성 갱신·스택 전환의 범위와 검증을 계획한다. 영향 문서와 필요한 작업만 보완하고 실행 요청이면 구현·검증까지 이어 수행한다.
vivantel/kms · plugins/kms/skills/refactor-plan/SKILL.md · Produces a safe, phased refactoring plan that respects existing decisions and guardrails, without writing anything. Use…
