plan-work
Explicit-only. Produce and review an implementation-ready plan from a task source.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Explicit-only. Produce and review an implementation-ready plan from a task source.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Explicit-only. Run a named autonomous mode, repeatedly selecting, implementing, and shipping coherent work while preserving anything blocked.
Use globally installed `playwright-cli` for browser automation, UI inspection, screenshots, Playwright test debugging, or test generation. Trigger when a task needs browser interaction or test repair. Do not use for generic tests, web search, non-browser docs, or API-only work.
Explicit-only. Align a feature specification, produce a reviewed plan, complete the local work, and ship the pull request.
Explicit-only. Review a plan/task/context artifact set and report material findings.
Explicit-only. Ship one pull request, observe hosted CI and review feedback, follow PR policy, reply to every eligible comment, and request merge authorization before merging and cleaning up.
Explicit-only. Verify completed work against its authoritative contract and report coverage, working-code evidence, material gaps, and the completion verdict.
| name | plan-work |
| description | Explicit-only. Produce and review an implementation-ready plan from a task source. |
Create a reviewed, implementation-ready plan, task list, and context artifact.
Require a task source or user request and one or more self-contained
plan_reviewers target specifications. Resolve each through /agent-dispatch's
live metadata; use an unambiguous match without confirmation. Missing task
input, an empty reviewer list, or an unresolved reviewer blocks planning;
create nothing.
references/write-plan.md. Correct evidence-backed gaps within this
stage. Ask the user only when a substantive choice cannot be resolved under
repository escalation rules./review-plan. Give each
the complete artifacts and optional source/spec..agent-layer/tmp/plan-work.<run-id>.report.md using the plan artifact
run ID. Include reviewer finding paths, dispositions, rejection reasons,
unresolved decisions, and status.Return the plan, task, context, and report paths with one status:
implementation-ready: accepted findings are addressedblocked-for-user-decision: name the unresolved substantive decision