Results for “plan-verification”

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.

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

Guides multi-step tasks by decomposing them into checkpoints, verifying results with concrete observations, and re-planning after surprises or failures.

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.

Guides a structured feature-development workflow: explore the codebase with subagents, draft a plan for approval, implement step by step, verify with parallel checks, and record conventions.

Use when planning a CAV (Computer Aided Verification) project timeline from venue and category selection through submission, the two-stage review with early reject and rebuttal, artifact evaluation by the AEC, and the LNCS open-access camera-ready, with backward-planning offsets for a verification-tool paper and honest handling of the single-annual-deadline cycle.

Structured workflow to reproduce, diagnose, plan, fix, verify, and record a bug fix, requiring a deterministic reproduction before diagnosis and minimal changes only.

Implements a structured problem-solving algorithm that guides every response through observe, think, plan, build, execute, verify, and learn phases toward a defined ideal state.

Detects the current state of an Open-workspace project and advances to the next logical workflow step, from discussion through planning, execution, verification, and completion.

Use when planning a COLT (Conference on Learning Theory) submission calendar backward from the single AoE paper deadline — proof-completion and verification milestones, writing and appendix-assembly passes, CMT logistics, the rebuttal window, decision aftermath, and PMLR camera-ready with conference presentation in early summer.

Orchestrate the full MoonSpec lifecycle from a preselected single-story feature request or active feature directory through specification, planning, TDD task generation, artifact alignment, implementation, and final verification. Use when the user asks for an end-to-end MoonSpec run and the input has already been routed to one independently testable story, or when Codex needs to coordinate `moonspec-specify`, `moonspec-plan`, `moonspec-tasks`, `moonspec-align`, `moonspec-implement`, and `moonspec-verify` without manual analyze/remediation prompts.