Results for “plan-verification”

Coordinates multi-phase problem-solving workflows with structured task tracking and verification.

Plan structure validation, phase completeness checks, reference integrity verification, and artifact existence confirmation. Provides the structured verification layer ensuring GSD artifacts are well-formed and complete.

Executes approved Flow plans one atomic task at a time with test-first implementation, fresh verification, blocker handling, and durable evidence.

Executes a written implementation plan task-by-task with verification, review checkpoints, and sub-skill handoffs.

Turns a mature product plan into a rough implementation plan with high-level steps, maturity and verification marks, and a risks section.

Executes a written implementation plan via per-batch sub-agent coordinators with verification and commits between batches.

Generates complete, copy-paste ready implementation documentation from a PR plan, including code blocks and verification checklists.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Verifies each step of a rough implementation plan against source code and current documentation, attaching proof and marking steps as verified or unverified.

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Structured task planning with clear breakdowns, dependencies, and verification criteria. Use when implementing features, refactoring, or any multi-step work.

Compare, cross-review, and merge competing plans from multiple agents into one executable direction with a clear handoff.

Guides CAPA effectiveness assessment with verification methods, SMART criteria, and closure requirements.

Verification-before-completion discipline ensuring all success criteria are met, tests pass, and reviews complete before declaring work done.

Claude Code 会话的全面验证系统。

Verify tasks marked [X] in tasks.md are implemented, not phantom completions (marked done but backed by missing or dead code).

Build a compact, validation-gated implementation plan for multi-step, risky, or ambiguous work — typically when phases need explicit checkpoints, the change touches multiple files/services, or the user wants alignment before execution. Output goes to `.claude/plans/<topic>.md` (or `.agents/plans/`) with goal, in/out-of-scope, phased steps, validation per phase, and replanning triggers. Skip for trivial single-file fixes, bug investigations (use `tracer`), or open-ended exploration (use `explore`). Pair with `ship` once the plan ends and merge work begins.

Verify implemented work meets acceptance criteria — run tests, check PHPCS, validate Blade output, lando phpunit, lando phpcs, lando yarn test, Playwright tests, accessibility check, post-implementation verification, done criteria validation, checklist review, verification phase

Runs a multi-phase verification pipeline including build, type-check, lint, tests, security scan, and diff review to ensure code quality before creating a PR.

Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md. Identifying inconsistencies, duplications, ambiguities, and underspecified items.

A comprehensive verification system for Claude Code sessions.

Loads an implementation plan, reviews it critically, executes each task with verification, and reports completion, stopping to ask for help when blocked.

Perform a non-destructive post-implementation verification gate validating the implementation against spec.md, plan.md, tasks.md, and constitution.md.

Verify feature, bug, UI, API, mobile, security, or deployment work against acceptance criteria.

Use this when the system needs explicit runtime validation for API inputs, config, queue messages, webhook payloads, file metadata, or external provider responses in TypeScript, JavaScript, Python, or mixed systems.

Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.

Verifica la reproducibilidad y consistencia de un análisis de datos antes de presentarlo, validando contra la pregunta original y documentando limitaciones.

Verifies data structures, files, YAML blocks, or agent output against their defined schema, producing a pass/fail report with actionable fix instructions.