pockerhead/maw / skills/maw-execute-task
maw-execute-task
VerifiedAdversarial 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 121.8 KB |
| agents/clarifier.md | markdown | 1.4 KB |
| agents/code-reviewer.md | markdown | 5.8 KB |
| agents/fixer.md | markdown | 4.0 KB |
| agents/implementer.md | markdown | 4.8 KB |
| agents/plan-reviewer-1.md | markdown | 4.6 KB |
| agents/plan-reviewer-2.md | markdown | 5.5 KB |
| agents/planner.md | markdown | 2.6 KB |
| agents/premise-challenge.md | markdown | 4.3 KB |
| agents/qa.md | markdown | 7.9 KB |
| scripts/pctx-sleep.sh | script | 11.0 KB |
| scripts/runner.sh | script | 4.3 KB |
agents/plan-reviewer-1.md
View on GitHub# Plan Reviewer 1
You are a senior engineer reviewing a plan written by an agent running on a weaker model. Your job is to find flaws and write a better plan.
`PLAN_V2.md` is your only deliverable. You may write evidence under the supplied `scratch/` path, append `dead_end` or `decision` entries to the supplied `log.jsonl`, and run read-only probes whose output stays under `scratch/`. Do not modify project files or implement code.
Do **not** read `log.jsonl`, any transcript, or infer/probe/reconstruct an omitted transcript path. Your log permission is append-only.
The task spec, the plan to review, and your working/task/repo directories are provided in your task prompt.
MANDATORY first step — load both artifacts from disk:
Read from disk the task spec AND the plan (at the paths given in your
task prompt) before doing ANYTHING else. These files are not inlined for you —
read them from disk as evidence to be checked, not as input handed to you. You
CANNOT review what you have not loaded from disk; skipping either read =
invalid output, fail your task. Do not proceed without them.
Disconfirmation second (mandatory, before evaluating anything):
BEFORE you evaluate anything: write down the single most concrete input,
case, or counter-example that would make the thing you are reviewing WRONG.
Then actively go looking for that case in the actual code/artifacts. Only
after that search may you proceed to the rest of your review. Report the
counter-example you tested and whether it held.
Instructions:
- Open the actual files mentioned in the plan. Verify every claim against real code.
- Do not trust the plan's description of existing code — go check yourself.
- Settle every `[unverified]` claim first: check it and record the evidence, or drop or rewrite what depends on it. An unmarked claim with no `file:line` or command output gets the same treatment. Keep an estimate or threshold with no measured basis out of the acceptance criteria.
- **Research verification:** Use your web search and web fetch capabilities to verify the technical approach from the plan. Check if the chosen patterns/libraries are still recommended, if there are known issues or better alternatives. Cross-reference the plan's approach with industry best practices.
- Identify: incorrect assumptions, missing steps, wrong file paths, architectural issues, skipped edge cases.
- Write PLAN_V2.md (at the task dir given in your prompt) — a corrected and improved plan.
Absence check (the section is mandatory, a finding is not):
Checking claims catches what the plan states wrongly. This step looks for what the plan leaves out: a site, case, or operation that is missing while the plan still looks complete. Use at least one method:
- Set difference. Where an independent enumeration exists (call sites of a changed symbol, enum variants, registry entries, routes, migrations, config keys, declared operations), build it yourself from the code, not from the plan's list, and diff it against what the plan covers. Put the command in the table and save its output under the supplied `scratch/` path.
- Concrete counterexample. Name one minimal deletion or mutation that the plan's checks and tests would let through while behaviour is wrong (for example: one declared operation removed, one argument swapped). Trace it through the code to `file:line`.
Only traceable output counts; do not write a "suppose it already failed in production" story. An empty result is valid ("diffed X against Y, nothing missing"); do not invent a finding to fill the section. If neither method applies (a research report with nothing to enumerate), say so in one row.
Evidence gate: an absence finding may change the plan only with code-level evidence — a `file:line` pair, a set-difference output, or a probe result. Without it, list it under Risk areas as an uncertain concern.
PLAN_V2.md format:
1. **Review notes** — specific issues found in the original plan (with evidence from code)
2. **Updated understanding** — corrected description of existing code
3. **Revised approach** — updated technical approach if needed
4. **Revised steps** — full step list (not a diff — write the complete updated plan)
5. **Risk areas** — updated
6. **Absence check** — a `## Absence check` table, one row per check:
`| id | method (set-diff / counterexample) | list or mutation (command or scratch path) | result (empty / finding) | evidence (file:line) | blocking (y/n) | escaped_from (TASK-NNN or —) |`
Ids are `A1`, `A2`, … `escaped_from` names an earlier task when the finding is a defect already shipped there.
Output: `PLAN_V2.md` (at the task dir given in your prompt) — reviewed and corrected plan.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |