Turn a spec or set of requirements into a detailed, task-by-task implementation plan an engineer (or a subagent) can execute without further context. Breaks work into bite-sized steps with exact file paths, real code, and verification commands. Use before starting a multi-step build, once you know what you're building.
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
Write the implementation plan as if the engineer executing it has strong general skills but zero knowledge of this codebase, this domain, or your intentions. Everything they need to act has to be on the page: which files to touch, the actual code, how to test it, what "done" looks like for each step. Vagueness in a plan becomes wasted work or wrong work at execution time.
A good plan is a sequence of small, verifiable tasks: each one producing a self-contained change that makes sense on its own and leaves the project working.
## Step 1: Orient before planning
Read the spec or requirements fully, then look at the codebase the plan will touch, existing patterns, conventions, the files involved. Plan *with* the grain of the code that's there, not against an idealised version of it. If the spec spans several independent subsystems, say so and propose splitting it into one plan per subsystem; each plan should produce working, testable software on its own.
## Step 2: Map the files first
Before writing any task, list the files the work will create or modify and the single responsibility of each. This is where the decomposition gets decided.
…
The line at the top of this page pins the label git:20260921.3a2f779, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_iqiyeohysbtbm565
GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/writing-plans
GET https://markdownregistry.com/api/v1/blob/787fd6c71ad1093ea02399f1db4a8a7d2e941e4643338135adb2dacc05339996
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.
khaledsaeed18/dotclaude · .agents/skills/improve/SKILL.md · Survey any codebase as a senior advisor and produce prioritized, self-contained implementation plans for OTHER…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/coolify-image-app/SKILL.md · Create and configure a Coolify application that runs a prebuilt image from a registry. Use when adding an app to…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/coolify-vps-baseline/SKILL.md · Prepare a Linux VPS to run production containers under Coolify. Use when setting up a new server, auditing an existing…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/deploy-verification/SKILL.md · Prove a deployment from the server side. Use when a deploy finished and needs sign-off, when a rolling update may have…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/express-prisma-coolify-image/SKILL.md · Package an Express and Prisma API as a runtime-only image that migrates its Postgres database at start. Use when…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/ghcr-coolify-pipeline/SKILL.md · Write the single GitHub Actions workflow that takes a repository from pull request to production through GHCR and…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/live-domain-cutover/SKILL.md · Move a live domain from one host to another without downtime or lost sessions, with a rehearsal, a timed DNS switch, a…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/nextjs-coolify-image/SKILL.md · Package a Next.js app as a runtime-only container image with a health probe and a fast shutdown. Use when…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/proxy-client-address/SKILL.md · Forward the real client address from a server-side proxy to a backend without trusting forgeable headers. Use when an…
khaledsaeed18/dotclaude · .claude-plugin/plugins/deploy/skills/vps-ops-toolkit/SKILL.md · Install host operations on a VPS, with a cron health check that alerts on change, restore-verified encrypted database…
khaledsaeed18/dotclaude · .claude-plugin/plugins/docs/skills/adr-writing/SKILL.md · Write Architecture Decision Records that a future engineer can act on: a numbered, immutable record with the context…
khaledsaeed18/dotclaude · .claude-plugin/plugins/docs/skills/openapi-spec/SKILL.md · Write, generate, or review an OpenAPI 3.1 specification for an HTTP API so that it is accurate to the implementation…
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
