writing-plans SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
writing-plans from khaledsaeed18/dotclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add khaledsaeed18/dotclaude/writing-plans@git:20260921.3a2f779Pins git:20260921.3a2f779 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- khaledsaeed18/dotclaude
- Path
skills/engineering/writing-plans/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260921.3a2f779, committed Sep 21, 2026
- First version recorded
- Jun 9, 2026
- Size
- 4,995 bytes
- Repository stars
- 5
- License
- MIT
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. …
Read the whole file at its exact version.
How to install
mdr add khaledsaeed18/dotclaude/writing-plans@sha256:787fd6c71ad1093eThe 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.
[](https://markdownregistry.com/a/art_rscjzcllmfirkexx)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Jun 9, 2026 and Sep 21, 2026, about one every 52 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.3a2f779 latest | 2026-09-21 | 3a2f779 | 4,995 B | A | view · diff |
| git:20260921.6c17ffd | 2026-09-21 | 6c17ffd | 4,713 B | A | view · diff |
| git:20260609.13bdd5a | 2026-06-09 | 13bdd5a | 4,743 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 (4995 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
khaledsaeed18/dotclaude · 5 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_rscjzcllmfirkexx 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.
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.
More from khaledsaeed18/dotclaude
Every file in khaledsaeed18/dotclaude