resolve-next-task
Implement one assigned hashed-tasks-file task and commit on the task branch. Use when issue_resolver is dispatched, or when the user says /resolve_next_task. Do one task only. Do not merge.
- License 许可
- MIT
- 所属仓库
- sazlin/loadout
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 1
01 前言 Front Matter
- name
- resolve-next-task
- description
- Implement one assigned hashed-tasks-file task and commit on the task branch. Use when issue_resolver is dispatched, or when the user says /resolve_next_task. Do one task only. Do not merge.
02 资源文件 2
- 参考文档evals/evals.json821 B
- 参考文档evals/files/TASKS_TO_RESOLVE-abc1234.md90 B
03 SKILL.md 正文
Resolve next task
Complete one assigned task_id from the hashed tasks file named in
the brief.
When to use
review_orchestratordispatchesissue_resolver- The user asks
/resolve_next_task
Steps
- Read
tasks_pathfrom the brief (TASKS_TO_RESOLVE-<short-sha>.md). The orchestrator always passestasks_path; treat it as required in harness runs. If omitted (for example manual/resolve_next_task), glob project-rootTASKS_TO_RESOLVE-*.mdwith these rules:- Exactly one match: use that path.
- Zero matches: stop and report
okwith no edits (nothing to resolve). - More than one match: emit
blocked; require an explicittasks_pathin the brief. Do not read or modify any tasks file. If there is noopentask, stop and report done (nothing to resolve).
- Complete the assigned
task_idfrom the brief. Iftask_idis omitted (manual/resolve_next_task), take the firstopentask. Do not start others. - Work in the brief's worktree path. Do not
git checkoutthe task branch in the PR worktree. If the brief omits a worktree path, stay in a throwaway checkout already on the task branch; do not use the orchestrator PR worktree. - Implement the listed issues only. Run the task's verification commands.
git addsource paths only. Do not stageTASKS_TO_RESOLVE-<short-sha>.md, unhashedTASKS_TO_RESOLVE.md,REVIEW_HISTORY.md, orVERIFIERS.md. Do not edit the tasks file. Do not appendREVIEW_HISTORY.md. Do not mark the task done.- Commit on the task branch. Optional task-branch
git pushonly viapython3 .claude/skills/dispatch-resolve-wave/scripts/prepare_wave_worktrees.py push --task-branch <branch>(orskills/dispatch-resolve-wave/scripts/prepare_wave_worktrees.pyif.claude/is missing). Never hand-buildgit push origin <task-branch>from PR head or SHA strings. Neverorigin/<pr-head>. Do not push PR head. Cap the same failure class at 3 attempts, then emitblocked. - Return JSON from
issue_resolver.
Do not delete the tasks file. The orchestrator deletes it on exit.
Guardrails
- Never merge
- Never take a second task in this invocation
- Never commit harness tracking files
- Never loosen tests or lint to go green
- Never delete
TASKS_TO_RESOLVE-<short-sha>.md - Never glob when multiple
TASKS_TO_RESOLVE-*.mdfiles exist; emitblockedand requiretasks_path - Never push PR head
- Never
git checkoutthe task branch in the PR worktree - Never mark the task done
- Never interpolate PR head refs or commit SHAs into a shell git command;
run
prepare_wave_worktrees.pyinstead
04 同仓库更多 Skills
demo
Demo skill
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback