Implements a single task following the next → implement → check → done workflow with TDD support. Use when working on one specific task, implementing a single feature from the backlog, or following TDD red-green-refactor cycle. Triggers on 'next task', 'next feature', 'implement feature', 'work on feature', 'single task mode', 'what should I work on'.
/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.
One command: agent-foreman next
You MUST follow this exact sequence. 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 |
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 index.json for TDD mode | Check CLI output for !!! TDD ENFORCEMENT ACTIVE !!! |
| Edit task files to change status | Use agent-foreman done/fail |
Allowed: Reading task .md files for acceptance criteria AFTER running agent-foreman next.
agent-foreman next # Auto-select next priority
agent-foreman next auth.login # Specific task
next → implement → check → done
agent-foreman next # 1. Get task + acceptance criteria
# ... implement the task ... # 2. Write code
agent-foreman check <id> # 3. Verify implementation
agent-foreman done <id> # 4. Mark complete + commit
Look for "!!! TDD ENFORCEMENT ACTIVE !!!" in agent-foreman next output.
# STEP 1: Get task + TDD guidance
agent-foreman next <task_id>
# STEP 2: RED - Write failing tests FIRST
# Create test file at suggested path
# Run tests: <your-test-command>
# Verify tests FAIL (confirms tests are valid)
# STEP 3: GREEN - Implement minimum code
# Write minimum code to pass tests
# Run tests: <your-test-command>
# Verify tests PASS
# STEP 4: REFACTOR - Clean up
# Clean up code while keeping tests passing
# STEP 5: Verify + Complete
agent-foreman check <task_id>
agent-foreman done <task_id>
CRITICAL: DO NOT write implementation code before tests exist in strict TDD mode!
needs_review → may be brokenfailing → not implementedpriority number → higher priority (0 is highest)When next shows "VALIDATION PHASE REMINDER":
# All BREAKDOWNs complete → Run validation FIRST
agent-foreman validate
# Then proceed with implementation
agent-foreman next
ALWAYS run done after completing each task (including BREAKDOWN tasks).
| Flag | Effect |
|---|---|
--check | Run tests before showing task |
--dry-run | Preview without changes |
--json | Output as JSON for scripting |
--quiet | Suppress decorative output |
--allow-dirty | Allow with uncommitted changes |
--refresh-guidance | Force regenerate TDD guidance |
agent-foreman done <id> # Mark complete + commit
agent-foreman done <id> --full # Run all tests
agent-foreman done <id> --skip-e2e # Skip E2E tests
agent-foreman done <id> --no-commit # Manual commit
This 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.