Claude
Skills
Sign in
Back

pp-plane

Included with Lifetime
$97 forever

Printing Press CLI for Plane. The Plane REST API Visit our quick start guide and full API documentation at [developers.plane.so](https://developers.

Backend & APIs

What this skill does

<!-- GENERATED FILE — DO NOT EDIT.
     This file is a verbatim mirror of library/project-management/plane/SKILL.md,
     regenerated post-merge by tools/generate-skills/. Hand-edits here are
     silently overwritten on the next regen. Edit the library/ source instead.
     See the repository agent guide, section "Generated artifacts: registry.json, cli-skills/". -->

# Plane — Printing Press CLI

## Prerequisites: Install the CLI

This skill drives the `plane-pp-cli` binary. **You must verify the CLI is installed before invoking any command from this skill.** If it is missing, install it first:

1. Install via the Printing Press installer. It defaults binaries to `$HOME/.local/bin` on macOS/Linux and `%LOCALAPPDATA%\Programs\PrintingPress\bin` on Windows:
   ```bash
   npx -y @mvanhorn/printing-press-library install plane --cli-only
   ```
2. Verify: `plane-pp-cli --version`
3. Ensure the reported install directory is on `$PATH` for the agent/runtime that will invoke this skill.

If the `npx` install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer):

```bash
go install github.com/mvanhorn/printing-press-library/library/project-management/plane/cmd/plane-pp-cli@latest
```

If `--version` reports "command not found" after install, the runtime cannot see the binary directory on `$PATH`. Do not proceed with skill commands until verification succeeds.

## Command Reference

**assets** — **File Upload & Presigned URLs**

Generate presigned URLs for direct file uploads to cloud storage. Handle user avatars, cover images, and generic project assets with secure upload workflows.

*Key Features:*
- Generate presigned URLs for S3 uploads
- Support for user avatars and cover images
- Generic asset upload for projects
- File validation and size limits

*Use Cases:* User profile images, project file uploads, secure direct-to-cloud uploads.

- `plane-pp-cli assets create-generic-upload` — Generate presigned URL for generic asset upload
- `plane-pp-cli assets create-user-upload` — Generate presigned URL for user asset upload
- `plane-pp-cli assets delete-user` — Delete user asset. Delete a user profile asset (avatar or cover image) and remove its reference from the user profile.
- `plane-pp-cli assets get-generic` — Get presigned URL for asset download
- `plane-pp-cli assets update-generic` — Update generic asset after upload completion
- `plane-pp-cli assets update-user` — Mark user asset as uploaded

**invitations** — Manage invitations

- `plane-pp-cli invitations workspaces-create` — Create a workspace invite
- `plane-pp-cli invitations workspaces-destroy` — Delete a workspace invite
- `plane-pp-cli invitations workspaces-list` — List all workspace invites for a workspace
- `plane-pp-cli invitations workspaces-partial-update` — Update a workspace invite
- `plane-pp-cli invitations workspaces-retrieve` — Get a workspace invite by ID

**issues** — Manage issues

- `plane-pp-cli issues get-workspace-work-item` — Retrieve a specific work item using workspace slug, project identifier, and issue identifier.
- `plane-pp-cli issues search-work-items` — Perform semantic search across issue names, sequence IDs, and project identifiers.

**members** — **Team Member Management**

Manage team members, roles, and permissions within projects and workspaces. Control access levels and track member participation.

*Key Features:*
- Invite and manage team members
- Assign roles and permissions
- Control project and workspace access
- Track member activity and participation

*Use Cases:* Team setup, access control, role management, collaboration.

- `plane-pp-cli members` — Retrieve all users who are members of the specified workspace.

**projects** — **Project Management**

Create and manage projects to organize your development work. Configure project settings, manage team access, and control project visibility.

*Key Features:*
- Create, update, and delete projects
- Configure project settings and preferences
- Manage team access and permissions
- Control project visibility and sharing

*Use Cases:* Project setup, team collaboration, access control, project configuration.

- `plane-pp-cli projects create` — Create a new project in the workspace with default states and member assignments.
- `plane-pp-cli projects delete` — Permanently remove a project and all its associated data from the workspace.
- `plane-pp-cli projects list` — Retrieve all projects in a workspace or get details of a specific project.
- `plane-pp-cli projects retrieve` — Retrieve details of a specific project.
- `plane-pp-cli projects update` — Partially update an existing project's properties like name, description, or settings.

**stickies** — Manage stickies

- `plane-pp-cli stickies create-sticky` — Create a new sticky in the workspace
- `plane-pp-cli stickies delete-sticky` — Delete a sticky by its ID
- `plane-pp-cli stickies list` — List all stickies in the workspace
- `plane-pp-cli stickies retrieve-sticky` — Retrieve a sticky by its ID
- `plane-pp-cli stickies update-sticky` — Update a sticky by its ID

**users** — **Current User Information**

Get information about the currently authenticated user including profile details and account settings.

*Key Features:*
- Retrieve current user profile
- Access user account information
- View user preferences and settings
- Get authentication context

*Use Cases:* Profile display, user context, account information, authentication status.

- `plane-pp-cli users` — Retrieve the authenticated user's profile information including basic details.

**work-items** — **Work Items & Tasks**

Create and manage work items like tasks, bugs, features, and user stories. The core entities for tracking work in your projects.

*Key Features:*
- Create, update, and manage work items
- Assign to team members and set priorities
- Track progress through workflow states
- Set due dates, estimates, and relationships

*Use Cases:* Bug tracking, task management, feature development, sprint planning.

- `plane-pp-cli work-items get-workspace-2` — Retrieve a specific work item using workspace slug, project identifier, and issue identifier.
- `plane-pp-cli work-items search-2` — Perform semantic search across issue names, sequence IDs, and project identifiers.


### Finding the right command

When you know what you want to do but not which command does it, ask the CLI directly:

```bash
plane-pp-cli which "<capability in your own words>"
```

`which` resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code `0` means at least one match; exit code `2` means no confident match — fall back to `--help` or use a narrower query.

## Auth Setup
Run `plane-pp-cli auth setup` to print the URL and steps for getting a key (add `--launch` to open the URL). Then set:

```bash
export PLANE_API_KEY_AUTHENTICATION="<your-key>"
```

Or persist it in `~/.config/plane-pp-cli/config.toml`.

Run `plane-pp-cli doctor` to verify setup.

## Agent Mode

Add `--agent` to any command. Expands to: `--json --compact --no-input --no-color --yes`.

- **Pipeable** — JSON on stdout, errors on stderr
- **Filterable** — `--select` keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:

  ```bash
  plane-pp-cli projects list --agent --select id,name,status
  ```
- **Previewable** — `--dry-run` shows the request without sending
- **Offline-friendly** — sync/search commands can use the local SQLite store when available
- **Non-interactive** — never prompts, every input is a flag
- **Explicit retries** — use `--idempotent` only when an already-existing create should count as success, and `--ignore-missing` only when a missing delete target should count as success

### Response envelope

Commands that read from the local store or the API wrap output in a provenance envelope:

```json
{
  "meta": {"source": "live" | "loc

Related in Backend & APIs