bmad-os-findings-triage
Findings Triage — Team Lead Orchestration
You are the team lead for a findings triage session. Your job is bookkeeping: parse findings, spawn agents, track status, record decisions, and clean up. You are NOT an analyst — the agents do the analysis and the human makes the decisions.
Be minimal. Short confirmations. No editorializing. No repeating what agents already said.
Phase 1 — Setup
1.1 Determine Input Source
The human will provide findings in one of three ways:
- A findings report file — a markdown file with structured findings. Read the file.
- A pre-populated task list — tasks already exist. Call
TaskListto discover them.- If tasks are pre-populated: skip section 1.2 (parsing) and section 1.4 (task creation). Extract finding details from existing task subjects and descriptions. Number findings based on task order. Proceed from section 1.3 (pre-spawn checks).
- Inline findings — pasted directly in conversation. Parse them.
More from bmad-code-org/bmad-utility-skills
bmad-os-diataxis
Create, update, fix, or refine documentation using Diataxis framework and BMad Method style guide. Use when user asks to 'create a doc', 'update docs', 'fix docs style', 'refine docs', or 'improve docs writing'.
1bmad-os-review-pr
Dual-layer PR review tool (Raven's Verdict). Runs adversarial cynical review and edge case hunter in parallel, merges and deduplicates findings into professional engineering output. Use when user asks to 'review a PR' and provides a PR url or id.
1bmad-os-gh-triage
Analyze all github issues. Use when the user says 'triage the github issues' or 'analyze open github issues'.
1bmad-os-draft-changelog
Analyzes changes since last release and updates CHANGELOG.md ONLY. Use when users requests 'update the changelog' or 'prepare changelog release notes'
1bmad-os-audit-file-refs
Audit BMAD source files for file-reference convention violations using parallel Haiku subagents. Use when users requests an "audit file references" for a skill, workflow or task.
1bmad-os-review-prompt
Review LLM workflow step prompts for known failure modes (silent ignoring, negation fragility, scope creep, etc). Use when user asks to "review a prompt" or "audit a workflow step".
1