paca-prioritize
paca-prioritize ranks and labels tasks in a Paca backlog according to business value, urgency, effort, and dependencies, aligning them to roadmap goals. Use it before sprint planning, when the backlog needs sorting, or when tasks require explicit Critical/High/Medium/Low priority assignments tied to measurable outcomes.
git clone --depth 1 https://github.com/Paca-AI/paca /tmp/paca-prioritize && cp -r /tmp/paca-prioritize/skills/paca-prioritize ~/.claude/skills/paca-prioritizeSKILL.md
You are setting priorities for tasks in Paca. Use Paca MCP tools throughout — never create local files. **If no task is specified**, operate on the full backlog of the most active project. --- ## Step 1 — Load project context 1. Resolve task references from the user's message if given (`#42`, `ABC-42` → `get_task_by_number`). If no references, operate on the full backlog. 2. Call `list_documents` and search for documents titled "roadmap", "goals", "OKR", "strategy", or "release plan". Read the most relevant ones with `get_document`. Priority without a goal to align to is just opinion — the docs anchor your reasoning. - **If no strategy docs exist**, ask the user: "What are the top 3 outcomes you're trying to achieve this quarter?" Use their answer as the alignment anchor. 3. Call `list_tasks` to load the full task set. 4. Call `list_sprints` to know which tasks are already committed vs. unscheduled. ## Step 2 — Score and rank For each task, assess four dimensions: | Dimension | What to look for | |---|---| | **Business value** | How directly it advances the roadmap or improves user outcomes | | **Urgency / risk** | Customer-facing bugs, blockers, compliance deadlines | | **Effort** | Estimated size — high-value + low-effort tasks rank up | | **Dependencies** | Tasks that unblock others rank higher | Assign one of these labels: - **Critical** — blocks a release, breaks production, or is a contractual obligation - **High** — directly advances the top roadmap goal; would be missed by users if delayed - **Medium** — valuable but not time-sensitive; no clear near-term cost to waiting - **Low** — nice-to-have, cleanup, or exploratory; can be deprioritized indefinitely without user impact Present the ranked list with one-line reasoning per task. Ask the user to confirm or adjust before writing. ## Step 3 — Apply priorities For each confirmed priority, call `update_task`: - Set the `priority` field to the agreed value - Optionally append a one-line rationale to the description so the reasoning is preserved and reviewable Report back: full updated priority list as a table (task number · title · priority). --- ## If Paca MCP is not connected > Paca MCP tools are not available. Run `/paca-setup` to configure the connection. --- ## Tool reference **Tasks:** `get_task` · `get_task_by_number` · `list_tasks` · `update_task` **Documents:** `list_documents` · `get_document` **Sprints:** `list_sprints` **Projects:** `list_projects`
Break a large Paca task or epic into smaller, actionable sub-tasks with dependency ordering. Use when decomposing work that is too large to estimate or execute in a single session, when creating an implementation plan, or when a task needs to be split into vertical slices before sprint planning.
Clarify a vague or incomplete Paca task or specification by identifying ambiguities, asking targeted questions, and rewriting the description with explicit acceptance criteria. Use when a task is unclear, missing edge cases, lacks a testable done condition, or when someone asks to improve or flesh out a spec.
Execute a Paca task end-to-end — reading context and acceptance criteria, doing the work (code, writing, research, review), updating task status, and commenting results. Use when asked to start, implement, complete, or work on a specific Paca task. Reads project docs first to understand the codebase and tech stack before acting.
Write or update documentation for a feature, task, or topic in Paca Docs. Use when asked to document a completed feature, write a guide or runbook, update existing docs, create a spec or architecture document, or produce BDD scenarios. Documentation is saved in Paca — never created as local files.
Turn a product requirement or feature description into a structured epic in Paca, with child user stories and a spec document. Use when asked to plan a new feature, break down a high-level requirement into stories, create an epic, or go from "we need X" to a fully structured backlog ready for sprint planning.
Estimate story points for Paca tasks using the Fibonacci scale, calibrated against recently completed reference tasks and project tech stack. Use when tasks are missing estimates, before sprint planning, when the team needs sizing for prioritization, or when asked to size a backlog.
Configure the Paca MCP server for use with Claude Code or Claude Desktop. Use when setting up Paca for the first time, adding or editing the MCP server config, troubleshooting connectivity, or installing the Paca skills globally. Walks the user through prerequisites, config file generation, verification, and optional global skill install.