beads-planning

Plan and track multi-session work with epic-to-task decomposition.

Updated Nov 30, 2018
One-click install
npx skills add https://github.com/guygrigsby/dotfiles --skill beads-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: beads-planning
Source: https://github.com/guygrigsby/dotfiles/tree/main/opencode/skills/beads-planning
Command: npx skills add https://github.com/guygrigsby/dotfiles --skill beads-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

beads planning provides a structured approach to tracking complex, multi-session work by creating a persistent context that survives across sessions and handoffs, reducing context loss and miscommunication.

Core Features & Use Cases

  • Epic-based planning for multi-day projects with dependencies
  • Epics → tasks → subtasks decomposition to map work granularity
  • Proactive beads suggestions when complexity is detected and integration with session-close
  • Cross-team coordination through blockers and handoffs

Quick Start

Create a beads epic and outline an initial set of tasks to begin tracking multi-session work.

Frequently Asked Questions about beads-planning

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

FAQPage Schema
How do I track multi-session work without losing context across days?

Multi-session work tracking requires persistent context to survive handoffs. Using beads to preserve context allows you to map epic-to-task decompositions and proactively detect blockers across multiple days.

What is the best way to plan complex tasks with cross-team dependencies?

Planning complex tasks with cross-team dependencies involves decomposing epics into tasks and subtasks. This approach preserves context through beads and integrates with session-close workflows to reduce miscommunication.

When do I need beads planning for task management?

Beads planning is needed for task management involving work with three or more steps, dependencies, and cross-team handoffs. It applies to multi-day projects where context preservation across sessions is critical.

How do I start tracking an epic with multiple subtasks and blockers?

Start tracking an epic by creating a beads epic and outlining an initial set of tasks. This establishes multi-session work tracking with proactive complexity detection and context preservation for dependencies.

Can I integrate session-close handoffs with my multi-day project tracking?

Session-close handoffs integrate directly with multi-day project tracking. The workflow supports cross-team coordination through persistent beads context, reducing loss during epic, task, and subtask transitions.

Does this approach to context preservation work for small single-session tasks?

This context preservation approach does not suit single-session tasks. Beads planning targets complex workflows with three or more steps, dependencies, and multi-day cross-team handoffs requiring structured tracking.