writing-plans SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 6 indexed copies. Same content hash, so the same checks give both the same grade.
writing-plans from ddtcorex/maestro-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ddtcorex/maestro-skills/writing-plans@git:20260927.d32495aPins git:20260927.d32495a in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ddtcorex/maestro-skills
- Path
skills/writing-plans/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260927.d32495a, committed Sep 27, 2026
- First version recorded
- Aug 22, 2026
- Size
- 10,335 bytes
- Repository stars
- 5
- License
- MIT
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 implementation plans for an engineer who has not seen this codebase or this spec. Assume they write idiomatic code in the project's language once they know the exact interface and the exact test, and that they will make a reasonable choice wherever the plan leaves one open. What they cannot know is what you decided: which files, which names and signatures, which values from the spec, which tests prove each task. Document those. Give them the whole plan as bite-sized tasks. DRY. YAGNI. TDD. Frequent commits. **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 …
Read the whole file at its exact version.
How to install
mdr add ddtcorex/maestro-skills/writing-plans@sha256:a6c67c1900064347The line at the top of this page pins the label git:20260927.d32495a, 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_k5swvi7mwkows5p3)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 22, 2026 and Sep 27, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.d32495a latest | 2026-09-27 | d32495a | 10,335 B | A | view · diff |
| git:20260919.2c4bbac | 2026-09-19 | 2c4bbac | 9,092 B | A | view · diff |
| git:20260822.9d40859 | 2026-08-22 | 9d40859 | 7,053 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 (10335 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
ddtcorex/maestro-skills · 5 stars · license MIT · pushed 2026-10-27 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_k5swvi7mwkows5p3 GET https://markdownregistry.com/api/v1/resolve?ref=ddtcorex/maestro-skills/writing-plans GET https://markdownregistry.com/api/v1/blob/a6c67c1900064347c2a329990dd3c555657c51c3ec53b259a08aa01a2c26139a
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 ddtcorex/maestro-skills
Every file in ddtcorex/maestro-skills