Skill

BMAD Workflow Status

Checks BMAD project progress via config.yaml and workflow-status.yaml, displays phase status with icons, and recommends next steps like creating PRD. Useful for tracking BMAD workflows.

developer-tools

cli-tools

npx claudepluginhub urso/claudev --plugin bmad

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/bmad:status

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

**Goal:** Display current project status and recommend next workflow.

SKILL.md

76 lines · ~409 tokens

Similar Skills

bmad-help

Analyzes BMad project state from catalog CSV, configs, artifacts, and query to recommend next skills or answer questions. Useful for help requests, 'what next', or starting BMad.

bmad

bmad-help

48.0k

Orients users within a BMad workflow by identifying current module and phase, recommending next skills with reasoning, and answering module-related questions from documentation.

bmad-pro-skills

skill-status

3.5k

Displays project status, roadmap progress, blockers, and next-action suggestions based on workflow state. Use for progress checks and orientation.

1 file

octo

Stats

LanguagePython

Parent stars10

Parent forks2

MaintenanceExcellent

Last CommitMar 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

BMAD Workflow Status

Goal: Display current project status and recommend next workflow.

Execution Steps

Check for BMAD initialization:

Look for bmad/config.yaml
If not found: suggest running /bmad:init

Load configuration:

Read bmad/config.yaml for project info
Read planning-artifacts/workflow-status.yaml for progress

Display status:

Project: {project_name} ({project_type}, Level {project_level})

✓ Phase 1: Analysis
  ✓ product-brief (planning-artifacts/product-brief-{date}.md)
  - research (optional)

→ Phase 2: Planning [CURRENT]
  ⚠ prd (required - NOT STARTED)
  - ux-design (optional)

Phase 3: Solutioning
  - architecture (required)
  - epics-stories (not started)

Phase 4: Implementation
  - sprint-planning (not started)

Determine recommendations based on:

Project level
Completed workflows
Required vs optional workflows
Workflow dependencies

Recommend next step:

Recommended: Create PRD with /bmad:create-prd

Why? For Level 2+ projects, PRD ensures all requirements are
captured before architecture and implementation.

Offer to execute:

Would you like to start /bmad:create-prd now?

Status Icons

✓ Complete (with file path)

→ Current phase

⚠ Required but not started

Optional or not started

Usage

/bmad:status

Run anytime to check progress and get recommendations.