Implement
ericrisco/rsc-harness
A skill your agent uses when an approved plan and task list exist and it is time to turn them into working, tested code — the SDD phase after analyze and before verify.
Enforces a strict next-implement-check-done cycle through the agent-foreman CLI so an agent works one backlog task at a time, with optional TDD gating.
Install Feature Next Task Workflow
$ npx skills add mylukin/agent-foreman --skill feature-next -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install mylukin/agent-foreman feature-next --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/mylukin/agent-foreman.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/agent-foreman/skills/feature-next .claude/skills/feature-next && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "feature-next" agent skill from https://github.com/mylukin/agent-foreman/tree/main/plugins/agent-foreman/skills/feature-next into .claude/skills/feature-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-next", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/mylukin/agent-foreman/tree/main/plugins/agent-foreman/skills/feature-nextType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add mylukin/agent-foreman --skill feature-next -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install mylukin/agent-foreman feature-next --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mylukin/agent-foreman.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/agent-foreman/skills/feature-next .agents/skills/feature-next && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "feature-next" agent skill from https://github.com/mylukin/agent-foreman/tree/main/plugins/agent-foreman/skills/feature-next into .agents/skills/feature-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-next", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mylukin/agent-foreman --skill feature-next -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install mylukin/agent-foreman feature-next --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mylukin/agent-foreman.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/agent-foreman/skills/feature-next .cursor/skills/feature-next && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "feature-next" agent skill from https://github.com/mylukin/agent-foreman/tree/main/plugins/agent-foreman/skills/feature-next into .cursor/skills/feature-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-next", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/mylukin/agent-foreman.git --path plugins/agent-foreman/skills/feature-next--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add mylukin/agent-foreman --skill feature-next -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install mylukin/agent-foreman feature-next --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mylukin/agent-foreman.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/agent-foreman/skills/feature-next .gemini/skills/feature-next && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "feature-next" agent skill from https://github.com/mylukin/agent-foreman/tree/main/plugins/agent-foreman/skills/feature-next into .gemini/skills/feature-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-next", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install mylukin/agent-foreman feature-nextInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add mylukin/agent-foreman --skill feature-next -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/mylukin/agent-foreman.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/agent-foreman/skills/feature-next .github/skills/feature-next && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "feature-next" agent skill from https://github.com/mylukin/agent-foreman/tree/main/plugins/agent-foreman/skills/feature-next into .github/skills/feature-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-next", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add mylukin/agent-foreman --skill feature-next -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install mylukin/agent-foreman feature-next --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/mylukin/agent-foreman.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/agent-foreman/skills/feature-next .opencode/skills/feature-next && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "feature-next" agent skill from https://github.com/mylukin/agent-foreman/tree/main/plugins/agent-foreman/skills/feature-next into .opencode/skills/feature-next/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "feature-next", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
feature-next- GitHub stars
- 250
- Token cost
- ~927 tokens
- SKILL.md length
- 218 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- None found
At a glance
Enforces a strict next-implement-check-done cycle through the agent-foreman CLI so an agent works one backlog task at a time, with optional TDD gating.
- Works in 3 steps: needs_review → may be broken → failing → not implemented → Lower priority number → higher priority…
- Picking the next task to work on from a backlog
- SKILL.md covers ⚠️ STRICT WORKFLOW - NO…, ⛔ CLI-ONLY ENFORCEMENT, Quick Start and Workflow, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The workflow has exactly four steps, next, implement, check and done, and the skill is explicit that these may not be skipped, reordered or supplemented with invented extra steps; the check command is required before done, and task files are read only for acceptance criteria after next has already selected the task, never to pick a task, check status or change it directly, since all of that goes through the CLI's own commands. The next command can auto-select the next priority task or take a specific task id, and its output is checked for a TDD-enforcement banner before anything is implemented; in strict TDD mode, code must not be written before tests exist.
Tasks are picked by priority: items needing review come first since they may be broken, then failing tasks that are not yet implemented, then lower numeric priority values rank higher. A separate breakdown-validate-implement cycle runs a validate command once every breakdown task is complete, before any of those pieces are implemented, and done is always run after finishing a task, including a breakdown task. Flags extend the base commands: checking tests before showing a task, a dry-run preview, JSON output for scripting, quiet output, allowing a dirty working tree, and forcing TDD guidance to regenerate.
When your agent uses it
- Picking the next task to work on from a backlog
- Working through one feature end to end with a check step before marking it done
- Following a TDD red-green cycle enforced by the CLI
- Validating a set of breakdown tasks before implementing them
Example prompts
- “Run agent-foreman next and start on whatever it gives me.”
- “What should I work on next from the backlog?”
- “Check this task's implementation and mark it done if it passes.”
Requirements
- The agent-foreman CLI installed in the project
- Pre-approved tools (allowed-tools): Bash, Read, Glob, Grep, Write, Edit
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- needs_review → may be broken
- failing → not implemented
- Lower priority number → higher priority (0 is highest)
What it can do on your machine
Read from SKILL.md and the folder at commit 2763f83. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
BashReadGlobGrepWriteEdit
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Feature Next Task Workflow loads about 927 tokens when it runs. Until then it costs about 92 tokens; SKILL.md has 218 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
allowed-tools: Bash, Read, Glob, Grep, Write, Edit
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 218 words (~927 tokens).
- name
- feature-next
- allowed-tools
- Bash, Read, Glob, Grep, Write, Edit
- user-invocable
- true
Files
Just SKILL.md in plugins/agent-foreman/skills/feature-next of mylukin/agent-foreman.
Open the folder on GitHubat commit 2763f83
Compare with similar skills
Feature Next Task Workflow next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Feature Next Task Workflow this skillmylukin/agent-foreman | 250 | — | ~927 | Automated safety check: Notes | None | |
| Implementericrisco/rsc-harness | 174 | — | ~5.9k | Automated safety check: Notes | MIT | |
| Context Modes0xNyk/lacp | 305 | — | ~313 | Automated safety check: Pass | MIT | |
| TasksRafaelGB/Obsidian-ZettelFlow | 174 | — | ~573 | Automated safety check: Pass | MIT | |
| TDDpietheinstrengholt/rssmonster | 564 | 30 repos | ~906 | Automated safety check: Pass | MIT | |
| TDD WorkflowhellangleZ/burn-in-cceverywhere-ralph | 112 | 11 repos | ~2.4k | Automated safety check: Pass | None |
Similar skills
Context Modes
0xNyk/lacp
Structured work modes for agent sessions. An agent skill from 0xNyk/lacp.
Tasks
RafaelGB/Obsidian-ZettelFlow
Stage 3 of the SDD pipeline — turn a ZettelFlow plan (in a GitHub issue comment) into an ordered TDD task checklist posted as a second issue comment.
TDD
pietheinstrengholt/rssmonster
Test-driven development. An agent skill from pietheinstrengholt/rssmonster.
TDD Workflow
hellangleZ/burn-in-cceverywhere-ralph
A skill your agent uses when writing new features, fixing bugs, or refactoring code.
- Official
TDD
sanity-io/sanity
Test-driven development with red-green-refactor loop. An agent skill from sanity-io/sanity.
More from mylukin/agent-foreman
Agent-Foreman Feature Run
mylukin/agent-foreman
Runs the agent-foreman task loop for one task by ID or unattended across every pending task, following next, implement, check, done for each one.
Multi-Role Spec and Task Breakdown
mylukin/agent-foreman
Runs a requirement through four research-backed specialist agents, a PM, a UX designer, a tech architect and QA, to produce implementable tasks.
Agent Task Backlog Initializer
mylukin/agent-foreman
Builds a feature backlog, progress log, and optional strict test enforcement for agent-driven work with a single init command.
Project Analyze
mylukin/agent-foreman
Scans codebases to generate architecture documentation (ARCHITECTURE.md). Use when joining an existing project, understanding codebase structure, exploring…
Related
Categories
Questions about Feature Next Task Workflow
What does Feature Next Task Workflow do?
Enforces a strict next-implement-check-done cycle through the agent-foreman CLI so an agent works one backlog task at a time, with optional TDD gating. The workflow has exactly four steps, next, implement, check and done, and the skill is explicit that these may not be skipped, reordered or supplemented with invented extra steps; the check command is required before done, and task files are read only for acceptance criteria after next has already selected the task, never to pick a task, check status or change it directly, since all of that goes through the CLI's own commands. The next command can auto-select the next priority task or take a specific task id, and its output is checked for a TDD-enforcement banner before anything is implemented; in strict TDD mode, code must not be written before tests exist.
When should I use Feature Next Task Workflow?
Feature Next Task Workflow fits situations like: picking the next task to work on from a backlog; working through one feature end to end with a check step before marking it done; following a TDD red-green cycle enforced by the CLI; validating a set of breakdown tasks before implementing them.
How do I install Feature Next Task Workflow in Claude Code?
Run `npx skills add mylukin/agent-foreman --skill feature-next -a claude-code`. Or copy the skill folder (plugins/agent-foreman/skills/feature-next in mylukin/agent-foreman) into .claude/skills/feature-next in your project. Claude Code loads it when a task matches its description.
How do I install Feature Next Task Workflow in Codex?
Run `npx skills add mylukin/agent-foreman --skill feature-next -a codex`. Or copy the skill folder (plugins/agent-foreman/skills/feature-next in mylukin/agent-foreman) into .agents/skills/feature-next in your project. Codex loads it when a task matches its description.
Can I use Feature Next Task Workflow in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mylukin/agent-foreman --skill feature-next -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/feature-next, .gemini/skills/feature-next, .github/skills/feature-next and .opencode/skills/feature-next in your project.
What does Feature Next Task Workflow need to run?
SKILL.md names no scripts, command-line tools or credentials: Feature Next Task Workflow is instructions for the agent only. Our summary lists: The agent-foreman CLI installed in the project. Its frontmatter pre-approves these tools: Bash, Read, Glob, Grep, Write, Edit.
Does Feature Next Task Workflow access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Feature Next Task Workflow safe to install?
Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Feature Next Task Workflow use?
No licence was found for Feature Next Task Workflow or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Feature Next Task Workflow use?
About 927 tokens (SKILL.md is roughly 3.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Feature Next Task Workflow?
Skills that share tags, products or a category with Feature Next Task Workflow: Implement (ericrisco/rsc-harness, 174 stars), Context Modes (0xNyk/lacp, 305 stars), Tasks (RafaelGB/Obsidian-ZettelFlow, 174 stars) and TDD (pietheinstrengholt/rssmonster, 564 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Feature Next Task Workflow?
mylukin (a GitHub user) maintains it in mylukin/agent-foreman, which has 250 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on January 23, 2026.
Source: mylukin/agent-foreman on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.