execute

User Input

$ARGUMENTS

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

Setup

1. Read .coco/config.yaml for project configuration (including pr section).
2. Determine the active epic (from $ARGUMENTS or most recent open epic).
3. 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:

1. Tracker tasks exist with correct dependencies
2. If issue tracker configured: every task has issue_key in metadata
3. Commit message issue keys are real -- keys must reference actual issues
4. 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)