delegate-issue

Delegates fully-scoped coding issues to SWE-AF nodes and merges returned implementation branches.

989|171|Updated Feb 4, 2026
One-click install
npx skills add https://github.com/Agent-Field/SWE-AF --skill delegate-issue
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: delegate-issue
Source: https://github.com/Agent-Field/SWE-AF/tree/main/.claude/skills/delegate-issue
Command: npx skills add https://github.com/Agent-Field/SWE-AF --skill delegate-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Offloading well-specified coding tasks to a separate agent harness normally requires manual coordination, token-heavy planning, and ad-hoc branch handling. This Skill lets a main harness fan out independent, fully-specified issues to a SWE-AF sub-harness that implements each issue on an isolated branch with cheap models, while the main harness keeps planning, review, and merging.

Core Features & Use Cases

  • Async issue delegation: Fires swe-planner.implement_issue executions via the AgentField HTTP API with structured issue specs including acceptance criteria, files to modify, and testing strategy.
  • Progress tracking and result triage: Polls execution status and agent notes, then handles success, partial-salvage, and empty-result outcomes with concrete git workflows.
  • Cost and safety guardrails: Caps fan-out at 3 concurrent delegations per repo, forbids blind retries, and requires the main harness to run its own integration test gate after merging.
  • Use Case: While refactoring a large service, delegate three independent, fully-specified fixes (e.g., add input validation to module A, migrate module B's logging, add tests for module C) to SWE-AF in parallel, then review each returned branch with git diff and merge the ones that pass your test suite.

Quick Start

Ask the agent to delegate a fully-specified issue to SWE-AF by composing an issue spec with title, description, and acceptance criteria, firing an async implement_issue call, and merging the returned branch after review.

Frequently Asked Questions about delegate-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delegate a coding issue to SWE-AF?

Compose a JSON issue spec with title, description, acceptance criteria, and files to modify, then POST it to /api/v1/execute/async/swe-planner.implement_issue with the repo path and base branch. Capture the execution_id from the 202 response and poll for the result.

When should I use implement_issue instead of swe-planner.build?

Use implement_issue only when the change is fully specified: you can name the files, behavior, and acceptance criteria without any planning. Vague feature requests belong to swe-planner.build, which handles scoping and planning itself.

How many issues can I delegate to SWE-AF in parallel?

Cap fan-out at 3 concurrent delegations per repository unless the user explicitly requests more. Each delegation is a paid multi-agent run, so unbounded parallel delegation creates unexpected cost.

What happens when a SWE-AF delegation fails?

A failed execution may still return a branch with salvaged partial work, which you can fix forward, re-delegate with a sharpened spec, or delete. If the branch is empty, nothing usable was produced and you should improve the spec before retrying rather than retrying verbatim.

Does the SWE-AF sub-harness run the full test suite before returning a branch?

No, the sub-harness verifier is only a per-issue check. After merging all accepted branches, the main harness must run the project's full test suite itself as the integration gate before reporting done.