Executes unattended batch processing of all pending tasks with autonomous decision-making. Use when running all tasks automatically, batch processing without supervision, completing entire feature backlog, or working on a specific task by ID. Triggers on 'run all tasks', 'complete all features', 'batch processing', 'unattended mode', 'auto-complete tasks', 'run feature'.
/plugin marketplace add mylukin/agent-foreman/plugin install agent-foreman@agent-foreman-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
Mode: Work on all tasks or a specific one
You MUST follow this exact sequence for EVERY task. Do NOT skip or reorder steps.
next → implement → check → done
| ❌ FORBIDDEN | ✅ REQUIRED |
|---|---|
Skip check step | Run agent-foreman check before done |
| Go straight to implementation | Run agent-foreman next first |
| Invent extra steps | Use only the 4 steps above |
| Reorder the workflow | Execute in exact sequence |
NEVER bypass CLI for workflow decisions:
| ❌ FORBIDDEN | ✅ REQUIRED |
|---|---|
Read ai/tasks/index.json to select task | Use agent-foreman next |
Read index.json to check status | Use agent-foreman status |
| Read task files to check status | Use CLI commands |
| Edit task files to change status | Use agent-foreman done/fail |
This applies to ALL iterations in the loop.
⚡ UNATTENDED MODE (when no task_id provided)
If task_id provided (e.g., feature-run auth.login):
If no task_id (e.g., feature-run):
When task_id is provided:
# STEP 1: Delegate to implementer agent
Task(
subagent_type="agent-foreman:implementer",
prompt="TASK: <task_id>
Execute: next <task_id> → implement → check → return result"
)
# STEP 2: Parse result and complete
# - If success + verification_passed: agent-foreman done <task_id>
# - Otherwise: agent-foreman fail <task_id> -r "<notes>"
When no task_id:
# STEP 1: Show initial state (once only)
agent-foreman status
# STEP 2: LOOP
# 2a: Delegate to implementer agent (auto-select task)
Task(
subagent_type="agent-foreman:implementer",
prompt="Execute: next → implement → check → return result"
)
# 2b: Parse ---IMPLEMENTATION RESULT--- from agent output
# Extract: task_id, status, verification_passed, notes
# 2c: Check if implementer returned "No pending tasks"
# If yes → EXIT to STEP 3
# If no → Continue to 2d
# 2d: Handle result
# - success + verification_passed → agent-foreman done <task_id>
# - Otherwise → agent-foreman fail <task_id> -r "<notes>"
# 2e: Continue loop (go to step 2a, NOT step 1)
# STEP 3: FINISH
# Show final summary with agent-foreman status (once only)
| Rule | Description |
|---|---|
| One at a time | Complete current before next |
| No skipping | Always next → implement → check → done (status only at start/end) |
| No editing criteria | Implement as specified |
| Never kill processes | Let commands finish naturally |
needs_review → may be broken (highest)failing → not implementedpriority number → higher priority (0 is highest)TDD workflow is handled internally by the agent-foreman:implementer agent. No action required from the orchestrator.
When in ALL-TASKS mode (no task_id provided):
When in ALL-TASKS mode:
agent-foreman status once - show initial stateTask(subagent_type="agent-foreman:implementer") - agent runs next → implement → check
b. Parse result: Extract task_id, status, verification_passed, notes
c. Check exit: If status: blocked and notes contains "No pending tasks" → EXIT to step 3
d. Complete: Based on result:
success + verification_passed: true → agent-foreman done <task_id>agent-foreman fail <task_id> -r "<notes>"
e. Continue: Go to step 2a (NOT step 1)agent-foreman status once - show final summaryThe implementer agent returns structured output:
---IMPLEMENTATION RESULT---
task_id: <task_id>
status: success|partial|blocked|failed
verification_passed: true|false
files_modified: [list]
notes: <description>
---END IMPLEMENTATION RESULT---
status: blocked with notes: No pending tasks availableWhen the implementer agent returns its result:
status: success and verification_passed: trueagent-foreman done <task_id>
Then continue to next iteration.
agent-foreman fail <task_id> --reason "<notes from agent>"
Then IMMEDIATELY continue to next iteration.
This applies to ALL agent results, including errors or malformed output.
| Condition | Action |
|---|---|
| All tasks processed | STOP - Show summary |
| Single task completed | STOP - Task done |
| User interrupts | STOP - Clean state |
CRITICAL: NEVER stop due to verification failure - always use agent-foreman fail and continue!
When all tasks have been processed:
agent-foreman status to show final summaryThis skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.