plan-wave SKILL.md skillA
plan-wave from andrewbrown-usda/aigb-skills-usda is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add andrewbrown-usda/aigb-skills-usda/plan-wave@v1.2Pins v1.2 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- andrewbrown-usda/aigb-skills-usda
- Path
skills/plan-wave/SKILL.md- Versions recorded
- 8
- Latest version
- v1.2, committed Oct 14, 2026
- First version recorded
- Sep 25, 2026
- Size
- 7,391 bytes
- Repository stars
- 7
- License
- a license file GitHub does not identify
Develops an implementation plan ready for wave-orchestration to execute. Takes the user's goal or rough plan as input, mines the codebase for facts, grills the user one question at a time for the decisions, drafts the planning/ artifacts (task DAG, wave table, worker prompt template, state file), then reviews its own plan on two axes before seeking approval. Use when the user wants to turn a feature idea, master plan, or backlog into a wave-orchestration execution 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
# Plan-Wave: author the plan that wave-orchestration executes Produces the `planning/` artifact set that the **wave-orchestration** skill consumes: `EXECUTION_PLAN_N.md` (task directed acyclic graph + wave table + per-task specs), `PROMPT_TEMPLATE_N.md` (worker prompt), and `STATE_N.md` (scaffold). The output contract -- task-spec fields, right-sizing rules, wave rules -- is defined by wave-orchestration; read that skill first and treat it as the spec this plan must conform to. Here, `N` is the next available orchestration number. For example, orchestration plan 3 uses `EXECUTION_PLAN_3.md`, `PROMPT_TEMPLATE_3.md`, and `STATE_3.md`. Division of labor with the user, borrowed from **grilling**: *facts* come from the codebase -- look them up, never ask. *Decisions* belong to the user -- put each one to them and wait. Nothing is executed here; this skill ends at an approved plan. ## Phase 1 -- Intake (embed the user's input) The user's input -- a goal sentence, a master-plan document, a TODO backlog, scattered notes, links -- is the seed. Read every referenced document in full. Then restate it as a structured **Goal & Scope** block that will head EXECUTION_PLAN_N.md: …
Read the whole file at its exact version.
How to install
mdr add andrewbrown-usda/aigb-skills-usda/plan-wave@sha256:7a0d57c5f886c955The line at the top of this page pins the label v1.2, 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_bjaker64bzpm5oh6)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 8 versions of this file, between Sep 25, 2026 and Oct 14, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.2 latest | 2026-10-14 | 2620635 | 7,391 B | A | view · diff |
| v1.2 | 2026-10-14 | 677be34 | 7,465 B | A | view · diff |
| v1.1 | 2026-10-09 | 0d32dbb | 6,991 B | A | view · diff |
| v1.1 | 2026-10-02 | 511c0e3 | 6,991 B | A | view · diff |
| v1.1 | 2026-10-02 | 8c813e9 | 6,968 B | A | view · diff |
| v1.1 | 2026-10-02 | 3df38ef | 7,112 B | A | view · diff |
| v1 | 2026-09-30 | b8f4ba9 | 6,937 B | A | view · diff |
| v1 | 2026-09-25 | 160ae7c | 6,735 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 (7391 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
andrewbrown-usda/aigb-skills-usda · 7 stars · license a license file GitHub does not identify · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bjaker64bzpm5oh6 GET https://markdownregistry.com/api/v1/resolve?ref=andrewbrown-usda/aigb-skills-usda/plan-wave GET https://markdownregistry.com/api/v1/blob/7a0d57c5f886c955d0262f5d966d4b966d854e464af3168484bc3a986d9952dc
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.