spec-readiness skillA
spec-readiness is agent-read markdown (skill) from eltmon/overdeck: Evaluate an issue or epic's requirements readiness before development begins. Produces a scored report (0-100) across 5 dimensions with detailed findings, actionable blockers, and a JSON sidecar for dashboards. Works with any issue tracker (Linear, GitHub, GitLab, Rally, Jira). Use a wrapper skill to customize branding and tracker-specific field mappings..
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
# Spec Readiness — Orchestrator
## Philosophy
The most important work on a feature is the PRD/spec, not the implementation. Every major overrun traces back to **requirements incomplete when development started.** This skill measures requirements maturity as a **leading indicator**.
## Wrapper Architecture
This is the **core scoring engine**. It is designed to be wrapped by a thin customization layer.
### How Wrapping Works
A wrapper skill overrides branding, tracker bindings, and field mappings by providing a `config.yaml`:
```
1. Check: Does ~/.overdeck/skills/spec-readiness-*/config.yaml exist?
2. If yes: Load tracker bindings, field mappings, branding, conventions
3. If no: Use defaults (generic branding, auto-detect tracker)
```
### Wrapper Config Schema
```yaml
# ~/.overdeck/skills/spec-readiness-mycompany/config.yaml
tracker:
type: linear | github | gitlab | rally | jira
tools:
get_issue: "mcp__linear__get_issue"
list_child_issues: "mcp__linear__list_issues"
get_comments: "mcp__linear__list_comments"
search_issues: "mcp__linear__list_issues"
get_relations: "mcp__linear__get_issue" # with includeRelations=true
…Read the whole file at its exact version.
How to install
mdr add eltmon/overdeck/spec-readiness@git:20260618.e501626mdr add eltmon/overdeck/spec-readiness@sha256:6ecc76db4fe1a4baPin 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_pvejqfgypgq5q6uz)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260618.e501626 latest | 2026-06-18 | e501626 | 15,730 B | A | view · diff |
| git:20260522.817c2c7 | 2026-05-22 | 817c2c7 | 15,738 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 (15730 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
eltmon/overdeck · 28 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_pvejqfgypgq5q6uz GET https://markdownregistry.com/api/v1/resolve?ref=eltmon/overdeck/spec-readiness GET https://markdownregistry.com/api/v1/blob/6ecc76db4fe1a4babb89548ebe0d20e4a82d35e6a93f87c568573962581f21c3
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.