design-and-plan SKILL.md skillA
design-and-plan from lawzava/megapowers is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add lawzava/megapowers/design-and-plan@git:20261021.ffb3826Pins git:20261021.ffb3826 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- lawzava/megapowers
- Path
plugins/megapowers/skills/design-and-plan/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261021.ffb3826, committed Oct 21, 2026
- First version recorded
- Oct 9, 2026
- Size
- 3,628 bytes
- Repository stars
- 8
- License
- MIT
Use to specify non-trivial behavior or interfaces, resolve requirements or tradeoffs, or produce a multi-step implementation plan. Do not use for a mechanical edit, routine status update, or execution of a settled plan.
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
# Design and Plan ## Understand the system Read repository instructions and relevant code. Establish entry points, callers, blast radius, the nearest convention-setting sibling, test coverage, and any unread area that could change the decision. Name the one fact that makes the change safe, and check where search stops: wire formats, stored data, and flags. Before custom design, check existing code, the standard library, platform features, and installed dependencies. Defer speculative needs while preserving requirements, conventions, and acceptance criteria. Resolve factual prerequisites, with a throwaway probe instead of a question to the user when one can settle them, before preference or policy questions. Present competing sketches only for a high-impact, underconstrained, or hard-to-reverse design, and screen them against [design red flags](references/design-red-flags.md). Recommend one and state its tradeoff. Mark assumptions and blockers. Model a domain term when repeated state branches or synchronized booleans obscure one concept. Propose an ADR only for a decision that is hard to reverse, surprising without context, and a real tradeoff. ## Specify observable behavior …
Read the whole file at its exact version.
How to install
mdr add lawzava/megapowers/design-and-plan@sha256:faf10c965513ac2cThe line at the top of this page pins the label git:20261021.ffb3826, 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_jibxapmlvowp32fm)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Oct 9, 2026 and Oct 21, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261021.ffb3826 latest | 2026-10-21 | ffb3826 | 3,628 B | A | view · diff |
| git:20261020.a845365 | 2026-10-20 | a845365 | 3,643 B | A | view · diff |
| git:20261016.8bb6759 | 2026-10-16 | 8bb6759 | 3,662 B | A | view · diff |
| git:20261014.d8b5030 | 2026-10-14 | d8b5030 | 3,628 B | A | view · diff |
| git:20261009.c4c8941 | 2026-10-09 | c4c8941 | 3,446 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 (3628 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
lawzava/megapowers · 8 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jibxapmlvowp32fm GET https://markdownregistry.com/api/v1/resolve?ref=lawzava/megapowers/design-and-plan GET https://markdownregistry.com/api/v1/blob/faf10c965513ac2ca6958f4d20de7203b4a3e56be46d167f5cc57f809bd5b308
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.