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; ticket entry and status changes belong to a separately authorized CRUD workflow.

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

• A separately configured Plane MCP server with host-permitted read tools; identify its implementation/version and inspect its tool schemas before querying (see references/api-surface.md)
• A Plane workspace with at least one project, cycle, and active issues (otherwise the commands return informative empty states)

Authentication

This skill does not handle credentials directly. Auth is delegated to the MCP server. See references/api-surface.md for version-specific configuration. Never request, print, or copy tokens or raw auth errors. Report a sanitized status and ask the user to verify configuration in their credential store.

Instructions

Mode detection

Determine user intent from their prompt:

• Compound query mode (default): user asks about cycle health, team behavior, stale tickets, reviewer patterns, priority drift, or workload distribution → read agents/plane-analyst.md as an analysis checklist and use the compound-command playbook within the current host permissions.
• API help mode: user asks "how do I query X in Plane" or "what endpoint does Y" → read agents/plane-expert.md as a reference checklist and answer from references/api-surface.md without live API calls.
• …