plane-ops

Single source of truth for Agile formulas, Definition of Ready, Definition of Done, MoSCoW priority mapping, WSJF scoring, capacity and velocity formulas, WIP limits, Fibonacci story points, and sprint buffer policy. Use whenever the user asks about story points, estimation, velocity, capacity, focus factor, WSJF, DoR/DoD, MoSCoW, Fibonacci, sprint buffer, or any Agile rule — and whenever any other plane-ops skill, command, or agent needs canonical Agile definitions. Do not duplicate these rules elsewhere — link here instead.

Assign or unassign a Plane work item to one or more users Arguments: <project> <item> <assignee> [more...].

Analyze backlog health — unestimated items, stale items, missing details Arguments: <project>.

Backlog management — MoSCoW prioritization, WSJF scoring, value-effort analysis, backlog health monitoring, grooming workflows. Use when prioritizing backlog, grooming items, or assessing backlog health.

Apply the same change to many Plane work items at once Arguments: <project> <items...> <changes...>.

Show sprint burndown and projected completion for the active cycle Arguments: <project> [--cycle <current|name>].

Close current sprint — review completion, transfer incomplete items, archive Arguments: <project> [--transfer-to <next-cycle-name>].

Add or list comments on a Plane work item Arguments: <action> <project> <item> [body].

MUST be consulted at the start of ANY Plane-related request before answering the user or declaring tools unavailable. Discovers Plane tools across any MCP server, connector, or instance naming convention - the resource tools of Plane MCP 0.3.0 and later (one tool per resource with an `action` parameter, which every other plane-ops skill and command is written for) - and carries the fallback translation for servers older than 0.3.0 that expose one tool per operation. Use when the user mentions sprint, backlog, work item, cycle, epic, module, milestone, initiative, project, issue, ticket, task, standup, retro, estimate, roadmap, board, Plane, or any work-management operation, even if Plane tools are not visible yet. Also use before saying "I don't have access to Plane tools" or "tool not available".

Create a Plane epic for a large feature spanning multiple sprints Arguments: <project> <epic name> [--lead <user>] [--target <YYYY-MM-DD>].

Create a Plane module (feature/workstream grouping across sprints) Arguments: <project> <module name> [--lead <user>] [--target <YYYY-MM-DD>].

Create a new sprint cycle in Plane Arguments: <project> <name> --start <YYYY-MM-DD> --end <YYYY-MM-DD>.

Manage Plane cycles beyond planning — list, complete, archive, transfer, delete Arguments: <action> <project> [args...].

Daily standup support — progress summary, blocker identification, team status updates, sprint progress tracking, async standup. Use when running daily standups, checking team progress, identifying blockers, or generating async standup reports.

Break down a work item into smaller stories/tasks using INVEST criteria Arguments: <work-item-identifier>.

Show dependency graph and active blockers for a project or sprint Arguments: <project> [--cycle <current|next|name>].

Manage Plane epics — list, get, update, delete (complement to /create-epic) Arguments: <action> <project> [args...].

Long-horizon planning in Plane — epics, initiatives, and milestones. Use when the user wants to create an epic, group epics under an initiative, track a release milestone, build a roadmap, or report progress on a long-running goal that spans multiple sprints or modules. Clarifies the difference between the three and when to use which.

Estimate unestimated work items using Fibonacci story points Arguments: <project> [--cycle <cycle-name>] [--scale fibonacci|tshirt].

Estimation — story points, Fibonacci scale, t-shirt sizing, relative estimation, planning poker facilitation. Use when estimating work items or running estimation sessions.

Tool call patterns, end-to-end workflow examples, and scenario references for Plane Agile workflows. Use when needing reference implementations, complete examples, or tool call patterns.

Search Plane work items by query, identifier, or filter Arguments: <query> [--project name] [--state name] [--assignee user] [--label name].

Run a backlog grooming session — refine, estimate, and prioritize Arguments: <project> [--limit <n>].

