AgileFlow

Completeness Consensus Coordinator

PreviousNext

Consensus coordinator for completeness audit - validates findings, votes on confidence, filters by project type, assesses user impact, and generates prioritized Completeness Audit Report

Completeness Consensus Coordinator

The Completeness Consensus Coordinator collects findings from all completeness analyzers, applies intentionality filtering, votes on confidence, classifies user impact, filters by project type, and produces the final prioritized Completeness Audit Report.

When to Use

Use this agent when:

  • You need to consolidate findings from multiple completeness analyzers into one report
  • You want to filter out false positives and intentional patterns (test stubs, abstract methods)
  • You need to classify findings by user impact (blocking, confusing, silent data loss)
  • You want to detect project type and exclude irrelevant findings
  • You need a prioritized "Complete or Remove" checklist

How It Works

  1. Detects project type - Determines if CLI, API-only, SPA, Library, Full-stack, Mobile, or Microservice
  2. Collects findings - Parses all analyzer outputs into normalized structure
  3. Applies intentionality filtering - Excludes test stubs, abstract methods, generated code, extension points
  4. Votes on confidence - Multiple analyzers flagging same issue = higher confidence
  5. Classifies user impact - Categorizes each finding by how it affects end users
  6. Filters by project type - Excludes findings irrelevant to the detected project type
  7. Generates report - Produces prioritized, actionable Completeness Audit Report

Consensus Process

Confidence Voting

ConfidenceCriteriaAction
CONFIRMED2+ analyzers flag same location or related issueHigh priority, include in report
LIKELY1 analyzer with strong evidenceMedium priority, include
INVESTIGATE1 analyzer, weak or circumstantial evidenceLow priority, needs manual review
INTENTIONALAnalyzer flags it but intentionality filter appliesExclude from report with note

User Impact Classification

ImpactDefinitionExamples
user-blockingUser cannot complete a core workflowEmpty form handler, broken checkout, dead navigation
user-confusingUI element exists but does nothingButton with no action, link to nowhere
data-silentData loss happens silentlyState set but never persisted, API response ignored
developer-onlyMaintenance burden, no user-visible impactDead exports, unused dependencies

Priority Matrix

Severity x Confidence determines priority:

CONFIRMEDLIKELYINVESTIGATE
BROKENShip BlockerFix Before ReleaseFix This Sprint
INCOMPLETEFix Before ReleaseFix This SprintBacklog
PLACEHOLDERFix Before ReleaseFix This SprintBacklog
DORMANTFix This SprintBacklogInfo

Project Type Filtering

Project TypeIrrelevant Findings
CLIDead UI handlers, dead routes, unused React state
API-onlyEmpty onClick, dead navigation links, unused React state
SPAOrphaned backend endpoints, server-side stubs
LibraryDead routes, API mismatches (but dead exports are HIGHER severity)
Full-stackNone excluded - all findings potentially relevant

Tools Available

This agent has access to: Read, Write, Edit, Glob, Grep

Output Format

The final Completeness Audit Report includes:

  • Summary: Counts by severity with user impact categories
  • Ship Blockers: BROKEN + CONFIRMED findings to fix immediately
  • Fix Before Release: High-priority incomplete features
  • Fix This Sprint: Medium-priority items
  • Backlog/Info: Low-priority dormant code
  • Intentional Exclusions: Findings excluded with reasoning
  • Analyzer Agreement Matrix: Which analyzers flagged which locations
  • Complete or Remove Checklist: Actionable items with both remediation paths

Example Usage

Task(
  description: "Run completeness audit consensus",
  prompt: "Consolidate findings from all 7 completeness analyzers. Detect project type, apply intentionality filtering, vote on confidence, classify user impact, and generate the prioritized Completeness Audit Report.",
  subagent_type: "agileflow-completeness-consensus"
)

Related Agents