plan-backlog

Design sprint backlog items and generate implementation plans in Plan Mode.

3|Updated Jan 30, 2026

Search Tags:#planning #brainstorming #backlog #sprint #sub-tasks #plan mode

Ready to run

npx skills add https://github.com/workingdanny911/dannys-claude --skill plan-backlog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-backlog
Source: https://github.com/workingdanny911/dannys-claude/tree/main/plugins/sprint/skills/plan-backlog
Command: npx skills add https://github.com/workingdanny911/dannys-claude --skill plan-backlog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill designs backlog items in detail within a sprint by guiding brainstorming, producing a formal implementation plan in Plan Mode, and attaching actionable sub-tasks to BACKLOG.md upon approval.

Core Features & Use Cases

Brainstorm backlog refinement to clarify scope and outcomes.
Generate a detailed implementation plan in Plan Mode and organize sub-tasks under the backlog.
Update BACKLOG.md with new sub-tasks after plan approval and create references in refs/plans/.

Quick Start

Start a planning session by triggering one of: plan task, plan feature, or plan backlog. During the session, discuss the backlog item, brainstorm approaches, draft a detailed implementation plan in Plan Mode, and await approval to update BACKLOG.md and create a plan document in refs/plans/.

Frequently Asked Questions about plan-backlog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I plan sprint backlog items with actionable sub-tasks?▼

Sprint planning for backlog items involves guided brainstorming, drafting a formal implementation plan in Plan Mode, and attaching actionable sub-tasks to BACKLOG.md once approved. This process clarifies scope and organizes references in refs/plans/.

What is the best way to brainstorm and refine backlog features for an active sprint?▼

Brainstorming and refining backlog features is best handled by a planning session that clarifies scope, generates a formal implementation plan in Plan Mode, and organizes resulting sub-tasks under the backlog item in BACKLOG.md.

Do I need external tools to generate an implementation plan and update BACKLOG.md?▼

No external tools are needed to generate an implementation plan or update BACKLOG.md. The process operates entirely within Plan Mode using existing sprint artifacts like BACKLOG.md, HANDOFF.md, and refs/ to formalize and store plans.

How does Plan Mode work for creating formal implementation plans?▼

Plan Mode formalizes implementation plans by guiding brainstorming sessions and storing the resulting plan documents in refs/plans/. Upon approval, it automatically appends the generated sub-tasks to BACKLOG.md for sprint execution.

Can I use this structured planning approach for both tasks and features in a sprint?▼

Yes, this structured planning approach applies to Features, Tasks, and Backlog items within an active sprint. It uniformly guides brainstorming, drafts implementation plans in Plan Mode, and updates BACKLOG.md with sub-tasks upon approval.

When should I not use Plan Mode for sprint planning and backlog design?▼

Avoid using Plan Mode for backlog design when items are outside an active sprint or lack standard artifacts like BACKLOG.md and HANDOFF.md. The workflow depends on these sprint files to store references and attach actionable sub-tasks effectively.