菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| 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.
#42, ABC-42 → get_task_by_number). If no references, operate on the full backlog.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.
list_tasks to load the full task set.list_sprints to know which tasks are already committed vs. unscheduled.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:
Present the ranked list with one-line reasoning per task. Ask the user to confirm or adjust before writing.
For each confirmed priority, call update_task:
priority field to the agreed valueReport back: full updated priority list as a table (task number · title · priority).
Paca MCP tools are not available. Run
/paca-setupto configure the connection.
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.