Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →rocm/rfc-backlog
Turn a technical RFC into an actionable backlog of JIRA stories and tasks, grounded in the codebase the RFC affects. Derives unified, independently-shippable work items (each with a user-story sentence, acceptance criteria, functional and non-functional requirements), presents them for review, then — unless run as a dry run — collects component/epic/label defaults and creates the tickets in JIRA.
Passed 12 of 18 test cases with the skill, and 7 of 18 without it.
and 5 more in the full report
8 fixed7 passed either way6 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
I want to convert an RFC located at `docs/rfcs/0050-flash-attn.md` into backlog items. How should the command be formatted?
| Checked | Without skill | With skill |
|---|---|---|
| Passes the RFC file path directly as a positional argument to the command. | Missed | Passed |
The instructions your model reads when the skill loads.
Convert a technical RFC into a backlog of JIRA work items. The aim is a backlog an engineer could pick up and start on: each item is a unified, independently-compilable, value-delivering piece of work — not a generic "implement the RFC" placeholder.
This skill is the planning bridge between /rfc-review (judge the design) and implementation (do the work). It reads the RFC, grounds the work in the actual codebase, and — when not a dry run — writes the tickets.
/rfc-backlog # Find the RFC on the current branch, derive a backlog, create tickets
/rfc-backlog docs/rfcs/my-rfc.md # Use a specific RFC file
/rfc-backlog --dry-run # Derive and display the backlog only — never touches JIRA
/rfc-backlog docs/rfcs/my-rfc.md --dry-run
Do NOT invoke for reviewing an RFC's design — use /rfc-review for that. This skill assumes the design is settled enough to plan against; if the RFC is still contentious, suggest a review first.
Apply this rule to every derived item — it decides the JIRA issue type:
The detailed, authoritative steps live in prompt.md. In brief:
assets/templates/backlog-item.md).--dry-run, stop here. No prompts, no JIRA writes.config.json defaults, confirm/collect component, epic, labels, project key; save back to config.json.test cases passed, vs 7 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.