paca-prioritize

Agent Skills › Paca-AI/paca › paca-prioritize

paca-prioritize

GitHub

用于在Paca中根据路线图目标、业务价值、紧急度和依赖关系对任务进行优先级排序。支持全量或指定任务，结合战略文档评分，并自动更新优先级标签及理由。

skills/paca-prioritize/SKILL.md Paca-AI/paca

Trigger Scenarios

需要对待办事项进行排序冲刺规划前需要为任务分配明确优先级要求按重要性或紧迫性排名

Install

npx skills add Paca-AI/paca --skill paca-prioritize -g -y

More Options

Use without installing

npx skills use Paca-AI/paca@paca-prioritize

指定 Agent (Claude Code)

npx skills add Paca-AI/paca --skill paca-prioritize -a claude-code -g -y

安装 repo 全部 skill

npx skills add Paca-AI/paca --all -g -y

预览 repo 内 skill

npx skills add Paca-AI/paca --list

SKILL.md

Frontmatter

{
    "name": "paca-prioritize",
    "description": "Set or adjust priorities across the Paca backlog, aligned to roadmap goals and business value. Use when the backlog needs sorting, before sprint planning, when tasks need explicit Critical\/High\/Medium\/Low priority labels, or when asked to rank work by importance or urgency.",
    "compatibility": "Requires Paca MCP server. Run \/paca-setup if Paca tools are not available."
}

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

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.
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.
Call list_tasks to load the full task set.
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