writing-plans SKILL.md skillA
writing-plans from yeaight7/agent-powerups is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yeaight7/agent-powerups/writing-plans@git:20260606.1a3461cPins git:20260606.1a3461c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yeaight7/agent-powerups
- Path
plugins/dev-vitals/skills/writing-plans/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260606.1a3461c, committed Jun 6, 2026
- First version recorded
- May 2, 2026
- Size
- 3,856 bytes
- Repository stars
- 8
- License
- Apache-2.0
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
## Purpose Turn a spec into a detailed, executable multi-step implementation plan. Prevents implementation drift and gives any engineer — or agent — enough detail to build without guessing. ## When to Use - Before implementing any multi-subsystem or non-trivial feature. - When a spec or requirements document exists and needs to become actionable tasks. - When the implementation requires coordinating multiple files or components. If the spec covers multiple independent subsystems, break it into separate plans — one per subsystem. Each plan should produce working, testable software on its own. ## Inputs - Spec or requirements document. - Access to the codebase (for file paths and existing patterns). ## Workflow 1. **Scope check** — Identify all affected subsystems. If multiple independent subsystems, suggest separate plans. 2. **Design file structure** — Before defining tasks, map which files will be created or modified and what each is responsible for. Units should have clear boundaries, focused responsibility, and well-defined interfaces. 3. **Write the plan header:** ```markdown # [Feature Name] Implementation Plan …
Read the whole file at its exact version.
How to install
mdr add yeaight7/agent-powerups/writing-plans@sha256:239e17a73a14f774The line at the top of this page pins the label git:20260606.1a3461c, 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_zcriki22kwveptpg)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 2, 2026 and Jun 6, 2026, about one every 35 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260606.1a3461c latest | 2026-06-06 | 1a3461c | 3,856 B | A | view · diff |
| git:20260502.a124a94 | 2026-05-02 | a124a94 | 3,857 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 (3856 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
yeaight7/agent-powerups · 8 stars · license Apache-2.0 · pushed 2026-09-27 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zcriki22kwveptpg GET https://markdownregistry.com/api/v1/resolve?ref=yeaight7/agent-powerups/writing-plans GET https://markdownregistry.com/api/v1/blob/239e17a73a14f7744f9c34a72c1c05f1651c7bc4bd91e26e127c249ca9dc34be
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 yeaight7/agent-powerups
Every file in yeaight7/agent-powerups