plan-correspondence-verifier
byblockscout· 2 subagents
Use to verify that ONE phase of a structured implementation plan was implemented completely and honestly. Invoked by the implement-plan orchestrator after a phase-developer finishes a phase (and after each fix round).
How to install plan-correspondence-verifier?
blockscout/mcp-server/plan-correspondence-verifier
$curl -o .claude/agents/plan-correspondence-verifier.md https://raw.githubusercontent.com/blockscout/mcp-server/HEAD/.claude/agents/plan-correspondence-verifier.mdInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Install plan-correspondence-verifier by running `curl -o .claude/agents/plan-correspondence-verifier.md https://raw.githubusercontent.com/blockscout/mcp-server/HEAD/.claude/agents/plan-correspondence-verifier.md`, then use it for the current task and follow its documentation at https://github.com/blockscout/mcp-server.
Related
6 picksType
- code-reviewerSenior code reviewer that evaluates changes across five dimensions — correctness, readability, architecture, security, and performance. Use for thorough code review before merge.Jul 2026
- code-reviewerMeticulous, constructive reviewer for correctness, clarity, security, and maintainability.Jul 2026
- code-reviewerExpert code review specialist with severity-rated feedback, logic defect detection, SOLID principle checks, style, performance, and quality strategyJul 2026
- code-simplifierSimplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.Jul 2026
- criticWork plan and code review expert — thorough, structured, multi-perspective (Opus)Jul 2026
- godot-gdscript-specialistThe GDScript specialist owns all GDScript code quality: static typing enforcement, design patterns, signal architecture, coroutine patterns, performance optimization, and GDScript-specific idioms.…May 2026
