build-roadmap SKILL.md skillA
build-roadmap from cmc-27/pass-the-parcel is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add cmc-27/pass-the-parcel/build-roadmap@v4Pins v4 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- cmc-27/pass-the-parcel
- Path
.devops/skills/build-roadmap/SKILL.md- Versions recorded
- 6
- Latest version
- v4, committed Sep 29, 2026
- First version recorded
- Aug 20, 2026
- Size
- 6,855 bytes
- Repository stars
- 35
- License
- MIT
Make sure to use this skill whenever the user mentions building a product roadmap, creating a roadmap, defining themes or epics, /build-roadmap, planning strategic phases, or wants to map out the future of a product at a high level above the backlog. Use it to create or update a product-roadmap.md file and optionally scaffold aligned epics and implementation plans.
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
# Build Roadmap — Product Roadmap Builder
## Context: Document Hierarchy
The project operates on a three-tier planning hierarchy:
| Level | Document | Versioning | Location |
|---|---|---|---|
| **L1 — Theme** | `product-roadmap.md` | T1, T2, T3… | `.devops/backlog/` (master doc) |
| **L2 — Epic** | `product-roadmap.md` (sections) | T{n}-E1, T{n}-E2… | `.devops/backlog/` (master doc) |
| **L3 — Impl Plan** | `T{n}-E{n}.{impl}-{slug}-plan.md` | .01, .02, .03… | `.devops/backlog/` (parked) → `.devops/plans/` (claimed) |
A **Theme** is the strategic container (e.g. "Master Data Management"). An **Epic** is a large body of work within a theme (e.g. "Material Import & Integrity"). An **Implementation Plan** is a single executable deliverable (the parcel plan).
---
## 1. Discover Existing Roadmap
Before doing anything else, scan for an existing `product-roadmap.md` in the project's `.devops/backlog/` directory. If one exists, read it in full to understand current theme definitions, epic breakdowns, scope, and version number. Also read `.devops/backlog/backlog-index.md` to see what prefix codes are already assigned.
---
## 2. Determine Mode (question)
…Read the whole file at its exact version.
How to install
mdr add cmc-27/pass-the-parcel/build-roadmap@sha256:c37d10f49a33621fThe line at the top of this page pins the label v4, 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_cl6hm5dbeajhhjfe)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 20, 2026 and Sep 29, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v4 latest | 2026-09-29 | f7d4578 | 6,855 B | A | view · diff |
| v3 | 2026-09-17 | 0ed41bf | 6,813 B | A | view · diff |
| v2 | 2026-09-12 | 4364a55 | 6,717 B | A | view · diff |
| v1 | 2026-09-03 | 31da0f7 | 6,479 B | A | view · diff |
| git:20260903.60a41b1 | 2026-09-03 | 60a41b1 | 6,448 B | A | view · diff |
| git:20260820.d4a30da | 2026-08-20 | d4a30da | 4,773 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 (6855 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
cmc-27/pass-the-parcel · 35 stars · license MIT · pushed 2026-10-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cl6hm5dbeajhhjfe GET https://markdownregistry.com/api/v1/resolve?ref=cmc-27/pass-the-parcel/build-roadmap GET https://markdownregistry.com/api/v1/blob/c37d10f49a33621fa6acf546caed9e30301333653ac677ce89a5b228e8066d6f
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.
More from cmc-27/pass-the-parcel
Every file in cmc-27/pass-the-parcel