plan SKILL.md skillA
plan from greglas75/zuvo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add greglas75/zuvo/plan@git:20261011.64038cePins git:20261011.64038ce in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- greglas75/zuvo
- Path
skills/plan/SKILL.md- Versions recorded
- 10
- Latest version
- git:20261011.64038ce, committed Oct 11, 2026
- First version recorded
- Aug 10, 2026
- Size
- 48,082 bytes
- Repository stars
- 7
- License
- MIT
Analyzes architecture, selects patterns, assesses testability, then decomposes work into ordered TDD tasks with exact verification commands and explicit acceptance mapping. Works from an approved spec (zuvo:brainstorm output) or directly from a user-provided description.
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
# zuvo:plan
Create a detailed, task-by-task implementation plan. Every task follows the TDD protocol: RED (failing test) -> GREEN (minimal code) -> Verify -> Commit.
---
## Input Resolution
Determine the planning input. Two modes: **spec-driven** (from brainstorm output) or **inline** (from user description).
### Step 1: Look for a spec
1. If the user provided an explicit path (e.g., `zuvo:plan docs/specs/my-spec.md`), use that file
2. Otherwise, search: `Glob("docs/specs/*-spec.md")`
3. If multiple specs exist, present the list and ask the user which one to plan against
### Step 2: Determine mode
- **Spec found with `status: Approved`** → **spec-driven mode**. Read spec in full. This is the source of truth.
- **Spec found without `status: Approved`** → Print: "Spec exists but is not approved. Using it as reference in inline mode." Treat spec as context, not authority. → **inline mode**.
- **No spec found** → **inline mode**.
### Inline mode requirements
The user's message (argument to `zuvo:plan`) IS the planning input. Extract:
- **Goal:** what they want built
- **Scope:** which files/areas are affected (explore codebase if not stated)
…Read the whole file at its exact version.
How to install
mdr add greglas75/zuvo/plan@sha256:1597b3277e137325The line at the top of this page pins the label git:20261011.64038ce, 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_6u76ozquqc6qzue6)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 10 versions of this file, between Aug 10, 2026 and Oct 11, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261011.64038ce latest | 2026-10-11 | 64038ce | 48,082 B | A | view · diff |
| git:20261011.fccd137 | 2026-10-11 | fccd137 | 48,034 B | A | view · diff |
| git:20261010.746a930 | 2026-10-10 | 746a930 | 47,645 B | A | view · diff |
| git:20261009.d45481e | 2026-10-09 | d45481e | 47,363 B | A | view · diff |
| git:20260918.bee90df | 2026-09-18 | bee90df | 46,974 B | A | view · diff |
| git:20260909.3c6bf47 | 2026-09-09 | 3c6bf47 | 46,419 B | A | view · diff |
| git:20260907.a500f64 | 2026-09-07 | a500f64 | 46,419 B | A | view · diff |
| git:20260906.015072f | 2026-09-06 | 015072f | 46,136 B | A | view · diff |
| git:20260902.29a022a | 2026-09-02 | 29a022a | 46,360 B | A | view · diff |
| git:20260810.40e315f | 2026-08-10 | 40e315f | 45,920 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 (48082 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
greglas75/zuvo · 7 stars · license MIT · pushed 2026-11-03 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6u76ozquqc6qzue6 GET https://markdownregistry.com/api/v1/resolve?ref=greglas75/zuvo/plan GET https://markdownregistry.com/api/v1/blob/1597b3277e137325cff50e0be13df9bf0f13f4207a2f25cbc6271601b9f1e013
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.