A tracked task is a piece of work recorded in a project task system, and TDD means writing a test before the code it checks. This command carries out the next available task through testing, validation, code review, pull-request creation, and issue-tracker synchronisation.

Use it to select the next unblocked task, implement it with TDD, run pre-commit checks, create a pull request, request an AI review, and update the connected issue tracker.

It removes much of the repeated work involved in taking an approved task from the queue to a reviewed change. Dependency checks help prevent work from starting before its prerequisites are complete.

execute — Command for Claude Code by skullninja/coco-workflow

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo

git clone --depth 1 https://github.com/skullninja/coco-workflow

Made for: Claude Code.

Or install coco, the plugin that ships this one along with the rest of its 6 skills, 14 commands, 4 agents, 3 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/skullninja/coco-workflow/execute/github.svg)](https://agentmods.dev/commands/skullninja/coco-workflow/execute)

Your own site

<a href="https://agentmods.dev/commands/skullninja/coco-workflow/execute"><img src="https://agentmods.dev/badge/commands/skullninja/coco-workflow/execute/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/skullninja/coco-workflow/execute"><img src="https://agentmods.dev/badge/commands/skullninja/coco-workflow/execute.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 3,439 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00028	$0.03439
Opus 5.5	$0.00011	$0.01376
Sonnet 5.5	$0.00006	$0.00688
Haiku 4.5	$0.00003	$0.00344

Measured 3d ago against content hash f06cf44be3ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

execute scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/execute.md · 395 lines

How it starts

The opening of the file, as written. The whole thing — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Setup

Read .coco/config.yaml for project configuration (including pr section).
Determine the active epic (from $ARGUMENTS or most recent open epic).
Determine the feature branch:
- If on a feature/* branch, that is the feature branch
- Otherwise, read feature_branch from the first task's metadata in the epic

Pre-Execution Gate (MANDATORY)

Before starting the execution loop, verify the epic was imported correctly:

coco-tracker epic-status {epic-id}

Check ALL before writing any code:

Tracker tasks exist with correct dependencies
If issue tracker configured: every task has issue_key in metadata
Commit message issue keys are real -- keys must reference actual issues
If pr.enabled: verify on a feature/* branch and remote origin is configured

If any check fails, STOP and use the import skill first.

Execution Loop

1. Find Next Task

coco-tracker ready --json --epic {epic-id}

Never manually pick tasks -- always use ready which respects dependency order.

2. Claim Task

coco-tracker update {task-id} --status in_progress

3. Create Issue Branch

If pr.enabled is false: skip this step.

Read issue_key from task metadata. Determine branch name:

If pr.branch.issue_branch_naming is "issue_key": use {issue_key} (e.g., AUTH-3)
If "task_id": use the tracker task ID (e.g., epic-001.3)
Normalize: lowercase, replace spaces with hyphens

git checkout -b "{feature-branch}/{issue_key}"

4. Bridge to Issue Tracker (Start)

Read issue_key from task metadata. Based on issue_tracker.provider in config:

If "linear": Update issue to status_map.in_progress using mcp__plugin_linear_linear__update_issue

If "github":

If github.use_projects is true and task has gh_project_item_id in metadata: Read .coco/state/gh-projects.json and find the feature entry where project_number matches the task's gh_project_number metadata. Extract project_id, status_field_id, and status_options from that entry. Then:
```
gh project item-edit --project-id {project_id} --id {gh_project_item_id} --field-id {status_field_id} --single-select-option-id {status_options[status_map.in_progress]}
```
Otherwise (legacy fallback): gh issue edit {issue_number} --add-label "{status_map.in_progress from config, lowercase with hyphens}" (label must exist in repo)

Read the full file on GitHub · 395 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago Changed · +2 lines f06cf44be3ee
1mo ago First seen · 393 lines · 28 tokens per session scan A 8df7f092e13a

Subscribe to this mod's changes

execute is a command published in the GitHub repository skullninja/coco-workflow (8 stars, last pushed yesterday), licensed MIT. It adds 28 tokens to every session and 3,439 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Claude Code Project management TDD Testing ai-coding ai-workflow anthropic autonomous-coding claude-code-plugin

ccc-feature-start

Kick off a feature: research context, create an isolated branch, confirm a green baseline, write a task breakdown, and the first failing test. Use when starting new feature work in a git repository.

KevinZai/commander · 44 tokens

ccc-tdd

Build a feature or fix test-first: scaffold the interface, write a failing test, implement the minimum to pass, refactor, then check coverage against the project threshold (80% when none is set). Use when adding a feature, function or component, or reproducing a bug.

KevinZai/commander · 57 tokens

execute