pipeline-builder
Use this agent when generating or updating the acceptance test generator for a project, or when the user asks to "build the pipeline", "generate the test…
An agent is a specialist Claude hands a whole job to, with its own tools and its own context.
33 agents across 226 plugins.
Use this agent when generating or updating the acceptance test generator for a project, or when the user asks to "build the pipeline", "generate the test…
Use this agent when reviewing GWT acceptance test specs for implementation leakage, or when the user asks to "check specs", "review specs", "audit specs",…
You are the **Baseline Solution Generator** in a Software Engineering Chain of Verification (SE-CoVe) system.
You are the **Independent Verification Executor** in a Software Engineering Chain of Verification (SE-CoVe) system.
You are the **Verification Task Planner** in a Software Engineering Chain of Verification (SE-CoVe) system.
Test-first coding agent. Use in Step 2 of the development workflow after the plan file is ready. Receives the plan file path, implements test code from the…
Duplicate test removal agent. Use in Step 4 (Refactoring) of the development workflow. Receives the list of test files added or modified in the current…
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is…
This agent is no longer used. All orchestration logic lives in `commands/haunt-test.md` so that output renders at the command level (visible) rather than…
You are a sub-agent that tests one specific page as a given persona. You are spawned in parallel with other page-tester agents.
This agent is no longer used. Report generation is inlined into `commands/haunt-test.md` so there is no sub-agent bubble. The Write tool is called directly…
Converts test scenarios into executable Playwright, Cypress, or Gherkin test code
Validates test scenarios against a running application using Chrome MCP — navigates, interacts, and verifies in a real browser
Use this agent when qa-output/functional-review.md or qa-output/browser-validation.md reports any gap, failed scenario, or blocked verdict. Turns each finding…
Autonomously author NEW verifiable stateful code from a feature description — draft a contract, author a SAM v2 strict-profile module (--legacy-bare-next for…
Autonomously prepare an invariant-elicitation session — harvest candidate invariants from the contract vocabulary, traces, and snapshots, pre-check each…
Autonomously check whether a state-machine version change is safe against the live fleet — classify it into compatibility lanes, run the mechanical gates…
You are the **Final Solution Synthesizer** in a Software Engineering Chain of Verification (SE-CoVe) system.
Checks out PR branches, runs setup commands, and starts the application locally for live testing
Compares code diff against acceptance criteria to find functional gaps, regression risks, and missing edge cases
Guides manual test execution scenario by scenario and produces a structured validation report
Autonomously run the Polygraph verification loop (default artifact SAM v2 strict-profile; --legacy-bare-next for the legacy bare-next contract) given a…
Routes QA tickets to the right agents in the right order — including environment setup and live browser validation
Analyzes a multi-repo release diff to map cross-repo impact, AC compliance, and deployment risks
Maps code changes to existing tests — finds which tests to run, which may break, and where coverage gaps exist
Generates comprehensive test scenarios from acceptance criteria (happy path, negative, boundary, edge cases)
© 2026 Flowy · Free and open source
Built for Claude Code · Not affiliated with Anthropic