codex

Plane Ops

Plane Agile Ops knowledge plugin: sprint planning, task decomposition, estimation, backlog management, velocity tracking, retrospectives, standups, intake triage, modules, epics, initiatives, milestones, roadmaps, dependencies, burndown, pages (sprint reports, retros, release notes, ADRs, runbooks, specs, meeting notes), labels, workflow states, work item types, custom properties, comments, links, work logs, relations, history, bulk edits, search, members, and assignment. Written for Plane MCP 0.3.0 and later (one resource tool per entity with an `action` parameter, PQL filters, counts, releases); a bootstrap skill finds the tools under any server name and carries the fallback translation for older per-operation connectors. Ships no MCP server; the user connects Plane.

0 on GitHubby AGENTS.STOREv2.0.13MITupdated 7 days agoproject-management

Plugin plane-ops in Agents-Store/codex-plugins. Commands read from the repo's manifest — 6 days ago.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (60)

  • agile-fundamentals

    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, focu

  • assign

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

  • backlog-health

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

  • backlog-management

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

  • bulk-update

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

  • burndown

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

  • close-sprint

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

  • comment

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

  • connector-bootstrap

    Finds the Plane MCP tools when their names are unclear. Probes ToolSearch across MCP servers, connectors and instance naming conventions, handles the resource tools of Plane MCP 0.3.0 and later (one tool per resource with an action parameter) and translates for older per-operation servers. Use when

  • create-epic

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

  • create-module

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

  • create-sprint

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

  • cycles

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

  • daily-standup

    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.

  • decompose

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

  • dependencies

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

  • epic

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

  • epics-initiatives-milestones

    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 betw

  • estimate

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

  • estimation

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

  • find

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

  • groom-backlog

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

  • history

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

  • initiative

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

  • intake-triage

    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 r

  • label

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

  • labels-states-properties

    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

  • link

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

  • log-time

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

  • members

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

  • milestone-status

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

  • milestone

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

  • module

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

  • modules

    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)

  • my-work

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

  • page

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

  • pages-publishing

    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

  • plan-sprint

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

  • project-setup

    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.

  • projects

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

  • property

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

  • publish-report

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

  • relate

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

  • retro

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

  • roadmap

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

  • setup-project

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

  • sprint-planning

    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-retro

    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.

  • sprint-status

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

  • standup

    Generate daily standup summary for current sprint Arguments: <project>.

  • state

    Manage Plane workflow states — list, create, update, delete, reorder Arguments: <action> <project> [args...].

  • task-decomposition

    Task decomposition — INVEST criteria, vertical slicing, epic-to-subtask breakdown, story splitting patterns. Use when breaking down epics, stories, or large work items into smaller pieces.

  • triage-intake

    Triage the Plane intake inbox — accept, defer, or reject incoming items Arguments: <project> [--limit <n>].

  • velocity-metrics

    Velocity and metrics — historical velocity calculation, sprint burndown analysis, WIP limits, throughput tracking, time effort analysis. Use when calculating velocity, analyzing sprint progress, reviewing team metrics, comparing estimated vs actual effort, or checking time logged per story point.

  • velocity

    Calculate team velocity from historical sprint data Arguments: <project> [--sprints <count>].

  • whoami

    Show the current Plane user, workspace, and connector status Arguments: (no arguments).

  • work-item-type

    Manage custom work item types in a Plane project (Story, Bug, Spike, ...) Arguments: <action> <project> [args...].

  • work-item

    Create, update, or inspect a work item (issue/task/ticket) in Plane Arguments: <action> <project> [args...].

  • work-items

    Work item operations in Plane — create, read, update, delete, search, filter with PQL, assign, label, link, comment, relate, and log time on work items (issues/tasks/tickets). Use when the user wants to create a task, update an issue, add a comment, attach a label, link a PR, set a blocker, log work

  • wsjf-prioritize

    Prioritize backlog items using Weighted Shortest Job First (WSJF) scoring Arguments: <project>.

Hooks (2)

  • SessionStart

    cat "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.txt"

  • PreToolUse

    python3 "${CLAUDE_PLUGIN_ROOT}/hooks/plane_guard.py"

View source on GitHub agents.store

More from Agents-Store/codex-plugins

All 44 plugins →

Google Workspace plugin powered by the official googleworkspace/cli (gws) Agent Skills. ~95 skills for Gmail, Drive, Calendar, Sheets, Docs, Chat, Meet, Tasks, Slides, Forms, Classroom and Admin — plus role personas and ready-made recipes — all driving the gws CLI. Vendored from upstream and auto-synced weekly. Requires the gws CLI (npm i -g @googleworkspace/cli) and a one-time OAuth setup.

96 skills

0

Vercel ecosystem plugin. Deployment, AI SDK, Edge Functions, storage, routing, performance optimization. Includes CLI deploy troubleshooting for non-Git projects, Hobby plan fixes, standalone output handling. Based on official vercel-plugin v0.53.0 by Vercel Labs; telemetry is opt-in (VERCEL_PLUGIN_TELEMETRY=on).

44 skills · 1 MCP server · hooks

0

