Agent

Scout Phase (RTM Generation)

Generates Forward, Backward, and Bidirectional Requirements Traceability Matrices from execution order, README, work breakdown, and codebase to detect gaps, orphans, and coverage before distributing tasks to agents.

Markdown

code-quality

testing

npx claudepluginhub berrzebb/quorum --plugin quorum

Popularity

Stars

Forks

Behavior

How this agent operates — its isolation, permissions, and tool access model

Agent reference

quorum:agents/knowledge/references/orchestrator/scout

Inline context

Inherits all tools

Requires power tools

Context Preview

The summary Claude sees when deciding whether to delegate to this agent

Before distributing work, dispatch a **scout** to produce a Requirements Traceability Matrix (RTM). The RTM is the **single source of truth** that all agents share. It eliminates redundant exploration. ``` Orchestrator selects track(s) ↓ Scout reads: execution-order → README → work-breakdown → codebase ↓ Produces 3 matrices: Forward RTM   — requirement → code → test (gap detection) Backward RTM...

Agent Content

69 lines · ~550 tokens

Similar Agents

loop-operator

185.1k

Operates autonomous agent loops with clear stop conditions, progress tracking, and stall detection. Intervenes safely when loops stall or fail repeatedly.

5 tools

ecc

Stats

LanguageJavaScript

Stars8

Forks6

MaintenanceExcellent

Last CommitApr 15, 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.

Scout Phase (RTM Generation)

Before distributing work, dispatch a scout to produce a Requirements Traceability Matrix (RTM).

The RTM is the single source of truth that all agents share. It eliminates redundant exploration.

Flow

Orchestrator selects track(s)
    ↓
Scout reads: execution-order → README → work-breakdown → codebase
    ↓
Produces 3 matrices:
  Forward RTM   — requirement → code → test (gap detection)
  Backward RTM  — test → code → requirement (orphan detection)
  Bidirectional — cross-reference summary (coverage analysis)
    ↓
Orchestrator distributes Forward RTM rows to implementers

Procedure

Spawn scout agent — read-only, thorough analysis (Opus):
```
{
  "prompt": "[target tracks + design doc paths]",
  "subagent_type": "scout",
  "description": "scout RTM for [track-name]"
}
```
Scout agent definition: agents/scout.md RTM format: ${QUORUM_ROOT}/platform/core/templates/references/${locale}/traceability-matrix.md
Receive 3 matrices:
- Forward RTM: Req ID × File with Exists/Impl/Test Case/Connected columns
- Backward RTM: Existing tests traced back to requirements (orphan detection)
- Bidirectional summary: Gap analysis
Use Forward RTM to:
- Identify open rows (⬜) → work items to distribute
- Validate non-overlapping file scopes for parallel distribution
- Assign rows to implementers by Req ID grouping
Use Backward RTM to:
- Detect orphan tests/code for cleanup
- Verify connection chains across tracks

RTM Staleness Check

Before distributing from an existing RTM:

Compare work-breakdown.md mtime vs rtm-{domain}.md mtime
If work-breakdown is newer → RTM is stale → re-run scout
If execution-order.md is newer → cross-track connections may be invalid → re-run scout

When to Skip Scout

RTM exists AND work-breakdown.md mtime < RTM mtime (fresh)
Correction round (Forward RTM rows already identified by auditor)
Single-file trivial change

RTM Tools via CLI

quorum tool rtm_parse --path <rtm.md> --status open
quorum tool rtm_merge --base <base.md> --updates '["wt1.md","wt2.md"]'