Stats
Actions
Tags
From design-system-ops
Transforms audit findings into sprint-ready work items with effort estimates, acceptance criteria, and stakeholder rationale. Use after audits to create tickets from reports.
How this skill is triggered — by the user, by Claude, or both
Slash command
/design-system-ops:backlog-generatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
The gap between "here are the problems" and "here is the plan for the next eight weeks" is where most audit value dies. Findings get filed, not acted on. Teams read the audit, nod, then move on because the step from "TA-07: Button component tokens not aliased correctly" to "what do we build next sprint?" is too large.
The gap between "here are the problems" and "here is the plan for the next eight weeks" is where most audit value dies. Findings get filed, not acted on. Teams read the audit, nod, then move on because the step from "TA-07: Button component tokens not aliased correctly" to "what do we build next sprint?" is too large.
This skill bridges that gap by transforming audit output into structured work items that engineers and product managers can prioritise, estimate, and execute without needing to re-read the audit or negotiate what "fix the tokens" means. The output is sprints, not a wall of problems.
This skill transforms existing audit findings into work items. It does not run audits itself — if no audit output exists, run the relevant audit skill first. If the audit produced zero findings, there is no backlog to generate; confirm this with the user and stop. If the findings lack severity ratings or remediation guidance, flag the gap and produce work items with what is available, but note the missing context.
Accept input in any form: copy-paste audit report, file path, reference to prior audit skill output, or natural language description of findings.
Parse findings and extract:
Do not assume findings are complete. If a finding is vague ("tokens are broken"), ask clarifying questions before proceeding.
For each finding, assign one of these work item types:
Document your reasoning for each classification. Different teams prioritise differently — tech debt might be lower priority than bugs, and that's a decision, not a mistake.
For each finding, produce a work item with all of these fields:
Title: Action-oriented, engineer-readable. Prefer "Route component tokens through semantic tier" over "Fix TA-01" or "Token aliasing issue". The title should be understandable without the audit context.
Type: Bug fix, tech debt, enhancement, migration, or documentation (from step 2).
Effort estimate: T-shirt size with sizing rationale.
Include 2–3 sentences of sizing rationale (e.g., "M because the Button component changes are isolated to one file, but we need to update three variants and test accessibility scenarios"). Do not estimate from severity — a critical bug might be 30 minutes (S) if it's a one-line fix.
Acceptance criteria: 2–4 testable statements. Each should be verifiable by a reviewer without ambiguity.
Rationale: 1–2 sentences explaining why this work matters to the system and team, not just a technical description. Address: What breaks or becomes harder if this is deferred? Who does this unblock? Example: "Prevents new components from accidentally breaking the token hierarchy; unblocks the Q2 component library expansion."
Dependencies: List other work item IDs or titles that must complete first. Be strict — only list blocking dependencies, not nice-to-haves. If a task has no dependencies, write "None".
Priority: Inherit from audit severity (Critical → P0, High → P1, Medium → P2, Low → P3), but adjust upward if the item unblocks multiple other items, or downward if high-effort with low impact.
Sort work items into phases based on dependencies and effort:
Do not create a phase assignment that violates dependency order (e.g., assigning a Sprint 1 item that depends on a Sprint 2 item). Review the dependency DAG before finalising phase groups.
Create a visual or textual dependency map showing which items block which other items. Format: simple text DAG or a markdown table with columns for Item, Depends On, Unblocks.
Flag any circular dependencies immediately — they indicate a misunderstanding of the problem or a need to re-scope work items. Example: If Item A depends on Item B and Item B depends on Item A, stop and clarify the actual order with the team.
Generate a markdown document with:
Summary section:
Summary table: All work items in a single table with columns: ID, Title, Type, Effort, Priority, Phase, Dependencies. Keep descriptions short; readers will dive into detailed cards for context.
Detailed cards: One card per work item with all fields from step 3 (title, type, estimate with rationale, acceptance criteria, rationale, dependencies, priority).
Dependency section: Text or ASCII representation of the dependency DAG. Highlight any chain longer than 3 items (suggests the phase grouping may be too aggressive).
Tool mapping section: Guidance for translating this markdown output into Jira, Linear, GitHub Issues, or Asana without tool-specific API calls. Include field mapping (e.g., "Effort = Story Points or custom field; Priority = Jira priority label; Phase = Sprint or custom field"). Do not write scripts or API calls — keep this human-readable guidance.
Every work item title is action-oriented and engineer-readable. A developer should understand what to build without re-reading the audit. Titles like "Flatten token hierarchy" or "Add size variant to Button" pass; "Fix token issue" does not.
Acceptance criteria are testable. Each criterion should be verifiable by code review, test output, or inspection without debate. "Button component uses semantic tokens" is vague; "Button component has zero direct references to primitive tokens" is testable.
Effort estimates include sizing rationale, not just a letter. Why is this S and not M? Why is that L and not XL? Document the reasoning (scope, risk, coordination overhead, etc.).
Rationale explains business impact, not just technical description. Do not repeat the audit finding. Explain why engineers should care, what risk the team avoids, what capability it unblocks.
Dependencies form a valid DAG. No circular references. If Item A depends on Item B, Item B cannot depend on Item A (directly or transitively). Run a topological sort to verify.
Phase grouping respects dependency order. No Sprint 1 item can depend on a Sprint 2 item. No Sprint 2 item can depend on a Backlog item (unless you're willing to schedule Backlog work early). Review the dependency map against phase assignments before finalising.
For audit reports with fewer than 10 findings, produce a single prioritised list (Immediate, Near-term, Backlog) rather than phased sprints. The structure is the same; the grouping is simpler. Dependencies still matter even for small systems.
npx claudepluginhub murphytrueman/design-system-opsExports audit findings from security, performance, accessibility, or quality analyses to Teamwork tasks with priority and template mapping.
Decomposes epics into trackable, right-sized tasks with Size, Urgency, Risk, ROI, Blast Radius, LOE ratings. Audit-aware modes use codebase reports or handoff.yaml; standalone option.
Grooms backlog items by fact-checking claims against sources, running RT-ICA analysis per item, spawning groomer agents, and writing updates via MCP tools. Use before planning or execution.