build-epic SKILL.md skillA
build-epic from beakpoint-insights/roost is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add beakpoint-insights/roost/build-epic@git:20261026.505a1daPins git:20261026.505a1da in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- beakpoint-insights/roost
- Path
skills/build-epic/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261026.505a1da, committed Oct 26, 2026
- First version recorded
- Oct 26, 2026
- Size
- 13,286 bytes
- Repository stars
- 30
- License
- MIT
Build an epic from its tech lead prompt to release QA, through the user's repo sessions (one per repo in the team's roost config). If the stories have no kickoff comments yet, it first sends the epic's tech lead prompt to the lead repo's session, brings the plan to the user for approval, and has the kickoffs posted. Then it runs run-slice for each story in order, slice-handoff between stories, the epic's "before release" work, review-epic, close-out-epic and release-qa. Starts without asking…
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 Epic
You coordinate a whole epic the way `run-slice` coordinates one story. You never edit, build or run tests in any repo yourself. One session per repo in the config's `repos` does the work, through `SendMessage`, exactly as `run-slice` describes. The **lead session** is the session of `planning.lead_repo`.
**First, load the team config with `roost-config`.**
Being asked to build the epic is the go-ahead. Don't ask for another one, at the start or between slices. Tell the user what you started and why, and keep going.
## Inputs
- **EPIC:** the epic's ticket key.
- A session for each repo the epic touches must be open. If one isn't, that's a blocker: ask the user to open it, and stop.
## Status: "where are we on the epic?"
Use `run-slice`'s Status for an epic: one row per story in story order, then the step table for the story in progress. Add one line under it: the counts from the epic's **Carry-over** comment ("before release: 2, later: 5"). Read-only; send nothing.
## 1. Find where the epic is
…Read the whole file at its exact version.
How to install
mdr add beakpoint-insights/roost/build-epic@sha256:d9f8a8c7da3c2ec9The line at the top of this page pins the label git:20261026.505a1da, 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_hwgqn66bmtnadxm6)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, all committed on Oct 26, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261026.505a1da latest | 2026-10-26 | 505a1da | 13,286 B | A | view · diff |
| git:20261026.dec76bc | 2026-10-26 | dec76bc | 13,265 B | A | view · diff |
| git:20261026.c517de3 | 2026-10-26 | c517de3 | 13,105 B | A | view · diff |
| git:20261026.66cdcd9 | 2026-10-26 | 66cdcd9 | 12,519 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 (13286 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
beakpoint-insights/roost · 30 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hwgqn66bmtnadxm6 GET https://markdownregistry.com/api/v1/resolve?ref=beakpoint-insights/roost/build-epic GET https://markdownregistry.com/api/v1/blob/d9f8a8c7da3c2ec98be171b5f981b355368ace28a59f2ae5bb69756c8f8cae18
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.