cdev-status skillA
cdev-status is agent-read markdown (skill) from elmayii/cdev: Use when the user asks where a CDev-conditioned repository stands — progress of the active sprint (or a named one) measured on three axes, functional requirements, non-functional requirements and user stories — after several batches have run, before deciding what to run next, or when coming back to a repo. Also when the user invokes /cdev-status or asks "status of the sprint", "where are we", "how far along is this", "status funcional", "por dónde vamos", "qué llevamos del sprint"..
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 Status A read-only reading of **one** conditioned repository: how far the sprint's intent has been walked, on three axes. **It edits no file and marks no state.** The single-repo counterpart of `cdev-monorepo-status`, which applies this skill's method by reference — this file is the method's single home. Requires a conditioned repo (`docs/develop/` with `SPRINTS.md`, `AGENT_PROGRESS.md`, protocol). Not conditioned → propose the `bootstrap` skill and stop; do not improvise a status. ## The idea The plan holds no list of requirements or user stories, on purpose: a formalized list has to be kept current while a feature is still being discovered, and that maintenance is what drifts. The intent lives in free form — the sprint's objective, each batch's text and acceptance, the decisions, the handoff. This skill engineers the three axes **at read time** from that raw chain, and says where each item came from. ## Scope - **No argument** → the `ACTIVE` sprint. None `ACTIVE` → say so, and read the most recently closed one. - **A sprint named** → that sprint. - **`all`** → one line per sprint (state, batches closed of N, the three percentages); full …
Read the whole file at its exact version.
How to install
mdr add elmayii/cdev/cdev-status@git:20260920.2c949abmdr add elmayii/cdev/cdev-status@sha256:2ba1f10e1a0a69bePin 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_dgb4tyha76ffgtjh)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260920.2c949ab latest | 2026-09-20 | 2c949ab | 6,547 B | A | view · diff |
| git:20260919.a226148 | 2026-09-19 | a226148 | 6,087 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 (6547 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_dgb4tyha76ffgtjh GET https://markdownregistry.com/api/v1/resolve?ref=elmayii/cdev/cdev-status GET https://markdownregistry.com/api/v1/blob/2ba1f10e1a0a69be98ef93d799e60e2d3f7ff776df3bb0cf89dd41c68d5efa39
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.