csp-agent-teamslisted

| Task Type | Characteristics | Model Tier | |-----------|-----------------|------------| | Mechanical | 1-2 files, clear spec | Fast/cheap | | Integration | Multi-file, debugging | Standard | | Architecture/Review | Design judgment, broad understanding | Most capable | ### Handling Agent Status - **DONE** → Proceed to spec review - **DONE_WITH_CONCERNS** → Read concerns before proceeding - **NEEDS_CONTEXT** → Provide missing context, re-dispatch - **BLOCKED** → Assess: context problem → more context; reasoning problem → more capable model; task too large → break it down; plan wrong → escalate to human ### Agent Prompt Structure Good prompts are: 1. **Focused** — One clear problem domain 2. **Self-contained** — All context needed to understand the problem 3. **Specific about output** — What should the agent return? ```markdown Fix the 3 failing tests in src/agents/agent-tool-abort.test.ts: 1. "should abort tool with partial output capture" - expects 'interrupted at' in message 2. "should handle mixed completed and aborted tools" - fast tool aborted instead of completed 3. "should properly track pendingToolCount" - expects 3 results but gets 0 These are timing/race condition issues. Your task: 1. Read the test file and understand what each test verifies 2. Identify root cause - timing issues or actual bugs? 3. Fix by replacing arbitrary timeouts with event-based waiting Do NOT just increase timeouts - find the real issue. Return: Summary of what you found and what you