skills.rest
firefly-events
firefly-eventsOFFICIAL
Explore all skills by this author →
GitHub

status

Report real-time status of active Hive workflows across epics and stories.

1|Updated Apr 10, 2026
Search Tags:#workflow#planning#story#hive#status#epic#dependency
One-click install
npx skills add https://github.com/firefly-events/plugin-hive --skill status-firefly-events
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: status
Source: https://github.com/firefly-events/plugin-hive/tree/main/skills/status
Command: npx skills add https://github.com/firefly-events/plugin-hive --skill status-firefly-events

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Report the status of active Hive workflow epics to help teams stay aligned on progress, blockers, and deadlines.

Core Features & Use Cases

  • Real-time epic and story status across multiple epics.
  • Dependency visibility and progress tracking with per-epic details.
  • Kickoff gate checks to ensure the project has been initialized before status evaluation.

Quick Start

Run the status command, optionally providing an epic ID, to view the current status of active Hive epics and stories.

Frequently Asked Questions about status

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

FAQPage Schema
How do I track Hive workflow status across multiple epics at a glance?▼

Track Hive workflow status by running the status command to identify and report real-time progress across epics and stories, including pending, in-progress, completed, or failed states. It loads epic metadata and workflow definitions to compute current workflow statuses.

Can I view dependency graphs for active Hive stories and epics?▼

Yes, you can view dependency graphs for active Hive stories and epics. The status reporting evaluates per-epic progress and generates a dependency graph to provide visibility into workflow relationships and blockers.

What is the best way to check real-time epic progress for projects tracked in .pHive?▼

The best way to check real-time epic progress for projects tracked in .pHive is to run the status command, optionally providing an epic ID. It loads kickoff gates, episode definitions, and hive.config.yaml to compute and report per-epic workflow execution states.

Do I need to initialize kickoff gates before evaluating Hive workflow status?▼

Yes, you need to initialize kickoff gates before evaluating Hive workflow status. The status reporting integrates kickoff gate checks to ensure the project has been properly initialized before it computes and reports the current workflow states.

How does the status command compute workflow states from episode and workflow definitions?▼

The status command computes workflow states by loading kickoff gates, epic metadata, and episode/workflow definitions. It integrates with hive.config.yaml for execution context to identify and report the real-time status of active Hive workflows.

Why does my Hive workflow status report show pending or failed states for active stories?▼

Your Hive workflow status report shows pending or failed states because the status command computes real-time execution results from episode definitions and kickoff gates. It identifies current per-epic progress, accurately reflecting pending, in-progress, completed, or failed workflow conditions.

Related Skills

Explore More Product & Management Skills→
firefly-eventsfirefly-events

kickoff

Detect project type and configure the Hive kickoff workflow.

Official
Intermediate
maltemdmaltemd

writing-status-and-progress

Generate status labels and progress messages for UI states.

Community
Intermediate
MarkusonMarkuson

bmad-sprint-planning

Parse epic and story markdown to generate sprint-status.yaml tracking files.

Community
Advanced
GDSDNGDSDN
3

po-close-story

Close product development stories by updating status, changelog, and epic indexes.

Community
Advanced