Use when you have a spec or requirements for a multi-step task, before touching 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 don't know good test design very well.
**Announce at start:** "I'm using the writing-plans skill to create the implementation plan."
**Context:** If working in an isolated worktree, it should have been created via the `superpowers:using-git-worktrees` skill at execution time.
**Save plans to:** `docs/superpowers/plans/YYYY-MM-DD-<feature-name>.md`
- (User preferences for plan location override this default)
## Scope Check
If the spec covers multiple independent subsystems, it should have been broken into sub-project specs during brainstorming. If it wasn't, suggest breaking this into separate plans — one per subsystem. Each plan should produce working, testable software on its own.
## File Structure
…
The line at the top of this page pins the label git:20260702.9dc0119, 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 (7092 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
jdanigo/hydraia · 8 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_phmc6hpw42bffpb7
GET https://markdownregistry.com/api/v1/resolve?ref=jdanigo/hydraia/writing-plans
GET https://markdownregistry.com/api/v1/blob/272e1af349f5062c28dc282b3e21b220d58d683a7314a10c455b7432ec91d845
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.
jdanigo/hydraia · codex/skills/hydraia/SKILL.md · Codex-native hydraia pipeline. Use when the user asks to build, add, implement, or change a feature, brings a…
jdanigo/hydraia · skills/adr/SKILL.md · Use when a design decision is made that is expensive to reverse, affects multiple components, or rejects a plausible…
jdanigo/hydraia · skills/agency-tier-ui/SKILL.md · Teaches the AI to design like a high-end agency. Defines the exact fonts, spacing, shadows, card structures, and…
jdanigo/hydraia · skills/api-design/SKILL.md · Use when designing or reviewing an API surface — REST, GraphQL, or gRPC. Contract-first methodology: the contract…
jdanigo/hydraia · skills/banner-design/SKILL.md · Design banners for social media, ads, website heroes, creative assets, and print. Multiple art direction options with…
jdanigo/hydraia · skills/brainstorming/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, or modifying…
jdanigo/hydraia · skills/caveman/SKILL.md · Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical…
jdanigo/hydraia · skills/db-optimization/SKILL.md · Use when the bottleneck is database-shaped — slow queries, lock timeouts, connection exhaustion, N+1 patterns, index…
jdanigo/hydraia · skills/design-to-code/SKILL.md · Elite render-to-code skill. The user brings a finished website design render (jpg/png); this skill distills it into…
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
