cdev-planner skillA
cdev-planner is agent-read markdown (skill) from elmayii/cdev: Use when planning work inside a single CDev-conditioned repository — turning an objective into batches in the local SPRINTS.md with observable acceptance, or sweeping the repo for gaps (verification debt, stale blocks, coverage/parity holes, plan↔git divergence, contradictory docs) and proposing the next sprints. Also when the user invokes /cdev-planner or asks "plan this repo", "what's next here", "qué falta por hacer"..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# CDev Planner
Planning brain for **one** conditioned repository. **Never implements code.** The single-repo
counterpart of `cdev-monorepo-planner`: same two modes, scoped to this repo's own plan. Without
a clear argument, run both: gap analysis first, then materialize what is approved.
Requires a conditioned repo (`docs/develop/` with `SPRINTS.md`, `AGENT_PROGRESS.md`, protocol,
clarity map). Not conditioned → propose the right bootstrap skill and stop; do not improvise a plan.
## Mode 1 — Materialize an objective (objective → executable batches)
1. **Read the repo state first**: repo guide → local protocol → `SPRINTS.md` → last
`AGENT_PROGRESS.md` entries → `git status` and recent commits. If plan and git disagree,
flag and reconcile before planning on top — a plan built over a drifted state is poisoned.
2. **Locate the objective in the clarity map** (`PRODUCT.md`):
- **DEFINED** → plan it fully;
- **PARTIAL** → plan the clear part; with a human present the unclear part becomes
questions (§ Closing open decisions); every assumption still made is recorded, dated, in
`DECISIONS.md`;
…Read the whole file at its exact version.
How to install
mdr add elmayii/cdev/cdev-planner@git:20260919.188d9cfmdr add elmayii/cdev/cdev-planner@sha256:6c56ea9e323ddae0Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_kektvlathkilbycg)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.188d9cf latest | 2026-09-19 | 188d9cf | 7,071 B | A | view · diff |
| git:20260815.5e4c63a | 2026-08-15 | 5e4c63a | 4,814 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 (7071 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
elmayii/cdev · 5 stars · license MIT · pushed 2026-09-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kektvlathkilbycg GET https://markdownregistry.com/api/v1/resolve?ref=elmayii/cdev/cdev-planner GET https://markdownregistry.com/api/v1/blob/6c56ea9e323ddae0c8522d47e4bff193173a2917f9f653240eb01abbb85eaf50
Your agent 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.