Plan to Backlog
Materialize an approved cited plan into proportionate Beads tracking when the user asks for durable ownership. Recommends no item, one item, or a bounded epic; checks owners and duplicates; previews every write; applies only after exact confirmation.
Install
npx skills add flurdy/agent-skills --skill plan-to-backloggit clone --depth 1 https://github.com/flurdy/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/plan-to-backlog ~/.claude/skills/plan-to-backlogPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Plan to Backlog Proposal-first. May recommend no backlog change. Never writes without confirmation. Turn an approved architecture or implementation plan into the smallest justified durable Beads structure. Inspect the cited plan and existing work, decide whether no item, one focused item, or a bounded epic is warranted, preview the exact write set, then apply only that confirmed proposal. The canonical behavior and thresholds are defined in the [plan-to-backlog contract](references/contract.md). ## When to use Select this skill dynamically, or through `/plan-to-backlog`, only when: - an `/architect` or implementation plan has been explicitly approved; - the plan has a stable source or exact capturable session text; - the user explicitly asks to create or reconcile durable Beads ownership rather than continue planning; and - no-item versus single-item versus epic is still a meaningful decision. The existence or approval of a plan alone is not a trigger. Do not use this skill for raw ideas or Jira intake (`/triage`), plan refinement (`/architect`), retrospective backlog quality (`/backlog-groom`), or cross-system reconciliation (`/tracking-sweep` or `/trello-beads`). ## Usage ```text /plan-to-backlog <plan-source> ``` Accepted sources: - repository or workspace Markdown path; - Bead ID whose description, design, notes, or linked specification contains the plan; - Jira or Confluence key/URL when the runtime can retrieve the complete plan; or
Details
- Skill name
plan-to-backlog- Repository
- flurdy/agent-skills
- Path
skills/plan-to-backlog/SKILL.md- License
- MIT
- Repo updated
- 17 November 2026
FAQ
What does the Plan to Backlog skill do?
Materialize an approved cited plan into proportionate Beads tracking when the user asks for durable ownership. Recommends no item, one item, or a bounded epic; checks owners and duplicates; previews every write; applies only after exact confirmation.
How do I install the Plan to Backlog skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add flurdy/agent-skills --skill plan-to-backlog. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Plan to Backlog popular?
It lives in flurdy/agent-skills, which has 9 GitHub stars and 0 forks.
Related skills
Architect
9flurdy/agent-skills
Architecture and implementation planning gate for complex or high-blast-radius work. Produces evidence-backed decisions, reviewable slices, acceptance evidence, and conditional human review ownership without editing code.
Artifact Hygiene
9flurdy/agent-skills
Run a local-only, read-only advisory audit of publishable working-tree files and unpublished branch history with redaction-safe findings.
Backlog Groom
9flurdy/agent-skills
Auto-detects workspace unfinished backlogs across unique stores; otherwise local open beads. Flags thin prose, missing labels, drift, lifecycle and duplicates. Report-only; mutations need approval, destructive ones individually.
Refine
9flurdy/agent-skills
Read-only sizing assessment of one existing bead: keep whole, clarify, or split into independently valuable outcomes, possibly under an epic. Hands any approved change to /triage; never writes.
Confluence
9flurdy/agent-skills
Read Confluence pages and comments. Use to fetch design docs, ADRs, runbooks, or any wiki content for context when working on tasks.
To Linear
5adelrioj/claude-skills
Create a properly-templated Linear issue or epic-project (bug, story, epic) from the current conversation, on whichever team this repo files to. Use this WHENEVER the user wants to write, file, log, or create a ticket/story/bug/epic. Triggers on: write a bug ticket, file this as a bug, log a defect, create a user story, file tech debt, turn this into an epic, file a ticket, to linear, to-linear.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.