Why This Matters

Delegation success depends on setup. Poorly-prepared issues produce poor agent PRs. This lesson builds the delegation runbook.

Concept Explained

Delegation setup: label issue as agent-eligible, write detailed acceptance criteria, ensure tests exist, verify CI gates, confirm branch protection.

How It Works

Triage issue for delegation eligibility. Add detailed acceptance criteria. Ensure tests exist or are specified. Add 'agent-ok' label. Assign to agent. Monitor.

Step-by-Step Tutorial

1. Triage for eligibility

2. Write acceptance criteria

3. Ensure tests exist

4. Verify CI gates

5. Verify branch protection

6. Add label and assign

7. Monitor

Real-World Example

A team prepared an issue: 'Add null check to parseDate. Test in tests/date.test.ts: should throw TypeError on null input. Function in src/date.ts.' Agent completed in 8 minutes, PR passed review. Clean delegation thanks to prep.

Example Prompts / Commands / Code

Title: Add null check to parseDate function

Description:
The `parseDate` function in `src/date.ts` throws an unhandled TypeError when input is null. Add a null check that throws a descriptive TypeError.

Acceptance criteria:
- [ ] `parseDate(null)` throws TypeError with message 'input is required'
- [ ] `parseDate('2024-01-15')` returns Date object (existing behavior preserved)
- [ ] `parseDate('invalid')` returns null (existing behavior preserved)
- [ ] Test added in `tests/date.test.ts` covering the null case

Files affected:
- src/date.ts
- tests/date.test.ts

Out of scope:
- Other functions in date.ts
- Type definitions
- Documentation

Labels: agent-ok, good-first-issue

1. Triage issue (see PR-15 scope-of-use)
2. Write acceptance criteria (specific, testable)
3. Ensure tests exist or are specified
4. Verify CI gates (status checks, required reviewers)
5. Verify branch protection (no direct push to main)
6. Add 'agent-ok' label
7. Assign to agent
8. Monitor (check progress every 30 min)
9. Review PR when opened (use IN-32 checklist)
10. Iterate if needed (reject + refine issue + re-delegate)
11. Merge when satisfied

Common Mistakes

• Vague issues — agent flails.
• No acceptance criteria — can't verify completion.
• No tests — agent's changes untested.
• No CI gates — agent's PR could merge without review.

Best Practices

• Triage for eligibility first.
• Write specific, testable acceptance criteria.
• Ensure tests exist or specify what to add.
• Verify CI gates and branch protection.
• Use 'agent-ok' label for eligible issues.

Troubleshooting

Practical Exercise

Professional Challenge

Frequently Asked Questions

Further Reading

• Copilot coding agent

Official References

• Copilot coding agent

Related lessons: PR-15, PR-16