follow-ups SKILL.md skillA
follow-ups from theam/claude-dev-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add theam/claude-dev-kit/follow-ups@git:20260902.b8d21a5Pins git:20260902.b8d21a5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- theam/claude-dev-kit
- Path
plugins/fullstack-dev-kit/skills/follow-ups/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260902.b8d21a5, committed Sep 2, 2026
- Size
- 3,802 bytes
- Repository stars
- 17
- License
- Apache-2.0
Turn the loose ends a finished story leaves — out-of-scope notes, deferred review findings, deliberate TODOs — into tracked follow-up work items in the team's tracker, linked to the source story, after approval. Supports Jira, Linear, GitHub Issues, and Azure DevOps via adapters. Use at the end of a story, or when the user asks to track follow-ups.
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
# Follow-ups Close the loop: when a story finishes, the loose ends it surfaced should be **tracked**, not just described in the PR body. This skill turns them into real work items in the configured tracker, **linked back to the source story** — created only after approval. It's the tracking counterpart to the "Out of scope / follow-ups" section `create-pr` already writes. ## Preconditions - `.claude/dev-kit.json` exists with a `tracker` block (otherwise run `dev-kit-setup` first). - The adapter's backend is authenticated (MCP connector authorized, or `gh`/`az` logged in) — otherwise tell the user how to authenticate and stop. - The **source story key** (the item just delivered) is known, for linking. If unknown, ask once. ## 1. Gather the loose ends — only real ones Collect follow-ups from the story just finished, from where they were already surfaced: - the **"Out of scope / follow-ups"** list in the `create-pr` PR body, - **deferred review findings** from `fix-pr` / `pr-review` (the "defer to a tracked issue" bucket), - deliberate **TODOs / known gaps** the implementation left. …
Read the whole file at its exact version.
How to install
mdr add theam/claude-dev-kit/follow-ups@sha256:ff9d2c69dbda948fThe line at the top of this page pins the label git:20260902.b8d21a5, 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_mthtidh3pua3dwk6)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 2, 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 (3802 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
theam/claude-dev-kit · 17 stars · license Apache-2.0 · pushed 2026-09-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_mthtidh3pua3dwk6 GET https://markdownregistry.com/api/v1/resolve?ref=theam/claude-dev-kit/follow-ups GET https://markdownregistry.com/api/v1/blob/ff9d2c69dbda948ffde5e1aa18d57436e13e6246832bd9e88fee026c4e93910b
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 theam/claude-dev-kit
Every file in theam/claude-dev-kit