Skip to content

feat(skills): add bmad-os-findings-triage HITL triage skill#1804

Merged
bmadcode merged 1 commit intobmad-code-org:mainfrom
alexeyv:feat/findings-triage
Mar 4, 2026
Merged

feat(skills): add bmad-os-findings-triage HITL triage skill#1804
bmadcode merged 1 commit intobmad-code-org:mainfrom
alexeyv:feat/findings-triage

Conversation

@alexeyv
Copy link
Contributor

@alexeyv alexeyv commented Mar 2, 2026

Summary

  • Adds bmad-os-findings-triage skill: team-based HITL triage orchestrator for review findings
  • One Opus agent per finding — researches autonomously, proposes plan, holds for human conversation
  • Team lead orchestrates lifecycle: parsing, task creation, agent spawning, scorecard, cleanup
  • Handles edge cases: wave batching (>25 findings), same-file conflicts, serialization, skip/defer

Files

  • .claude/skills/bmad-os-findings-triage/SKILL.md — registration (7 lines)
  • .claude/skills/bmad-os-findings-triage/prompts/instructions.md — team lead orchestration (287 lines)
  • .claude/skills/bmad-os-findings-triage/prompts/agent-prompt.md — per-finding agent contract (105 lines)

Test plan

  • Invoke skill with a structured findings report file
  • Verify agents spawn in parallel and signal ready
  • Verify HITL conversation flows naturally per finding
  • Verify decisions are recorded and scorecard is accurate
  • Test skip/defer flow
  • Test with >25 findings to verify wave batching prompt

🤖 Generated with Claude Code

@alexeyv alexeyv marked this pull request as ready for review March 2, 2026 18:09
@github-actions
Copy link
Contributor

github-actions bot commented Mar 2, 2026

@coderabbitai review

@augmentcode
Copy link

augmentcode bot commented Mar 2, 2026

🤖 Augment PR Summary

Summary: This PR introduces a new Claude skill, bmad-os-findings-triage, to orchestrate human-in-the-loop (HITL) triage of review findings using a team-lead + per-finding agent pattern.

Changes:

  • Adds skill registration metadata in .claude/skills/bmad-os-findings-triage/SKILL.md
  • Adds a team-lead orchestration prompt that covers input parsing, task creation, team setup, agent spawning, readiness tracking, decision recording, batching for large finding sets, and cleanup
  • Adds a per-finding agent prompt defining a strict lifecycle: autonomous research → visible plan → wait for HITL conversation → report a single final decision
  • Defines a standardized decision taxonomy (FIX/WONTFIX/DISMISS/REJECT/SKIP/DEFER) and a scorecard format for final reporting

Technical Notes: The design emphasizes parallelism (one Opus agent per finding), explicit messaging conventions for readiness/decisions, and safeguards for >25 findings and same-file edit conflicts.

🤖 Was this summary useful? React with 👍 or 👎

Copy link

@augmentcode augmentcode bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review completed. 2 suggestions posted.

Fix All in Augment

Comment augment review to trigger a new review at any time.

@alexeyv
Copy link
Contributor Author

alexeyv commented Mar 3, 2026

@CodeRabbit review

@coderabbitai
Copy link

coderabbitai bot commented Mar 3, 2026

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

Team-based skill that orchestrates human-in-the-loop triage of review
findings using parallel Opus agents. One agent per finding researches
autonomously, proposes a plan, then holds for human conversation before
a decision is recorded. Team lead maintains scorecard and lifecycle.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@alexeyv alexeyv force-pushed the feat/findings-triage branch from ab6e7e7 to bcd1d21 Compare March 3, 2026 08:42
@bmadcode bmadcode merged commit 7ece8b0 into bmad-code-org:main Mar 4, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants