workflow-manager

Set autonomy level (off, ask, auto) — controls how much Claude decides independently

Validate outcomes, commit, audit tech debt, and save handover

Toggle debug mode — control WFM observability level

Define the problem and outcomes

Design the solution and select the approach

Execute the approved plan with TDD and code edits enabled

Read an observation by ID from claude-mem

Track an observation ID in the workflow status line

Stop tracking an observation ID in the workflow status line

Close the workflow and disable phase enforcement

Manage workflow improvement proposals from claude-mem

Run review pipeline on changed files

Reviews code changes for architectural issues and plan compliance. Use during the REVIEW phase. Requires plan file path as context.

Counterevidence finder and edge case analyst. Use during DEFINE phase diverge step to challenge problem framing assumptions.

Tests edge cases and boundary conditions the plan didn't specify. Use in COMPLETE phase Step 2, parallel with outcome-validator and devils-advocate.

Reviews code changes for quality issues. Use when reviewing changed files during the REVIEW phase.

Explores current architecture, integration points, and dependency graph to determine which approaches fit. Use during DISCUSS phase converge step.

Scans for dead code, obsolete tests, orphaned files, and structural drift. Reports findings as tech debt for future sessions. Use during the REVIEW phase alongside other reviewers.

Verifies commit message quality and completeness. Use in COMPLETE phase Step 5 review gate.

Project history searcher for prior discussions, decisions, and failed attempts. Use during DEFINE phase diverge step.

Adversarial tester that attempts to break the implementation through attack vectors. Use in COMPLETE phase Step 2, parallel with outcome-validator and boundary-tester.

Analyzes changed files and recommends documentation updates. Use in COMPLETE phase Step 4.

Verifies documentation detection completeness. Use in COMPLETE phase Step 4 review gate.

Web search specialist for problem domain context. Use during DEFINE phase diverge step to research similar pain points, industry context, and standards.

Reviews code changes for production readiness, secrets hygiene, permissions, repo organization, pattern consistency, and compliance posture. Use during the REVIEW phase alongside code quality, security, and architecture reviewers.

Verifies handover observation quality for next session usability. Use in COMPLETE phase Step 8 review gate.

Prepares comprehensive claude-mem handover observation documenting what was built, decisions made, and work remaining. Use in COMPLETE phase Step 8.

Structures measurable outcomes with verification methods and acceptance criteria. Use during DEFINE phase converge step.

Validates success metrics and acceptance criteria from the decision record with behavioral evidence. Use in COMPLETE phase Step 2.

Validates implementation plan deliverables by classifying each as structural or behavioral and exercising behavioral ones. Use in COMPLETE phase Step 1.

Searches project history and codebase for previous related implementations or decisions. Use during DISCUSS phase diverge step.

Verifies validation result presentation quality — ensures every deliverable and outcome has individual evidence rows, not compressed summaries. Use in COMPLETE phase Step 3 review gate.

Verifies review findings from other agents by checking actual code, filtering false positives. Use after review agents return findings in the REVIEW phase.

Analyzes risks and implications of each shortlisted approach. Use during DISCUSS phase converge step.

Identifies scope boundaries, hidden dependencies, and constraints. Use during DEFINE phase converge step.

Reviews code changes for security vulnerabilities including OWASP Top 10, secret detection, and injection vectors. Use during the REVIEW phase.

Web search specialist for technical approaches, libraries, and implementation patterns. Use during DISCUSS phase diverge step.

Web search specialist for case studies, lessons learned, and how others solved similar problems. Use during DISCUSS phase diverge step.

Verifies tech debt audit quality — ensures every trade-off is addressed with concrete fix proposals. Use in COMPLETE phase Step 7 review gate.

Determines semantic version bump based on change analysis. Use in IMPLEMENT phase step 4b.

4 hooks across 3 events