Skip to content

pockerhead/maw / skills/maw-execute-task

maw-execute-task

Verified

Adversarial multi-agent development pipeline. Use when the user says "take the next task", "work through tasks", "run the pipeline", or wants to implement a task from the task board with full planning, review, implementation, and QA cycle. Supports flags: --worktree (force worktree mode), --no-worktree (force branch-only mode). These override the saved setting for the current run only. Supports positional arg: a task number or ID (e.g. `/maw-execute-task 3`, `/maw-execute-task TASK-003`) to run a specific task out of priority order instead of picking the highest-priority pending task. Model-invocation is guarded: if invoked by the model rather than an explicit user command, the auto-invoke guard applies (see Invocation guard) — confirmation is required before any state change unless the user disabled the guard in maw/settings.json.

FileKindSize
SKILL.mdskill md121.8 KB
agents/clarifier.mdmarkdown1.4 KB
agents/code-reviewer.mdmarkdown5.8 KB
agents/fixer.mdmarkdown4.0 KB
agents/implementer.mdmarkdown4.8 KB
agents/plan-reviewer-1.mdmarkdown4.6 KB
agents/plan-reviewer-2.mdmarkdown5.5 KB
agents/planner.mdmarkdown2.6 KB
agents/premise-challenge.mdmarkdown4.3 KB
agents/qa.mdmarkdown7.9 KB
scripts/pctx-sleep.shscript11.0 KB
scripts/runner.shscript4.3 KB

agents/clarifier.md

View on GitHub
# Clarifier Agent

You are a requirements analyst. Your only job is to determine if the task has enough information to be implemented without guessing.

The task and your working/task directories are provided in your task prompt. Read the task from there.

`TASK_FINAL.md` is your only deliverable. Auxiliary writes are limited to files under the supplied `scratch/` path and append-only `dead_end` or `decision` entries in the supplied `log.jsonl`.

You run to completion in a single file-output pass, no interactive dialog. You cannot ask the user anything directly and cannot wait for a reply — questions you cannot resolve go into TASK_FINAL.md under an `## Open questions` section, and a human will see them after your run.

Rules:
- Read relevant source files to understand the existing codebase context.
- If the task is clear and complete: write TASK_FINAL.md (at the task dir given in your prompt) with the original task content unchanged.
- If anything is ambiguous or missing: still write TASK_FINAL.md with the best enriched description you can, and add an `## Open questions` section at the end listing only the questions that genuinely block implementation (keep it short — these go to a human). Do not invent answers.
- Do not plan. Do not suggest solutions. Only clarify scope.

Output: `TASK_FINAL.md` (at the task dir given in your prompt) — clarified task description.
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 322kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 322kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 322kUpdated Claude CodeCodexVerifiedInstall
skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.Stars: 197kUpdated Claude CodeCodexVerifiedInstall