Renamed workflow to make it more obvious what it is

2026-02-12 11:00:35 +00:00
parent 442b6eafcf
commit c03d05734a
1 changed files with 0 additions and 0 deletions
@@ -0,0 +1,121 @@
+---
+name: "Kanban"
+description: "Manage Planka project boards using the pcli CLI"
+category: Workflow
+tags: [workflow, kanban, planka, project-management]
+---
+
+Manage Planka project boards using the `pcli` CLI. Use the kanban skill for detailed command reference.
+
+## Prerequisites
+
+Before running any commands, verify the environment is ready:
+
+```bash
+// turbo
+pcli status
+```
+
+If this fails, ensure `PLANKA_URL` and `PLANKA_API_KEY` environment variables are set and `pcli` is in PATH.
+
+---
+
+## How to Use
+
+**Input**: The argument after `/kanban` is what the user wants to do. Could be:
+- A status check: "show me all boards" or "what's on my board"
+- A card operation: "create a card for fixing the login bug"
+- A board query: "list all cards in the backlog"
+- A move: "move card X to done"
+- A bulk operation: "move all cards from In Progress to Done"
+- Nothing (show overall status)
+
+---
+
+## Responding to Requests
+
+### 1. Understand the request
+
+Map the user's intent to `pcli` commands. Use `pcli status` for overview requests. For specific operations, identify the resource (project, board, card, list, label, task, comment) and action (list, get, create, update, delete, move).
+
+### 2. Discover IDs when needed
+
+Most commands require IDs. Discover them by querying first:
+
+```bash
+# Find boards
+pcli board list | jq '.data[] | {id, title}'
+
+# Find lists on a board
+pcli board get <board-id> | jq '.data.included.lists[] | {id, title}'
+
+# Find cards on a list or board
+pcli card list --board <board-id> | jq '.data[] | {id, name}'
+pcli card list --list <list-id> | jq '.data[] | {id, name}'
+```
+
+Always use `jq` to extract and format output for readability.
+
+### 3. Execute the operation
+
+Run the appropriate `pcli` command. For create/update/delete operations, confirm with the user before executing unless the intent is unambiguous.
+
+### 4. Report results
+
+Show the user a concise summary of what happened. Use tables or formatted output when listing multiple items.
+
+---
+
+## Command Quick Reference
+
+| Resource | Commands |
+|----------|----------|
+| **Status** | `pcli status` |
+| **Projects** | `list`, `get` |
+| **Boards** | `list`, `get`, `actions` |
+| **Cards** | `list`, `get`, `create`, `update`, `delete`, `duplicate`, `move`, `assign`, `unassign`, `add-label`, `remove-label`, `actions` |
+| **Comments** | `list`, `create`, `update`, `delete` |
+| **Task Lists** | `create`, `get`, `update`, `delete` |
+| **Tasks** | `create`, `update`, `delete` |
+| **Labels** | `create`, `update`, `delete` |
+
+---
+
+## Common Patterns
+
+### Create a card with a checklist
+
+```bash
+CARD_ID=$(pcli card create --list <list-id> --name "Task" | jq -r '.data.id')
+TL_ID=$(pcli task-list create --card $CARD_ID --name "Steps" | jq -r '.data.id')
+pcli task create --task-list $TL_ID --name "Step 1"
+pcli task create --task-list $TL_ID --name "Step 2"
+```
+
+### Move all cards between lists
+
+```bash
+pcli card list --list <source-list-id> | jq -r '.data[].id' | while read id; do
+  pcli card move $id --list <target-list-id>
+done
+```
+
+### Extract IDs from output
+
+```bash
+# Single object
+pcli card create --list <id> --name "X" | jq -r '.data.id'
+
+# Array
+pcli card list --board <id> | jq -r '.data[].id'
+```
+
+---
+
+## Guardrails
+
+- **Discover before acting** - Always query for IDs rather than guessing
+- **Confirm destructive actions** - Ask before delete or bulk move operations
+- **Use jq for output** - Parse JSON responses with `jq` for clean, readable results
+- **Show context** - When listing cards, include the list/board name for context
+- **Global flags** - All commands accept `--format json|table` for output format