Results for “plan-verification”

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

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

Loads a written implementation plan, reviews it critically, executes all tasks with verification, and reports completion, stopping to ask for help when blocked.

Creates a concrete, multi-phase plan before starting a multi-file refactor, including affected files, dependencies, verification steps, and rollback procedures.

Autonomously repairs failed task verification by choosing retry, decompose, prune, or escalate strategies before surfacing to the user.

Guide a structural migration or dependency upgrade with a step-by-step plan and verification

Executes a written implementation plan in a separate session, reviewing it critically, running tasks with verification, and stopping to ask for help when blocked.

Generate comprehensive rollout plans with preflight checks, step-by-step deployment, verification signals, rollback procedures, and communication plans for infrastructure and application changes.

Delivers a small, bounded code change through inspection, a mini-plan, implementation, testing, review, and adversarial verification. Use for bug fixes, configuration changes, and features expected to touch no more than five files.

Autonomously implements large Elixir/Phoenix features end-to-end: discovers complexity, plans with specialist agents, implements with verification, reviews code, and cycles back on issues.

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

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

Repairs failed task verification by choosing a strategy: retry with adjustments, decompose into sub-tasks, prune infeasible tasks, or escalate to the user.

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.

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.

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

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

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

Scaffolds a per-task verification skill for a repo, including a dev-local launcher, a browser driver, and a verification SOP that spawns a sub-agent to drive the app and produce proof.

Verify that a change really works before you claim completion

Plan a multi-file refactor with proper sequencing and rollback steps

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

Combined verification — recite (description quality via cold-read prediction) + validate (schema compliance) + review (health checks). Use as a quality gate after creating notes or as periodic maintenance. Triggers on "/verify", "/verify [note]", "verify note quality", "check note health".

Verify code changes work by running them. Proves through execution, not just inspection.

Executes small ad-hoc tasks with GSD guarantees, spawning planner and executor agents, tracking tasks in .planning/quick/, and updating STATE.md. Supports composable flags for discussion, research, plan-checking, and verification.