superpowers-writing-plans SKILL.md skillA
superpowers-writing-plans from evovexai/evoflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add evovexai/evoflow/superpowers-writing-plans@git:20260912.6c490fdPins git:20260912.6c490fd in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- evovexai/evoflow
- Path
skills/public/superpowers-writing-plans/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260912.6c490fd, committed Sep 12, 2026
- Size
- 6,142 bytes
- Repository stars
- 611
- License
- a license file GitHub does not identify
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/user/evoflow/runs/<run-id>/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. …
Read the whole file at its exact version.
How to install
mdr add evovexai/evoflow/superpowers-writing-plans@sha256:0641922a4e4ba6eeThe line at the top of this page pins the label git:20260912.6c490fd, 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_qnbrm7ooecvbvsk7)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 12, 2026.
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 (6142 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
evovexai/evoflow · 611 stars · license a license file GitHub does not identify · pushed 2026-11-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qnbrm7ooecvbvsk7 GET https://markdownregistry.com/api/v1/resolve?ref=evovexai/evoflow/superpowers-writing-plans GET https://markdownregistry.com/api/v1/blob/0641922a4e4ba6eeab12511f9fb4b0fb045bee0ab6c3c32a5ffb474fc7367fc5
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.