tdmcp-backlog-campaign SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.
tdmcp-backlog-campaign from hybridlabor-api/bdb-dev-optimized-agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-backlog-campaign@git:20260727.48beb34Pins git:20260727.48beb34 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- hybridlabor-api/bdb-dev-optimized-agent-skills
- Path
mcps/tdmcp/.claude/skills/tdmcp-backlog-campaign/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260727.48beb34, committed Jul 27, 2026
- Size
- 13,463 bytes
- Repository stars
- 7
- License
- Apache-2.0
Drive a whole tdmcp feature BACKLOG to completion as resumable, wave-by-wave releases — the campaign layer ABOVE tdmcp-pipeline/tdmcp-feature-lead. Use whenever the user wants to implement an ENTIRE backlog or discovery file (e.g. _workspace/discovery*/FEATURE_BACKLOG*.md), 'all the features', many features across multiple releases, or a long autonomous build campaign, AND for every follow-up: continue/resume the campaign, run the next wave, re-run a failed wave, fold in QA results, or check…
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
# tdmcp-backlog-campaign — whole-backlog delivery A single feature-build wave is already handled well by **`tdmcp-pipeline`** (the five specialists) and **`tdmcp-feature-lead`** (parallel builders + single-writer integrate). This skill is the layer they do not provide: driving an entire **backlog** of dozens of features to completion across **multiple themed releases**, *resumably*. It is a thin, ledger-driven loop over the existing pipeline — it adds idempotency, resilience, shared-schema sequencing, and a checkpoint/release policy; it does **not** re-implement building. > **When NOT to use this:** one feature, or one small ad-hoc batch → `tdmcp-pipeline`. > A whole survey/backlog file, "all the features", or "continue the campaign" → here. ## The two things this skill owns 1. **The ledger** (`_workspace/campaign_<id>/ledger.json`, in the **main repo checkout** — resolve with `dirname "$(git rev-parse --path-format=absolute --git-common-dir)"`, never the worktree, so state survives worktree cleanup and is shared across sessions). One row per feature; `build-ledger.mjs` beside it regenerates the static plan **merge-safely** (preserves live state). This is the …
Read the whole file at its exact version.
How to install
mdr add hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-backlog-campaign@sha256:36fd586cd59703d5The line at the top of this page pins the label git:20260727.48beb34, 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_etjeu6zhfkstbtjl)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jul 27, 2026.
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 (13463 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
hybridlabor-api/bdb-dev-optimized-agent-skills · 7 stars · license Apache-2.0 · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_etjeu6zhfkstbtjl GET https://markdownregistry.com/api/v1/resolve?ref=hybridlabor-api/bdb-dev-optimized-agent-skills/tdmcp-backlog-campaign GET https://markdownregistry.com/api/v1/blob/36fd586cd59703d5f5c5a94636488f6d127938d1f0dde70be56bf76a68586367
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 hybridlabor-api/bdb-dev-optimized-agent-skills
Every file in hybridlabor-api/bdb-dev-optimized-agent-skills