planr

Plugin planr from marketplace openplanr in openplanr/marketplace. Commands read from the repo's manifest — 2 days ago.

Skills (30)

• artifact

  Open, share, import, or export an OpenPlanr diagram, design, or HTML artifact review. Use when feedback must move between a local artifact and its review board.

• browser-qa

  Run practical browser-backed QA against real routes, forms, viewports, accessibility, console, and network behavior. Use for UI, authentication, session, navigation, or browser-network changes.

• ceo-review

  Produce a grounded strategy and finance review for an Operate cycle. Use when direction, runway, margin, investment, or cost of delay needs a CEO lens.

• chair-review

  Synthesize an Operate cycle into a prioritized decision queue and action plan. Use after specialist reviews when leadership needs one coherent brief.

• challenger-review

  Challenge an Operate cycle's claims, alternatives, downside, and confidence. Use when assumptions or executive consensus need an independent stress test.

• cmo-review

  Produce a grounded market and growth review for an Operate cycle. Use when acquisition, positioning, demand, retention, or missing measurement needs a CMO lens.

• connect

  Report which chat, project tracker and source control connections the host has, and guide connecting the missing ones through the host. Use when the user wants to connect a service for OpenPlanr or asks what is connected.

• coo-review

  Produce a grounded operations and customer-health review for an Operate cycle. Use when readiness, service delivery, capacity, or customer health needs a COO lens.

• cpo-review

  Produce a grounded product and activation review for an Operate cycle. Use when customer value, activation, prioritization, or adoption needs a CPO lens.

• cto-review

  Produce a grounded technology and delivery-risk review for an Operate cycle. Use when architecture, reliability, security, or execution risk needs a CTO lens.

• dashboard

  Start or inspect the loopback-only OpenPlanr planning dashboard. Use when the user wants to view local planning or Operate state in the browser.

• delegate

  Coordinate an explicitly requested implementation with Claude Code, Codex or Cursor, then independently review and integrate its observed changes. Use when the user asks another coding agent to implement.

• design-loop

  Compare three materially different product design directions in a live review studio, collect pins and ratings, and develop the selected direction. Use for visual alternatives, comparison or a remix.

• design-review

  Review and revise an existing product design using stable board pins and scoped browser-verified changes. Use for focused improvements while preserving unrelated screens and feedback.

• design

  Design a polished product interface through adaptive consultation, a shared canvas/prototype/walkthrough studio, and an implementation-ready specification. Use for a new design or an existing interface that needs a coherent direction.

• diagram

  Create, edit, inspect, verify, or rerender professional offline diagrams. Use for architecture, process, sequence, data, state, or relationship visuals from intent or source.

• doctor

  Diagnose OpenPlanr CLI, pipeline, runtime-adapter, installation, and lock health. Use when setup, discovery, versions, generated assets, or runtime behavior seems wrong.

• investigate

  Diagnose a bug, regression, error, or unexplained behavior and optionally implement a bounded fix. Use for root-cause investigation, including before any fix, not planned feature delivery.

• land

  Assess release readiness and prepare or inspect an OpenPlanr landing sequence. Use after implementation and checks are complete, before merge, publication, or deployment.

• openplanr

  Route a planning, specification, delivery, delegation, design, review, diagram, release, or operating request to the best OpenPlanr skill. Use when the right skill is unclear or the request spans several.

• operate

  Run a focused operating review across seven executive lenses and produce a decision and action brief. Use for periodic product or company-level leadership review.

• plan-review

  Review an OpenPlanr plan for product, engineering, design, and developer-experience problems. Use after planning and before implementation to improve the plan.

• plan

  Turn a Protocol-compatible specification or product intent into schema-compatible OpenPlanr stories and implementation tasks. Use for planning and decomposition, not implementation.

• release

  Choose and maintain a product's versioning scheme, classify shipped changes, and write user-facing changelogs or release notes. Use for SemVer or CalVer decisions, version bumps, release cadence, and preparing a versioned release after landing.

• share

  Share a status report, sprint note or release notes with the team as a chat message draft that the user approves and sends. Use when the user asks to post a planning update to chat.

• ship

  Implement an OpenPlanr plan, specification, task, or clearly stated request end to end in the current repository. Use when the user asks to build, implement, fix, finish, or ship local work, or to plan and implement an accepted change. Invoke before editing files for the requested change. Not for pl

• spec

  Shape vague product or engineering intent into a clear, measurable Protocol-compatible specification grounded in the current repository. Use when requirements need clarification before planning or implementation.

• sprint

  Refine every open backlog item against the code and the calendar, refute the picks, and select a sprint that fits capacity and the release cut. Use before a cut or sprint; not for decomposing one specification or reporting status.

• status

  Inspect project delivery or one feature's pipeline status without changing state. Use when the user asks what is done, pending, blocked, or next.

• sync

  Audit OpenPlanr planning artifacts for graph and protocol drift. Use when statuses, references, schemas, or generated planning views may be inconsistent.

Subagents (9)

• planr-backend

  Implement the server side of a task or request — services, controllers, DTOs, entities, middleware, persistence, and their tests. Use for Tech tasks and other backend work; never for UI files.

• planr-database

  Read a database schema read-only through the host's database connector or a schema snapshot or dump the user supplies, and write the snapshot output/db/schema.json for PostgreSQL, MySQL, MSSQL, SQLite, or MongoDB. Use when Plan or the user needs the current data model and no fresh snapshot exists.

• planr-designer

  Analyze UI mockup images for a feature into a structured ten-section design specification (colors, typography, spacing, components, layout). Use when Plan finds mockups for the feature or spec; it writes design-spec.md only, never code or stories.

• planr-devops

  Generate infrastructure configuration (docker-compose.yml, Dockerfiles, .env.example, CI workflow stubs) that matches the project's stack. Writes files only — never deploys, pushes images, or calls cloud APIs.

• planr-documentation

  Create or update human-readable product and engineering documentation from the request, repository, planning context, and implemented behavior. Cross-references intent and code, flags material drift, and never generates application code.

• planr-entity-scaffold

  Generate ORM entity or DbContext scaffolding (Prisma schema, TypeORM entities, EF Core DbContext, or the stack's equivalent) from a database schema snapshot. Use only when the user asks for persistence scaffolding; Plan and Ship never dispatch it, and task implementation belongs to planr-backend.

• planr-frontend

  Implement the UI side of a task or request — components, pages, layouts, routes, styling, client-side state, form handling, and API wiring, with their tests. Use for UI tasks; never for services, controllers, DTOs, or database code.

• planr-qa

  Review a scoped implementation without editing it and return concise, evidence-based, actionable findings focused on acceptance, security, and correctness.

• planr-specification

  Decompose a functional specification into schema-compatible User Stories and tasks after loading the active stack, design, database, and repository context. Writes planning artifacts only.

Similar plugins