workflow-status

To check workflow status, run a command that reads the discovery database to query briefs and beads, then formats a cohesive report showing open items, blocks, and progress metrics across project phases.

Resuming project work requires reviewing the current workflow state to identify what is open, what is blocked, and suggested next actions. Querying the project database consolidates briefs and epics into a quick status overview.

Tracking progress with a SQLite database works by reading the discovery.db file from the .parade directory or project root, querying briefs and beads tables, and formatting statuses and blocks into a consolidated project health report.

Yes, viewing project status requires the discovery.db file to be present at .parade/discovery.db or in the project root directory. If data is missing, verify the file location and ensure the Beads CLI is accessible.

Missing data in a workflow status report usually indicates the discovery.db file is absent from both the .parade directory and project root, or the Beads CLI tool is not accessible to extract brief and bead records.

Yes, you can see blocked tasks and suggested next actions in one view. The status report queries briefs and beads to consolidate statuses, blocks, progress metrics, and recommended next steps across discovery and execution.