From harness
Use this skill when the user asks how the 2-agent workflow operates, wants to understand the collaboration process, or needs guidance on Cursor/CC roles and responsibilities. Do NOT load for: actual implementation work, executing handoffs (use cc-cursor-cc instead), or workflow configuration setup. Reference guide for Cursor ↔ Claude Code 2-agent collaboration workflow — explains roles, handoff patterns, and process flow.
npx claudepluginhub tim-hub/powerball-harness --plugin harnessThis skill is limited to using the following tools:
A skill that provides guidance on the Cursor ↔ Claude Code 2-agent workflow.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
A skill that provides guidance on the Cursor ↔ Claude Code 2-agent workflow.
This skill is triggered by the following phrases:
This skill explains the role assignments and collaboration methods between Cursor (PM) and Claude Code (Worker).
| Agent | Role | Responsibilities |
|---|---|---|
| Cursor | PM (Project Manager) | Task assignment, reviews, production deploy decisions |
| Claude Code | Worker | Implementation, testing, CI fixes, staging deploy |
┌─────────────────────────────────────────────────────────┐
│ Cursor (PM) │
│ - Add tasks to Plans.md │
│ - Request work from Claude Code (/handoff-to-claude) │
│ - Review completion reports │
│ - Decide on production deploys │
└─────────────────────┬───────────────────────────────────┘
│ Task request
▼
┌─────────────────────────────────────────────────────────┐
│ Claude Code (Worker) │
│ - Execute tasks with /work (supports parallel) │
│ - Implement -> Test -> Commit │
│ - Auto-fix on CI failure (up to 3 times) │
│ - Report completion with /handoff-to-cursor │
└─────────────────────┬───────────────────────────────────┘
│ Completion report
▼
┌─────────────────────────────────────────────────────────┐
│ Cursor (PM) │
│ - Review changes │
│ - Verify staging behavior │
│ - Execute production deploy (after approval) │
└─────────────────────────────────────────────────────────┘
| Marker | Meaning | Set By |
|---|---|---|
pm:requesting | Requested by PM (compat: cursor:requesting) | PM (Cursor/PM Claude) |
cc:TODO | Not yet started by Claude Code | Either |
cc:WIP | Claude Code working on it | Claude Code |
cc:done | Claude Code completed | Claude Code |
pm:confirmed | PM confirmed complete (compat: cursor:confirmed) | PM (Cursor/PM Claude) |
cursor:requesting | (compat) Synonym for pm:requesting | Cursor |
cursor:confirmed | (compat) Synonym for pm:confirmed | Cursor |
blocked | Blocked | Either |
pm:requesting -> cc:WIP -> cc:done -> pm:confirmed
| Command | Purpose |
|---|---|
/harness-init | Project setup |
/plan-with-agent | Planning and task breakdown |
/work | Task execution (supports parallel) |
/handoff-to-cursor | Completion report (to Cursor PM) |
/sync-status | Status check |
| Skill | Trigger Example |
|---|---|
handoff-to-pm | "Report completion to PM" |
handoff-to-impl | "Hand off to the implementer" |
| Command | Purpose |
|---|---|
/handoff-to-claude | Request task from Claude Code |
/review-cc-work | Review completion reports |
When CI fails 3 consecutive times:
A: Even when working solo, using Plans.md for task management is recommended. Perform production deploys manually and carefully.
A: Ask Cursor for clarification, or use /sync-status to organize the current status.
A: After 3+ failures, stop auto-fixing and escalate to Cursor.