| name | plane |
| description | Plane is a team behavior observatory — synthesize Plane API data into observations
about how teams actually behave under pressure, not just ticket state. Five compound
commands surface cycle velocity vs. plan, stale-ticket ownership churn, reviewer gate
strength, stated-vs-actual priority drift, and cross-project workload concentration.
Reads from the live mcp__plane MCP server when present; documentation-only otherwise.
Use when investigating "why is this team's plan diverging from reality", auditing cycle
health, finding orphan tickets, identifying review bottlenecks, or onboarding to a
new project. Trigger with "/plane-cycle-velocity", "/plane-stale-tickets",
"/plane-reviewer-gate-strength", "/plane-priority-drift", "/plane-cross-project-load",
"audit Plane cycle", "team behavior plane", "how is my team behaving".
|
| allowed-tools | Read,Bash(jq:*),Bash(date:*),AskUserQuestion |
| version | 0.3.0 |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| license | MIT |
| compatibility | Designed for Claude Code; requires mcp__plane MCP server configured (PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_API_HOST_URL env vars) |
| tags | ["plane","project-management","team-behavior","observability","productivity"] |
| model | inherit |
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:
/plane-cycle-velocity — does cycle close-out match cycle planning?/plane-stale-tickets — which In Progress tickets are quietly failing under shared ownership?/plane-reviewer-gate-strength — which reviewers gate-keep harder than the spec demands?/plane-priority-drift — does the team plan high-priority work but ship low-priority work?/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
mcp__plane MCP server installed and configured (env vars PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_API_HOST_URL)- 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 the env-var setup; if mcp__plane returns an auth error, the skill surfaces the error verbatim and instructs the user to verify their token.
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 → route to
plane-analyst agent (see agents/plane-analyst.md) which orchestrates the compound commands.
