Cooperation Modes

The skill auto-detects your team's cooperation mode from existing intake answers. No additional questions needed.

Detection Logic

if num_agents == 0             → Human-only
if num_agents > 0 AND maturity in [exploratory, partial] → Hybrid
if num_agents > 0 AND maturity == mostly-automated       → Agent-first

Three Modes

Human-Only

Traditional team, no AI agents.

• Story points: Use for sizing AND velocity — standard scrum works
• Velocity: Track in points/sprint
• Sprint planning: Fill to velocity in points
• Output: Shows points prominently alongside hours

Hybrid

Humans and agents working together. Most common mode.

• Story points: Use for sizing and prioritization only
• Hours: Use for sprint planning and velocity
• Velocity: Dual-track — points for trend, hours for planning
• Divergence detection: When points velocity rises but hours velocity stays flat, you've hit your human review ceiling
• Output: Shows both points and hours, labels which to use for what

Why dual-track? The same 5-point task might take 8 hours without an agent or 2 hours with one. Points measure complexity, hours measure delivery speed. With agents, these diverge.

Agent-First

Mostly autonomous agents with human review/steering.

• Story points: Optional for rough sizing ("is this bigger than that?")
• Hours: Plan by human review capacity — this is the real bottleneck
• Velocity: Track in human review hours/sprint
• Output: Leads with hours, includes review hours as separate line

Why hours only? Velocity in points becomes meaningless noise when agents can churn through tasks in minutes. The constraint is how fast humans can review, approve, and fix.

Impact on Output

The detected mode affects:

• One-line summary format
• Whether points appear in output
• Sprint fit check units (points vs hours vs review hours)
• Velocity tracking recommendations
• Calibration guidance

See Sprint Velocity for mode-aware velocity tracking. See Output Format for mode-specific output examples.