work_skill

Overview

This skill automates implementing tasks listed in Plans.md based on a user-specified scope. It asks for scope when invoked without arguments, then selects an execution strategy automatically and runs implementations, reviews, and optional commits. It supports single-task direct coding, parallel workers for multiple tasks, and iterative loops for large batches.

How this skill works

When triggered it inspects Plans.md to identify target tasks and chooses a strategy by task count and independence. For one task it implements directly; for a few tasks it spawns parallel task-workers; for many or "all" it runs parallel workers plus auto-iteration until tasks pass build/test/review or reach iteration limits. After implementation it runs review cycles and can auto-commit unless suppressed.

When to use it

• User types /work or variants (e.g., /work 3, /work all, /work 3-6).
• You want code implemented from Plans.md without manual orchestration.
• You need single-task quick fixes, multi-task parallel work, or full-batch iterative completion.
• When you want integrated review loops and optional auto-commit.
• Invoke with --codex to delegate implementation to Codex MCP.

Best practices

• Specify a clear scope when possible (task number, range, or all) to avoid interactive prompts.
• Use --no-commit in experimental sessions to prevent automatic commits.
• For independent changes, allow parallel workers to speed completion; limit parallelism for edits to the same file.
• Set --max-iterations for very large batches to bound automatic retries.
• Use --codex only when you want external engine execution and stricter guard behavior.

Example use cases

• /work to implement the next pending task and commit the change.
• /work 3-5 to implement a small group of related tasks in parallel and run a review loop.
• /work all to iterate until all Plans.md tasks are cc:done, tests pass, and reviews approve.
• /work --codex all to delegate implementation to Codex MCP while the harness manages review and quality gates.
• /work --no-commit during a dry run or exploratory coding session.