Results for “task-completion”

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

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

Persists through implement-verify-fix loops until a task is fully completed and verified, overriding default stopping behavior.

Create punch lists for construction completion inspection. TRIGGERS - Use when user needs help with punch-list related tasks.

Create punch lists for construction completion inspection. TRIGGERS - Use when user needs help with punch-list related tasks.

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

Benchmarks mobile GUI agents on multi-step tasks across 20 Android apps, measuring task completion and essential-state navigation with Task Success Rate and Essential State Achieved Rate.

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

Drives a PRD-based persistence loop that iterates on a task until all user stories pass and are reviewer-verified, with automatic retry and progress tracking.

Archives a completed change in the OpenSpec workflow, checking artifact and task completion, assessing spec sync, and moving the change directory.

Makes completion state obvious at the end of every response using a red/yellow/green status block.

Maintains a working memory file for AI agents, tracking active goals, completed tasks, performance metrics, blockers, and key decisions across sessions.

Final completion discipline including summary generation, plan document updates, and confirmation that all success criteria from the original plan are satisfied.

当用户已有确认过的开发任务清单（理想来自 split-task），要把它逐个落地成实现 + 测试 + 提交，并经验收确认真的做完时使用——如"执行任务、把 tasks 做掉、按任务清单开始编码、实现这些任务、推进开发"。不要用于：任务还没拆（先 split-task）、技术方案没定（先 make-design）、行为没钉死（先 write-spec）、想法还模糊（先 refine-idea）、只做单个改动的红绿闭环（那是 tdd）、只做一次代码审查（那是 review-changes）、单纯调试某个 bug、代码评审。

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.

Use when about to claim work is complete, fixed, or passing, before committing, before reporting a task done, or before telling the evaluator the batch is ready. Requires running the verification command and reading its output in this turn before any success claim; evidence before assertions always.

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

Generate one high-value follow-up workflow proposal when MoonMind execution quality issues are detected in a run.

Archives a completed change in the OpenSpec workflow, checking artifact and task completion, assessing spec sync, and moving the change directory to the archive.

issue-start 가 증거와 리포트를 게시하고 사람이 승인한 작업을 마무리합니다. 기존 증거의 완결성과 게시 상태를 확인하고, 부족하거나 바뀐 경우에만 보강·재게시한 뒤 PR 을 만듭니다. merge 는 하지 않고 issue-merge 로 넘깁니다. `$issue-end`, "이슈 마무리", "작업 종료", "승인한 작업 PR" 요청에 사용합니다.

当一段开发完成，要给当前分支 / worktree 收尾时使用——如"收尾、把这个分支收掉、开发完了怎么处理、合并还是留着"。通常由 execute-task 执行完后调用。先只读预检状态，再清除本次开发遗留的调试代码、跑最终测试，然后给出合并/本地保留/创建 PR/丢弃选项；提交、合并、推送、删除与移除工作树都交用户拍板。不要用于：开发还没完、建立工作区（那是 setup-worktree）。

Divide un cambio de diseño aprobado en tareas concretas, ordenadas por dependencias y agrupadas por fase, con criterios de done y un forecast de workload para revisión.

Close an approved plan with zero plan-related deferrals: implement every unfinished item, absorb every connected out-of-scope/follow-up/nice-to-have item parked by prior runs, fix. Use when a plan was marked done with work deferred, or the user says "complete everything", "don't defer", "fix out of scope too", "finish.

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

Commits changes, rebases on main, and creates a pull request to finish a development task.

Task Decomposition

Full autonomous engineering workflow

Use when all plan tasks are done and green to review, archive planning artifacts, and ask how to finish.

Archive completed milestone and prepare for next version

View and manage the task stack and processing queue. Shows pending work, active tasks, completed items, and queue state. Triggers on "/tasks", "show tasks", "what's pending", "task list", "queue status".