Writes a step-by-step implementation plan of bite-sized TDD tasks with exact file paths, interfaces, test code, and commits, from an approved spec. Use when a design or spec has been approved for a multi-step task and before touching any code.
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
# Writing Plans
## Overview
Write comprehensive implementation plans assuming the engineer has zero context for our codebase and questionable taste. Document everything they need to know: which files to touch for each task, code, testing, docs they might need to check, how to test it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits.
Assume they are a skilled developer, but know almost nothing about our toolset or problem domain. Assume they do not know good test design very well. In `opm:executing-plans`, each task's implementer sees ONLY its own task text plus the plan's interface and constraint blocks, so every task must stand on its own.
**Announce at start:** "Using opm:writing-plans to create the implementation plan."
**Save plans to:** `docs/plans/YYYY-MM-DD-<topic>.md` (user preferences for plan location override this default).
**Scope note:** for scope larger than roughly a week, or work with several distinct phases, use `opm:milestone-planning` instead and write one plan per milestone phase.
## Scope Check
…
The line at the top of this page pins the label git:20260912.a10a790, 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 (7231 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
harshadmadaye/opm · 5 stars · license MIT · pushed 2026-10-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rw5lplea6vavuuoo
GET https://markdownregistry.com/api/v1/resolve?ref=harshadmadaye/opm/writing-plans
GET https://markdownregistry.com/api/v1/blob/0c6fe49a8aede91c2f735d06d916aaea1679127758fb205c7aca9f58e3afdc8a
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.
harshadmadaye/opm · plugins/opm-video/skills/explainer-video/SKILL.md · Turns a spec or document into a narrated explainer video. Produces a 1920x1080 MP4 of illustrated still slides with a…
harshadmadaye/opm · skills/brainstorming/SKILL.md · Turns a rough idea into an approved design or written spec through one-question-at-a-time dialogue, scaled to spike…
harshadmadaye/opm · skills/brew-idea/SKILL.md · Runs a multi-agent debate over a project idea. Four angle agents (product, engineering, skeptic, market research)…
harshadmadaye/opm · skills/compound-learnings/SKILL.md · Captures a solved, non-obvious problem as a durable learning doc under docs/solutions/ with validated frontmatter, and…
harshadmadaye/opm · skills/executing-plans/SKILL.md · Executes a written implementation plan task-by-task by dispatching a fresh implementer subagent per task, a reviewer…
harshadmadaye/opm · skills/jump-start/SKILL.md · Creates an entire new project from one prompt. Takes a project name plus a brief, clarifies only what would change the…
harshadmadaye/opm · skills/milestone-planning/SKILL.md · Structures multi-week work as a milestone with a roadmap, a short always-read STATE digest, phased executable PLAN…
harshadmadaye/opm · skills/python-patterns/SKILL.md · Provides idiomatic modern Python (3.11+) patterns covering type hints, dataclasses and pydantic at boundaries, pathlib…
harshadmadaye/opm · skills/tdd-workflow/SKILL.md · Drives test-driven development through a strict RED-GREEN-REFACTOR cycle with test-runner detection, a "fails for the…
harshadmadaye/opm · skills/using-opm/SKILL.md · Establishes how to find and invoke OPM skills before taking any other action, including clarifying questions. Use when…
a5c-ai/babysitter · library/methodologies/superpowers/skills/writing-plans/SKILL.md · Use when you have a spec or requirements for a multi-step task, before touching code. Creates bite-sized TDD…
ganyuanran/aegis · skills/writing-plans/SKILL.md · Use when you have an approved spec or written requirements for a multi-step task that needs a durable plan document…
optima-cityu/llm4ad_next · docker/knowledge-parser/skills/writing-plans/SKILL.md · Use before a multi-step document restructuring task to map the source, preserve important relationships, and decide…
xu123-bob/baize · agent/skills/superpowers/5.1.0/skills/writing-plans/SKILL.md · Use when you have a spec or requirements for a multi-step task, before touching code
