cdev-monorepo-planner skillA
cdev-monorepo-planner is agent-read markdown (skill) from elmayii/cdev: Use when cross-repo work must be planned in a CDev Monorepo workspace — turning a system objective into SYSTEM_BATCHes with real local references, or analyzing all repos to find gaps (half-integrated features, broken contracts, pending parity) and proposing the next SYSTEM Sprints. Also when the user invokes /cdev-monorepo-planner or asks "plan the monorepo", "what's left to integrate", "planifica el monorepo", "qué falta por integrar"..
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 Monorepo Planner Planning brain of the workspace. **Never implements code.** Two modes depending on what is asked; without a clear argument, run both: gap analysis first, then materialize what is approved. ## Mode 1 — Materialize an objective (objective → executable SYSTEM_BATCH) **Before writing each SYSTEM_BATCH, close its open decisions with the human.** The rule lives in one place — § "Closing open decisions" of the `cdev-planner` skill: resolve this skill's base directory to its real path, read `../cdev-planner/SKILL.md`, and apply that section per SYSTEM_BATCH (including its no-human branch). System-level sources of open decisions, beyond that section's: which repos participate and which explicitly do not, the terms of a cross-repo contract, the sync-point artifact, implementation and deploy order, the verification level. 1. **Define the batch**: `SYS-<sprint>-B<n>` in the global `SPRINTS.md` with an observable objective, affected repos (and explicitly the non-affected ones if that clarifies scope), global acceptance and verification level L0–L3. It is born `PLANNED`. …
Read the whole file at its exact version.
How to install
mdr add elmayii/cdev/cdev-monorepo-planner@git:20260919.188d9cfmdr add elmayii/cdev/cdev-monorepo-planner@sha256:1c360436ad54186ePin 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_23disbvyuz6h5bkd)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.188d9cf latest | 2026-09-19 | 188d9cf | 5,702 B | A | view · diff |
| git:20260815.849c1e8 | 2026-08-15 | 849c1e8 | 5,097 B | A | view · diff |
| git:20260815.1fe0773 | 2026-08-15 | 1fe0773 | 5,097 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 (5702 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_23disbvyuz6h5bkd GET https://markdownregistry.com/api/v1/resolve?ref=elmayii/cdev/cdev-monorepo-planner GET https://markdownregistry.com/api/v1/blob/1c360436ad54186e51c93b84be82f5c801c00ae6cd72c49f977d2d5d99ac96f6
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.