Operations plugin for a fleet of self-hosted OpenClaw gateway instances running as Docker Compose projects on one host. Discovers every instance from the live Docker state (never from hard-coded paths), classifies it ok/degraded/down/alien, and runs day-two maintenance: health and liveness reporting, provider-auth triage (expired, emptied and shadowed OAuth profiles, shared-credential token sink), config surgery with snapshot and executable rollback, memory/embedding repair and reindexing, shared skills and plugins consolidation, Infisical secret-delivery audit by key name only, security audit, version-drift and channel-aware upgrades, and reference-instance cloning. Mutations are dry-run by default behind an eight-block plan, need --yes, and need a typed confirmation when irreversible. Secrets are reported as fingerprints, presence and expiry — never as values. File-based knowledge: no MCP server, no required environment variables, no stored credentials; the single optional variable OPENCLAW_OPS_CONFIG is an escape hatch for the fleet-config path, and deployment specifics live in that operator-owned config outside the repository. Also carries the workspace persona guides (AGENTS.md, SOUL.md, USER.md, IDENTITY.md, standing orders, bootstrap, memory, session analysis) taken over from the retired openclaw-configurator.

33 skills · hooks

0

Turns what a client says into documents they can correct, a machine spec an agent can build from, and a work list somebody can pick up. Keeps the macstack/ folder of a project: macstack.json — the standardized business + technical stack specification, always English — and the six client documents it is written from. OVERVIEW says what the product is and who it is for; USER-CASES carries each case with its UX bar and an addressable acceptance list; UX-UI states what each screen shows and what must never appear on it; AUTOMATION is the trigger -> task -> workflow -> role model; HANDBOOK is how a person actually uses the thing; OPEN-QUESTIONS splits what the client owes from what the team deferred. v3 makes those six pure markdown — headings and bullet lists, nothing else. No YAML blocks, no tables, no change-log sections: the only machine markup is an HTML comment the reader never sees, pointing each entity at its place in the spec. A client can edit the document in any editor and hand it back. Around them: an immutable inbox for anything a client sends, a gated delta/rulings loop that merges it, generated requirements, architecture, test cases and index that carry every id the client documents carry, an append-only ledger with one row per edit and per client comment, tasks reconciled with the team's own tracker, and a review package that shows each statement with its own history and reads the client's answers back into the ledger. Eight commands, one job each — including one that reconciles the whole folder against the source tree in a direction you have to declare: the code is master and every document is corrected through a gate that never silently overrules an answer the client gave, or the documents are master and the gaps become tasks. Every edit is journalled, every finished task sweeps the client documents and not only the generated ones, task statuses move to what the audit actually found — closing what is built and reopening what is not — and every document

26 skills · hooks

0

Sendpulse multi-channel marketing plugin. Manage chatbots (Telegram, WhatsApp, Instagram, Messenger, Viber, TikTok), CRM (contacts, deals, pipelines, boards, tasks), Courses (LMS) academies, courses and students, email campaigns, templates, addressbooks, and SMTP transactional email via 147 MCP tools.

26 skills · 1 MCP server

0

NocoBase v2 development plugin. Build, manage, and operate NocoBase through the `nb` CLI 2.2 (primary) or REST API (fallback). Bundles 20 official upstream skills from nocobase/skills (auto-synced weekly via GitHub Action; UI authoring enters through nocobase-portal-manage), 5 custom skills (overview, auth, cli-recipes, api-reference, examples), and an OpenAPI 3.0.3 snapshot of NocoBase v2.1.0-beta.29 (272 endpoints; refresh from a 2.2.x stand pending). Targets the stable @nocobase/cli channel (Node.js 22+); NocoBase 2.1.0+ for agent connection. No MCP server shipped; NocoBase has its own at /api/mcp. Env vars match upstream naming: NB_URL + NB_USER + NB_PASSWORD for sign-in flow, or NB_URL + NB_TOKEN for the long-lived API Key path.

24 skills

0

Similar plugins

atlassian

claude

Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.

6 skills · 1 MCP server

anthropics/claude-plugins-official 47,076

The official monday.com plugin for Claude Cowork. Manage boards, items, docs, and forms across work management, CRM, dev, service, and campaigns. Full read and write access via OAuth.

5 skills · 1 MCP server

anthropics/knowledge-work-plugins 35,601

Founder-mode executive team plugin: 13 cs-* C-suite agents (CFO, CMO, CRO, CPO, COO, CHRO, CISO, Chief of Staff, General Counsel, Chief Data Officer, Chief AI Officer, Chief Customer Officer, VP of Engineering) with distinct cognitive voices, plus 21 /c-level-agents:* slash commands — forcing-question office hours (CFO/CMO/CPO/CRO/CTO/CISO/GC/CDO/CAIO/CCO/VPE reviews), strategic sprint pipeline (brief → boardroom → decide → execute → post-mortem), and meta routing (/c-level-agents:founder-mode auto-router, /cs-onboard, /c-level-agents:cross-eval multi-model consensus, /c-level-agents:freeze cooldown lock). Wraps the 33 c-level skills with cognitive gearing, persona voice, and artifact-driven handoffs. The business-domain answer to YC Garry Tan's gstack.

22 skills · 13 agents

alirezarezvani/claude-skills 29,725

Execution and product management skills: PRDs, OKRs, roadmaps, sprints, pre-mortems, stakeholder maps, user stories, prioritization frameworks, live Q&A and polls, and more.

18 skills · 11 commands

phuryn/pm-skills 27,939

Product, legal, and business specialists - product strategy, licensing, project management, UX research

VoltAgent/awesome-claude-code-subagents 26,513

gsd

claude

Get Shit Done -- a structured workflow plugin for Claude Code that adds planning, execution, and verification commands with MCP-backed project state

83 skills · 33 agents · 1 MCP server

davepoon/buildwithclaude 3,741

Maintain Plane Ops?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins44 plugins