Plane — Team Behavior Observatory

A behavioral observation layer on top of Plane's project-tracking API. This skill does not wrap Plane CRUD — mcp__plane already does that and you should call it directly for ticket entry, status changes, etc.

Instead, this skill answers behavioral questions about how a team is actually performing under pressure: cycle velocity vs. plan, ownership churn, reviewer gate strength, priority drift, and cross-project load. Each question is answered by a compound command that synthesizes data across multiple Plane endpoints — observations no single endpoint exposes.

Overview

The NOI (references/noi.md) is the design anchor: Plane is a team behavior observatory. Five compound commands derive from that framing:

1. /plane-cycle-velocity — does cycle close-out match cycle planning?
2. /plane-stale-tickets — which In Progress tickets are quietly failing under shared ownership?
3. /plane-reviewer-gate-strength — which reviewers gate-keep harder than the spec demands?
4. /plane-priority-drift — does the team plan high-priority work but ship low-priority work?
5. /plane-cross-project-load — which engineers are spread across too many active projects?

None of these are answerable from any single Plane API call. Each requires cross-endpoint synthesis. That synthesis is the value.

Prerequisites