feature-next
A task-based development assistant that enforces a rigid workflow to ensure quality and tracking for single-feature implementation.
Install
mkdir -p .claude/skills/feature-next && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/9497" && unzip -o skill.zip -d .claude/skills/feature-next && rm skill.zipInstalls to .claude/skills/feature-next
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
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'.Key capabilities
- →Implement single tasks from a backlog
- →Follow TDD red-green-refactor cycles
- →Enforce strict task workflows via CLI
- →Manage task priority and status updates
- →Validate task breakdown before implementation
How it works
The tool enforces a strict next-implement-check-done workflow, requiring users to select tasks via CLI and verify implementation before marking them as complete.
Inputs & outputs
When to use feature-next
- →Implementing a single feature from the backlog
- →Applying TDD red-green-refactor cycles
- →Managing development tasks in a disciplined way
About this skill
Task Next
One command: agent-foreman next
⚠️ STRICT WORKFLOW - NO IMPROVISATION
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 |
⛔ CLI-ONLY ENFORCEMENT
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.
Quick Start
agent-foreman next # Auto-select next priority
agent-foreman next auth.login # Specific task
Workflow
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
Check TDD Mode First
Look for "!!! TDD ENFORCEMENT ACTIVE !!!" in agent-foreman next output.
TDD Workflow (when strict mode active)
# 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!
Priority Order
needs_review→ may be brokenfailing→ not implemented- Lower
prioritynumber → higher priority (0 is highest)
⚠️ BREAKDOWN → VALIDATE → IMPLEMENT Workflow
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).
Options
| 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 |
Complete Options
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
When not to use it
- →Performing tasks without explicit task selection
- →Bypassing the required check step
- →Improvising workflow steps outside the defined sequence
Prerequisites
Limitations
- →Requires strict adherence to the defined CLI workflow
- →Cannot bypass CLI for status changes or task selection
How it compares
Unlike manual task management, this tool enforces a rigid, CLI-gated workflow that prevents skipping verification or implementation steps.
Compared to similar skills
feature-next side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| feature-next (this skill) | 0 | 6mo | Review | Beginner |
| webapp-testing | 353 | 3mo | Review | Intermediate |
| dev-browser | 53 | 4mo | Review | Intermediate |
| playwright-browser-automation | 29 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by mylukin
View all by mylukin →You might also like
webapp-testing
anthropics
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
dev-browser
SawyerHood
Browser automation with persistent page state. Use when users ask to navigate websites, fill forms, take screenshots, extract web data, test web apps, or automate browser workflows. Trigger phrases include "go to [url]", "click on", "fill out the form", "take a screenshot", "scrape", "automate", "test the website", "log into", or any browser interaction request.
playwright-browser-automation
lackeyjb
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.
windows-ui-automation
martinholovsky
Expert in Windows UI Automation (UIA) and Win32 APIs for desktop automation. Specializes in accessible, secure automation of Windows applications including element discovery, input simulation, and process interaction. HIGH-RISK skill requiring strict security controls for system access.
unity-mcp-orchestrator
CoplayDev
Orchestrate Unity Editor via MCP (Model Context Protocol) tools and resources. Use when working with Unity projects through MCP for Unity - creating/modifying GameObjects, editing scripts, managing scenes, running tests, or any Unity Editor automation. Provides best practices, tool schemas, and workflow patterns for effective Unity-MCP integration.
agent-browser
vercel-labs
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.