main-workflow-router_skill

This skill automatically routes product work between BMAD and OpenSpec, tracks status, and guides you through the appropriate workflow phases.
  • Python

61

GitHub Stars

4

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill bacoco/bmad-skills --skill main-workflow-router

  • CHECKLIST.md498 B
  • REFERENCE.md17.9 KB
  • SKILL.md7.4 KB
  • WORKFLOW.md879 B

Overview

This skill routes work between OpenSpec (L0-1) and BMAD (L2-4), tracks project status, and guides the team through defined phases. It auto-invokes at project start or on status queries, initializes workflow state if needed, and recommends the next skill with concrete prerequisites and rationale.

How this skill works

The router assesses intent and complexity (levels 0–4) from the user's description or project summary, then selects OpenSpec for small changes or BMAD for discovery and complex work. It inspects status files (e.g., docs/bmad-workflow-status.md, docs/sprint-status.yaml, workflow-status.md) and artifact indexes, validates quality gates in CHECKLIST.md, updates workflow state, and returns the next action and required inputs.

When to use it

  • At the start of any BMAD project or when the user says “start project”, “new project”, or “initialize”
  • When the user asks workflow questions like “what's next?”, “where am I?”, or “check status”
  • When a user describes a product idea or feature and you need routing between lightweight change vs full product workflow
  • When a downstream skill finishes a phase and you need to transition to the next phase
  • When workflow-status.md or equivalent files are missing and initialization is required

Best practices

  • Always verify required artifacts and quality gates in CHECKLIST.md before advancing phases
  • Ask clarifying questions when complexity is ambiguous (default to asking rather than assuming)
  • Auto-initiate workflow files only when no status file exists; otherwise read and recommend next steps
  • Halt routing and report missing prerequisites or blockers with actionable remediation
  • Escalate to BMAD when scope grows beyond Level 1; downgrade to OpenSpec for simple fixes

Example use cases

  • User types “start project” — skill initializes workflow files and recommends discovery or openspec based on initial summary
  • User asks “what should I do next?” — skill reads workflow-status.md, summarizes progress, and routes to the appropriate skill
  • Developer reports a bug labeled “small change” — skill routes to openspec-change-proposal and scaffolds a change workspace
  • PM delivers a PRD — skill confirms prerequisites and routes to solutioning or architecture as appropriate
  • A downstream skill completes discovery — skill updates state and queues planning and UX phases

FAQ

It assesses project complexity (0–4) from the description: Level 0–1 → OpenSpec, Level 2–4 → BMAD. If unclear, it asks clarifying questions.

What happens if required status files are missing?

The skill auto-runs initialization workflows to create status files and prompts the user for minimal inputs to populate them.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational