skills.rest
wellmaintained
wellmaintainedOFFICIAL
Explore all skills by this author →
WebsiteGitHub

discovery-tree-workflow

Plans and tracks work using hierarchical outcome-based beads with color-coded statuses and on-demand expansion.

Updated Aug 23, 2026
Search Tags:#workflow#project management#beads#agile#task tracking#team coordination#outcome-driven
One-click install
npx skills add https://github.com/wellmaintained/skills --skill discovery-tree-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discovery-tree-workflow
Source: https://github.com/wellmaintained/skills/tree/main/.claude/skills/discovery-tree-workflow
Command: npx skills add https://github.com/wellmaintained/skills --skill discovery-tree-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bd.

What problem does it solve?

This Skill eliminates the chaos of complex, opaque project planning and tracking. It replaces rigid, upfront planning with an emergent, outcome-focused approach, making work visible and coordinating agents efficiently. It frees you from manual task lists and provides a clear, hierarchical view of progress, ensuring that work evolves with discovery.

Core Features & Use Cases

  • Outcome-Driven Planning: Focus on "what will be true" rather than "how to make it true," empowering implementing agents and ensuring verifiable results.
  • Just-in-Time & Emergent Breakdown: Start with minimal detail and grow the work breakdown structure organically as discoveries are made, reducing wasted upfront planning and adapting to new information.
  • Agent Coordination & Visual Status: Clearly define work units (beads) for implementing agents, track progress visually, and ensure everyone sees the current state at a glance, fostering seamless collaboration.
  • Use Case: When starting a new feature like "User Authentication System," use this skill to define the root epic and initial outcomes (e.g., "User can sign in," "Invalid credentials show error"). As development progresses, new requirements or complexities are discovered, they are added to the tree, keeping the project visible and adaptable without needing to re-plan from scratch.

Quick Start

To start a new project, create a root epic and bead: bd create "Users can securely access their accounts" -t epic -p 1 --json bd create "User authentication system [root]" -t task -p 1 --json bd dep add <root-bead-id> <epic-id> -t parent-child

Frequently Asked Questions about discovery-tree-workflow

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

FAQPage Schema
How do I coordinate project planning and tracking across a team using outcome-driven methods?▼

Outcome-driven planning focuses on 'what will be true' rather than 'how to make it true.' Discovery Tree workflow uses beads—PR-sized work units with hierarchical epic linking and color-coded status—to make progress visible, coordinate agents, and adapt to discoveries without constant re-planning.

What's the difference between upfront task planning and just-in-time breakdown for complex work?▼

Just-in-time breakdown starts with minimal detail and grows organically as discoveries emerge, reducing wasted upfront planning. Unlike rigid task lists, this approach captures emergent requirements and keeps the work breakdown structure adaptable to new information discovered during implementation.

How do I visualize work progress and coordinate multiple agents on a single feature or investigation?▼

Discovery Tree workflow provides a hierarchical, color-coded view of beads representing work units. Each bead shows status and links to parent epics, ensuring all agents see current progress at a glance and enabling seamless collaboration on related tasks and complex investigations.

Can I use this workflow for features, bugs, and investigations involving multiple related tasks?▼

Yes. Discovery Tree workflow applies to non-trivial work—features, bugs, or investigations—requiring multiple related tasks and agent coordination. Beads represent each PR-sized outcome, with hierarchical linking that accommodates complex dependencies and emergent requirements.

How do I set up an initial project structure before work begins?▼

Create a root epic defining the desired outcome (e.g., 'Users can securely access their accounts') and link it to an initial root bead representing the task. Use hierarchical parent-child relationships to establish the skeleton; expand with additional beads as requirements emerge during development.

Related Skills

Explore More Product & Management Skills→
mattwynnemattwynne
54

Discovery Tree Workflow

Structure work as discovery trees with epics, root tasks, and hierarchical subtasks.

Community
Advanced
profmikegreeneprofmikegreene
1

status-monitoring

Track pilot progress against milestones and generate status reports.

Community
Basic
KuassKuass
1

beads-bridge

Coordinate multi-agent tasks across sessions using Beads and OpenCode tools.

Community
Advanced
l3ochol3ocho

task-sizing

Enforce XS–XL task sizing and require breakdowns for L/XL tasks.

Community
Advanced