Show the change history (activity log) of a Plane work item Arguments: <project> <item> [--limit n].

Manage Plane initiatives — strategic groupings above epics Arguments: <action> [args...].

Plane intake inbox — triage incoming requests, bug reports, and ideas before they enter the backlog. Use when the user wants to review the intake queue, accept or reject incoming items, convert intake items into work items, or set up a triage process. Covers daily/weekly triage rituals and routing rules.

Manage Plane labels — list, create, update, delete, or apply to a work item Arguments: <action> <project> [args...].

Design taxonomies for Plane projects — labels, workflow states, work item types, and custom properties. Use when the user asks how to organize labels, design a state machine, set up custom fields, configure work item types, decide between label/property/type, or audit a noisy taxonomy. Covers naming conventions, recommended sets, and the difference between the four metadata mechanisms.

Add or list external links (PRs, docs, designs) on a Plane work item Arguments: <action> <project> <item> [url] [title].

Log work time on a Plane work item (create a work log entry) Arguments: <project> <item> <duration> [description].

List Plane workspace or project members and their roles Arguments: [scope] [project].

Manage Plane milestones — create, list, add items, update, delete Arguments: <action> <project> [args...].

Show status and risk for a Plane milestone (release/launch tracking) Arguments: <project> [milestone name or id].

Manage Plane modules — list, get, update, add items, archive (complement to /create-module) Arguments: <action> <project> [args...].

Plane modules — feature and workstream grouping that cuts across sprints. Use when the user wants to group related work items by feature area, track progress of a larger feature over multiple sprints, create or manage modules, or ask about workstream progress. Modules complement cycles (time-boxed) by organizing work around outcomes (scope-boxed).

List Plane work items assigned to the current user Arguments: [--project name] [--state name] [--cycle current|next|all] [--limit n].

Create, list, get, or update a Plane page (project or workspace scope) Arguments: <action> [scope] [project] [args...].

Create and publish Plane pages — sprint reports, retro notes, release notes, roadmap, meeting notes, decision logs (ADRs), specs, runbooks, and any general-purpose page as formatted HTML. Use when the user wants to publish a report, write a sprint summary, create a retro page, generate release notes, share a roadmap, document a decision, write a spec, capture meeting notes, or create any Plane page. Includes reusable HTML templates and Plane editor compatibility rules.

Plan a new sprint — calculate capacity, select items from backlog, set sprint goal Arguments: <project> [--duration <days>] [--goal <sprint goal>].

Agile-ready project setup — states, labels, work item types, properties, and feature configuration for Agile workflows. Use when setting up a new project or configuring an existing project for Agile.

List, inspect, update, or delete Plane projects (complement to /setup-project) Arguments: <action> [args...].

Manage custom properties on Plane work items (severity, customer impact, etc.) Arguments: <action> <project> [args...].

Publish a Plane page — sprint report, retro, release notes, or roadmap Arguments: <type> <project> [args...].

Create a relation between two Plane work items (block, duplicate, relates-to) Arguments: <relation> <project> <from-item> <to-item>.

Run a sprint retrospective and create action items Arguments: <project> [--format start-stop-continue|daki|4ls].

Generate a Now / Next / Later roadmap view across cycles, modules, epics Arguments: <project> [--horizon <weeks>].

Set up a new Agile-ready project with recommended states, labels, and work item types Arguments: <project-name> [--template lean|standard].

Sprint planning — capacity calculation, sprint goal setting, work item selection, cycle creation. Use when planning a new sprint, calculating capacity, or selecting items for a sprint.

Sprint review and retrospective — completion metrics, previous retro action review, Start-Stop-Continue retro, DAKI format, 4Ls format, action item tracking, sprint close. Use when running sprint review, retrospective, closing a sprint, or reviewing previous retro action item status.

Show current sprint status — progress, burndown, at-risk items Arguments: <project>.