Plane Agile Ops knowledge plugin. Sprint planning, task decomposition, estimation, backlog management, velocity tracking, retrospectives, standups, intake triage, modules, epics, milestones, roadmaps, dependencies, burndown, and page publishing. Written for Plane MCP 0.3.0+ (resource tools with an action parameter, PQL filters, releases); a bootstrap skill discovers the tools across naming conventions and translates for older per-operation connectors.
Plugin plane-ops from marketplace agents-store-claude-plugins in Agents-Store/claude-plugins. Commands read from the repo's manifest — today.
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.
agile-fundamentalsSingle 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
backlog-managementBacklog management — MoSCoW prioritization, WSJF scoring, value-effort analysis, backlog health monitoring, grooming workflows. Use when prioritizing backlog, grooming items, or assessing backlog health.
connector-bootstrapFinds 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
daily-standupDaily 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.
epics-initiatives-milestonesLong-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
estimationEstimation — story points, Fibonacci scale, t-shirt sizing, relative estimation, planning poker facilitation. Use when estimating work items or running estimation sessions.
intake-triagePlane 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
labels-states-propertiesDesign 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
modulesPlane 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)
pages-publishingCreate 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
project-setupAgile-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.
sprint-planningSprint 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-retroSprint 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.
task-decompositionTask 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.
velocity-metricsVelocity 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.
work-itemsWork 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
/plane-ops:assignAssign or unassign a Plane work item to one or more users
/plane-ops:backlog-healthAnalyze backlog health — unestimated items, stale items, missing details
/plane-ops:bulk-updateApply the same change to many Plane work items at once
/plane-ops:burndownShow sprint burndown and projected completion for the active cycle
/plane-ops:close-sprintClose current sprint — review completion, transfer incomplete items, archive
/plane-ops:commentAdd or list comments on a Plane work item
/plane-ops:create-epicCreate a Plane epic for a large feature spanning multiple sprints
/plane-ops:create-moduleCreate a Plane module (feature/workstream grouping across sprints)
/plane-ops:create-sprintCreate a new sprint cycle in Plane
/plane-ops:cyclesManage Plane cycles beyond planning — list, complete, archive, transfer, delete
/plane-ops:decomposeBreak down a work item into smaller stories/tasks using INVEST criteria
/plane-ops:dependenciesShow dependency graph and active blockers for a project or sprint
/plane-ops:epicManage Plane epics — list, get, update, delete (complement to /create-epic)
/plane-ops:estimateEstimate unestimated work items using Fibonacci story points
/plane-ops:findSearch Plane work items by query, identifier, or filter
/plane-ops:groom-backlogRun a backlog grooming session — refine, estimate, and prioritize
/plane-ops:historyShow the change history (activity log) of a Plane work item
/plane-ops:initiativeManage Plane initiatives — strategic groupings above epics
/plane-ops:labelManage Plane labels — list, create, update, delete, or apply to a work item
/plane-ops:linkAdd or list external links (PRs, docs, designs) on a Plane work item
/plane-ops:log-timeLog work time on a Plane work item (create a work log entry)
/plane-ops:membersList Plane workspace or project members and their roles
/plane-ops:milestone-statusShow status and risk for a Plane milestone (release/launch tracking)
/plane-ops:milestoneManage Plane milestones — create, list, add items, update, delete
/plane-ops:moduleManage Plane modules — list, get, update, add items, archive (complement to /create-module)
/plane-ops:my-workList Plane work items assigned to the current user
/plane-ops:pageCreate, list, get, or update a Plane page (project or workspace scope)
/plane-ops:plan-sprintPlan a new sprint — calculate capacity, select items from backlog, set sprint goal
/plane-ops:projectsList, inspect, update, or delete Plane projects (complement to /setup-project)
/plane-ops:propertyManage custom properties on Plane work items (severity, customer impact, etc.)
/plane-ops:publish-reportPublish a Plane page — sprint report, retro, release notes, or roadmap
/plane-ops:relateCreate a relation between two Plane work items (block, duplicate, relates-to)
/plane-ops:retroRun a sprint retrospective and create action items
/plane-ops:roadmapGenerate a Now / Next / Later roadmap view across cycles, modules, epics
/plane-ops:setup-projectSet up a new Agile-ready project with recommended states, labels, and work item types
/plane-ops:sprint-statusShow current sprint status — progress, burndown, at-risk items
/plane-ops:standupGenerate daily standup summary for current sprint
/plane-ops:stateManage Plane workflow states — list, create, update, delete, reorder
/plane-ops:triage-intakeTriage the Plane intake inbox — accept, defer, or reject incoming items
/plane-ops:velocityCalculate team velocity from historical sprint data
/plane-ops:whoamiShow the current Plane user, workspace, and connector status
/plane-ops:work-item-typeManage custom work item types in a Plane project (Story, Bug, Spike, ...)
/plane-ops:work-itemCreate, update, or inspect a work item (issue/task/ticket) in Plane
/plane-ops:wsjf-prioritizePrioritize backlog items using Weighted Shortest Job First (WSJF) scoring
plane-agile-coachAgile Coach for Plane project management. Guides startups through sprint planning, backlog management, task decomposition, estimation, retrospectives, standups, velocity tracking, intake triage, modules, epics, milestones, roadmaps, dependencies, and publishing reports as Plane pages. <example> user
plane-sprint-plannerSpecialized sprint planner for Plane. Handles capacity calculation, sprint goal setting, work item selection, and sprint creation with Agile best practices for startup teams. Works with any Plane MCP server, connector, or cowork instance. <example> user: "Create a 1-week sprint starting Monday with
cat "${CLAUDE_PLUGIN_ROOT}/hooks/session-start.txt"
python3 "${CLAUDE_PLUGIN_ROOT}/hooks/plane_guard.py"
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
Vercel ecosystem dev plugin. Deployment, AI SDK, Edge Functions, storage, routing, performance optimization. CLI deploy troubleshooting for non-Git projects, Hobby plan fixes, standalone output handling, CMS deploy hooks. Based on official vercel-plugin v0.53.0 by Vercel Labs; telemetry is opt-in (VERCEL_PLUGIN_TELEMETRY=on).
40 skills · 4 commands · 3 agents · 1 MCP server · hooks
Day-two operations for a fleet of self-hosted OpenClaw gateway instances on one Docker host. Discovers every instance from the live Docker state instead of hard-coded paths, classifies it ok / degraded / down / alien, and drives the repair work: health and liveness reporting, provider-auth triage (expired, emptied and shadowed OAuth profiles, shared-credential token sink), config surgery with a snapshot and an executable rollback, memory and embedding repair, shared skills and plugins consolidation, secret-delivery audit by key name only, security audit, version-drift and channel-aware upgrades, and reference-instance cloning. Mutations are dry-run behind an eight-block plan, need --yes, and need a typed confirmation when irreversible. Secrets are reported as fingerprint, presence and expiry — never as values. No MCP server and no required environment variables: the one 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.
22 skills · 11 commands · 2 agents · hooks
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.
11 skills · 15 commands · 2 agents · 1 MCP server
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
18 skills · 8 commands · 1 agent · hooks
Dokploy self-hosted PaaS development plugin (aligned with Dokploy v0.30.x). Deploy applications, provision 6 database types (Postgres, MySQL, MariaDB, MongoDB, Redis, LibSQL), manage domains and Docker Compose stacks, AND debug failed deployments end-to-end — reads runtime logs of every container (including each container in a Docker Compose stack) over the API/MCP with tail/since/search, plus AI-powered log analysis (ai-analyzeLogs), Docker container and host introspection (server health, events, disk usage, images, volumes), Traefik diagnosis, and a guided recovery chain. Complete MCP/REST coverage: all 604 operations across 57 categories indexed with params — covers per-service Docker network management, vault (external secrets) providers, DNS providers, forward-auth SSO domain protection, SCIM provisioning, build concurrency, and the auto-generated @dokploy/cli (604 commands incl. read-logs). Uses the official @dokploy/mcp server (secret fields are redacted by default since 0.30.0) plus debugging-focused slash commands including /compose-logs.
8 skills · 14 commands · 1 agent · 1 MCP server
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
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
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
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
Product, legal, and business specialists - product strategy, licensing, project management, UX research
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
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.