Plane — Team Behavior Observatory

Plane is a team behavior observatory. Most Plane integrations wrap the API for ticket entry; this one synthesizes the data Plane already has into observations about how a team actually behaves under pressure — cycle velocity vs. plan, ownership churn on stuck tickets, reviewer gate strength, stated-vs-actual priority drift, and cross-project workload concentration.

What this plugin is

A behavioral observation layer on top of Plane's project-tracking API. It does not replicate mcp__plane's CRUD surface; that's the data-retrieval layer. This plugin sits one level up — it asks behavioral questions that require JOINing across multiple Plane endpoints to answer.

What this plugin is not

• Not a Plane CLI (use mcp__plane MCP directly for ticket CRUD)
• Not a clone of the Plane web dashboard (the dashboard already shows you ticket state)
• Not a generic project-tracker skill (the framing is specifically behavioral, anchored in the NOI)

The five compound commands

Each answers a question that cannot be answered from any single Plane API endpoint:

| Command | Question | |---|---| | /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? |

Each command's exact endpoint sequence, scoring formula, and output table format is documented in skills/plane/references/compound-commands.md.

Install

/plugin install plane@claude-code-plugins-plus

Prerequisites

• mcp__plane MCP server installed and configured (env vars PLANE_API_KEY, PLANE_WORKSPACE_SLUG, PLANE_API_HOST_URL). Without it, the skill returns documentation-only output + an install hint.
• A Plane workspace with at least one project, cycle, and active issues — empty workspaces return informative empty states.

How it works

The orchestrator skill (skills/plane/SKILL.md) routes user intent to one of two agents:

• plane-expert — answers "how do I query X in Plane" without firing live API calls
• plane-analyst — orchestrates the compound commands, calling mcp__plane__* tools in the documented sequence and synthesizing the result

Both agents read from the references in skills/plane/references/ as their ground truth — noi.md is the design anchor; api-surface.md is the documented endpoint subset; compound-commands.md is the per-command playbook.

Provenance

This plugin was produced by /skill-creator --forge plane on 2026-05-07. The forge run's audit trail lives in .forge/ — research notes, ecosystem analysis, validation evidence — visible to anyone reviewing how the plugin came to exist.

plugin.json carries "generated": true and "author_type": "forge" so the marketplace surfaces a "Forge-generated" provenance pill on the detail page.

License

MIT. See LICENSE (project-wide root file).