Status

Overview

Provide a concise, human-friendly summary of project status or a specific bead. When no bead id is provided, run waif CLI tool to summarize recent work and current work in progress. When a bead id is provided, run bd show <bead-id> --json and provide a detailed explanation of that bead (title, status, assignee, description, blockers, and related links).

When To Use

• •User asks general project status (e.g., "What is the current status?", "Status of the project?", "audit the project", "audit").
• •User asks about a specific bead id (e.g., "What is the status of bd-123?", "audit bd-123").

Behavior

1. •Detect whether the user provided a bead id in the request.
2. •If no bead id is provided:
   • •Run waif in-progress --json to fetch in-progress work.
   • •Parse the returned JSON and produce a short summary including:
     • •Number of in-progress beads
     • •Highest-priority items, a short description, and their assignees
     • •Any items in a blocked state or missing assignees
     • •A one-line suggestion for next action (e.g., "Review bd-123 assigned to @alice")
     • •Run waif recent --json to fetch recently modified beads.
     • •Run bd show <bead-id> --json for the last 3 completed beads to get more information.
     • •Parse and summarize the last 3 completed beads with titles, most recent comments and assignees.
3. •If a bead id is provided:
   • •Run bd show <bead-id> --json to fetch bead details.
   • •Parse and present: title, status, assignee, priority, description, blockers, dependencies, comments count, and relevant links.
4. •Handle errors gracefully: if waif or bd are not available or return invalid JSON, present a helpful error and possible remediation steps.

Notes

• •Keep the output concise and actionable for quick human consumption.