Discovery Tree Workflow

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

54|6|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/mattwynne/yaks --skill discovery-tree-workflow-mattwynne
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Discovery Tree Workflow
Source: https://github.com/mattwynne/yaks/tree/main/.claude/skills/discovery-tree-workflow
Command: npx skills add https://github.com/mattwynne/yaks --skill discovery-tree-workflow-mattwynne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables just-in-time planning by structuring work as a discovery tree with epics, root tasks, and hierarchical subtasks, reducing upfront guesswork and scope creep.

Core Features & Use Cases

  • Epic and root task structure to track progress and deliver user value.
  • Hierarchical tasks with parent-child relationships to adapt plans as complexity emerges.
  • Visual status indicators and a lightweight workflow to coordinate ongoing work across teams.

Quick Start

Create an epic and root task, then break down only what you need to start and add tasks as complexity emerges.

Frequently Asked Questions about Discovery Tree Workflow

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

FAQPage Schema
How do I plan product development when requirements emerge iteratively?

Plan incrementally with hierarchical task trees by defining an epic and root task, then break down only what you need to start. Add subtasks as complexity emerges to reduce upfront guesswork and scope creep.

What is a discovery tree and how does it help with agile planning?

A discovery tree structures work hierarchically with epics, root tasks, and parent-child subtasks. It supports agile planning by allowing you to adapt plans and re-scope tasks as new requirements emerge during iterative product development.

How do I break down an epic into manageable subtasks without over-planning?

Create an epic and root task, then use hierarchical parent-child relationships to break down only what you need to start. Add new subtasks just-in-time as complexity emerges to avoid upfront guesswork and scope creep.

Can I re-scope tasks and add new ones as complexity emerges during a project?

Yes, you can re-scope tasks and add new ones as work progresses. The discovery tree workflow uses hierarchical relationships and color-coded status indicators to adapt plans dynamically when complexity emerges.

Does this planning approach require upfront dependencies or specific components?

No dependencies or components are required. This planning approach uses a lightweight workflow with optional scripts, references, and assets to coordinate ongoing work across teams.