writing-implementation-plans SKILL.md skillA
writing-implementation-plans from ed3dai/ed3d-plugins is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ed3dai/ed3d-plugins/writing-implementation-plans@git:20260616.eb1d79cPins git:20260616.eb1d79c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ed3dai/ed3d-plugins
- Path
plugins/ed3d-plan-and-execute/skills/writing-implementation-plans/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260616.eb1d79c, committed Jun 16, 2026
- First version recorded
- Feb 3, 2026
- Size
- 44,055 bytes
- Repository stars
- 253
- License
- none declared
Use when design is complete and you need detailed implementation tasks for engineers with zero codebase context - creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps assuming engineer has minimal domain knowledge.
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 Implementation 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 verify it. Give them the whole plan as bite-sized tasks. DRY. YAGNI. 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-implementation-plans skill to create the implementation plan." **Save plans to:** `docs/implementation-plans/YYYY-MM-DD-<feature-name>/phase_##.md` ## Critical: Design Plans Provide Direction, Not Code **Design plans are intentionally high-level.** They describe components, modules, and contracts — not implementation code. This is by design. **You MUST generate code fresh based on codebase investigation.** Do NOT copy code from the design document. Even if a design plan contains code examples (it shouldn't, but some might), treat them as illustrative only. **Why this matters:** …
Read the whole file at its exact version.
How to install
mdr add ed3dai/ed3d-plugins/writing-implementation-plans@sha256:6408f52acde50461The line at the top of this page pins the label git:20260616.eb1d79c, 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.
[](https://markdownregistry.com/a/art_eyqn6dg6k45extas)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Feb 3, 2026 and Jun 16, 2026, about one every 33 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260616.eb1d79c latest | 2026-06-16 | eb1d79c | 44,055 B | A | view · diff |
| git:20260217.ba8431d | 2026-02-17 | ba8431d | 43,600 B | A | view · diff |
| git:20260204.bd4341f | 2026-02-04 | bd4341f | 42,683 B | A | view · diff |
| git:20260204.611bfd1 | 2026-02-04 | 611bfd1 | 42,511 B | A | view · diff |
| git:20260203.17c9908 | 2026-02-03 | 17c9908 | 42,489 B | A | view |
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 (44055 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
ed3dai/ed3d-plugins · 253 stars · license none declared · pushed 2026-09-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eyqn6dg6k45extas GET https://markdownregistry.com/api/v1/resolve?ref=ed3dai/ed3d-plugins/writing-implementation-plans GET https://markdownregistry.com/api/v1/blob/6408f52acde504617ef681e4325971969ee0168dffa6b71e07433d2507b5685b
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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.