菜单
Plan a Paca sprint by selecting tasks from the backlog, detecting carryover from the previous sprint, inferring velocity from past sprints, and assigning tasks to the sprint. Use when starting a new sprint, filling an upcoming sprint, reviewing sprint capacity, or setting the sprint goal.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
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.
基于 SOC 职业分类
| name | paca-sprint |
| description | Plan a Paca sprint by selecting tasks from the backlog, detecting carryover from the previous sprint, inferring velocity from past sprints, and assigning tasks to the sprint. Use when starting a new sprint, filling an upcoming sprint, reviewing sprint capacity, or setting the sprint goal. |
| compatibility | Requires Paca MCP server. Run /paca-setup if Paca tools are not available. |
You are planning a sprint in Paca. Use Paca MCP tools throughout — never create local files.
If no sprint is specified, default to planning the next upcoming sprint for the most active project.
list_projects and identify the relevant project.list_documents and search for documents with keywords like "roadmap", "goals", "OKR", "retrospective", or "planning". Read the most relevant ones with get_document. What the last sprint achieved and what the project's current goals are will shape which tasks belong in this sprint.list_sprints to see existing sprints (active, upcoming, completed).list_tasks (backlog or unassigned filter) to see the candidate task pool.Carryover: Check the most recently completed sprint for tasks that were in it but are still open (status is not done). Flag these — carryover tasks typically get priority in the next sprint.
Velocity: Look at the last 2–3 completed sprints. Sum the story point estimates of tasks that were marked done. Use the average as the default capacity if the user hasn't stated one.
From the user's message and context:
Rank backlog tasks and recommend a set that fits within capacity:
/paca-estimate or /paca-clarify on them before committingPresent the proposed list with a total estimated points and the sprint goal. Ask the user to confirm, swap, or adjust before applying.
Once confirmed:
create_sprint (name, goal, startDate, endDate)update_task (set sprintId)update_sprintOptionally create or update a sprint planning note in Paca Docs (create_document / update_document) with the sprint goal, task list, capacity, and velocity reference.
Report back: sprint name, dates, task count, total estimate, capacity used, and sprint goal.
Paca MCP tools are not available. Run
/paca-setupto configure the connection.
Sprints: list_sprints · get_sprint · create_sprint · update_sprint · complete_sprint
Tasks: list_tasks · get_task · update_task · bulk_move_tasks
Documents: list_documents · get_document · create_document · update_document
Projects: list_projects