workflow-status

Aggregate discovery.db briefs and beads epics into a single workflow view.

2|3|Updated Jan 8, 2026
One-click install
npx skills add https://github.com/dot-do/dotdo --skill workflow-status-dot-do
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-status
Source: https://github.com/dot-do/dotdo/tree/main/.claude/skills/workflow-status
Command: npx skills add https://github.com/dot-do/dotdo --skill workflow-status-dot-do

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a unified view of the current workflow state by aggregating data from discovery.db and beads, helping teams understand where work stands without jumping between sources.

Core Features & Use Cases

  • Consolidated overview of discovery pipeline briefs and beads epics for quick orientation.
  • Visibility into active briefs, open epics, blocked tasks, and recent activity, with clear next-step suggestions.
  • Supports resuming work, cross-team planning, and prioritization by presenting a concise, actionable state.

Quick Start

Run the workflow-status check to pull the latest state across discovery and beads.

Frequently Asked Questions about workflow-status

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

FAQPage Schema
How do I consolidate workflow status across discovery briefs and beads epics?

Checking project momentum for cross-team planning requires a consolidated view of workflow state. Aggregating discovery.db briefs and beads epics surfaces recent activity and suggests next actions, enabling effective prioritization across teams.

How do I resume work on blocked tasks after a context switch?

To resume work on blocked tasks after a context switch, review the aggregated workflow state. The consolidated view identifies blocked tasks, recent activity, and suggested next actions, helping you pick up exactly where you left off.

Do I need consistent data sources to view active briefs and open epics together?

Yes, consistent data sources are required to view active briefs and open epics together. Robust formatting and consistent inputs from discovery.db and beads ensure the aggregated workflow state provides accurate, actionable insights.

What limitations exist when aggregating discovery pipeline briefs with beads epics?

A key limitation when aggregating discovery pipeline briefs with beads epics is the dependency on consistent data sources. Without robust formatting and reliable inputs, the unified workflow state may surface inaccurate insights or missing next-step suggestions.