Paca
ProductivitypacaPaca is an Agent Skill for productivity published in the Paca-AI/paca repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Interact with Paca project management using MCP tools. Use when tracking tasks, writing docs, planning sprints, managing work items, creating bugs or features, viewing the board, or handling any project-management request involving Paca. Routes to specialized skills for complex workflows like epics, sprint planning, and task execution.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Paca-AI/paca/blob/HEAD/skills/paca/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/paca, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
You have Paca MCP tools. Handle the request by using those tools directly — never create local files for tasks, docs, or to-do lists.
Step 0 — Route to a specialized skill if appropriate
If the request clearly matches one of these, let the user know — they'll get a better result with the specialized skill:
| If the user wants to... | Suggest |
|---|---|
| Turn requirements into a full epic with child stories | /paca-epic <requirements> |
| Clarify or improve a vague task or spec | /paca-clarify #<number> |
| Break a task into smaller sub-tasks | /paca-breakdown #<number> |
| Plan a sprint from the backlog | /paca-sprint |
| Estimate story points for tasks | /paca-estimate #<number> |
| Set priorities across the backlog | /paca-prioritize |
| Execute a task end-to-end | /paca-do #<number> |
| Test or verify a task | /paca-test #<number> |
| Write or update documentation | /paca-doc #<number> |
| Automate a process — auto-assignment, status chaining, task dependencies | /paca-workflow <goal> |
If it's a simple or mixed request (e.g. "create a task for X", "what's in the sprint", "mark #7 done"), just handle it directly below.
Step 1 — Scan for a task reference
Scan the user's message for any of these patterns, wherever they appear:
| Pattern | Example | How to resolve |
|---|---|---|
#<number> or number in task context | #42, close #7, task 42 is done | get_task_by_number(projectId, 42) |
PREFIX-<number> | ABC-42, PAC-7 | list_projects → match task_id_prefix → get_task_by_number |
| Paca URL | http://…/projects/{id}/tasks/{id} | parse both IDs → get_task(projectId, taskId) |
| UUID | 550e8400-e29b-41d4-a716-446655440000 | get_task(projectId, uuid) |
If a reference is found, fetch that task first, then apply the action the user is asking for.
Step 2 — Infer the action
| What the user wants | Tools to use |
|---|---|
| Track work — bug, feature, to-do, ticket, chore | create_task / update_task / list_tasks |
| Write content — guide, spec, design, BDD, SDD, notes | write_doc |
| See status — board, sprint, what's in progress | list_sprints + list_tasks |
| Plan an iteration — sprint, milestone | create_sprint / update_sprint |
| Comment or annotate an existing task | add_task_comment |
| Close / complete work | update_task (set to done status) |
| Break work into pieces | create_task × N, each referencing the parent |
| Write or update documentation | write_doc |
Step 3 — Get the project if needed
If no project is in context, call list_projects and pick the most relevant one based on the message. Only ask the user if it is genuinely ambiguous between two equally plausible candidates.
Step 4 — Act and confirm
Execute the tool call(s), then report back: task/doc number, title, and any relevant ID or link.
Examples
| User message | What you do |
|---|---|
fix login redirect bug | create_task titled "Fix login redirect bug" |
write the API authentication design doc | write_doc with a structured draft |
do this task ABC-123 | find project "ABC" → get_task_by_number(123) → start/act on task |
close #42 | get_task_by_number(42) → update_task status: done |
I finished PAC-99, mark it done | update_task #99 → status: done |
http://…/tasks/uuid — add comment: blocked | get_task from URL → add_task_comment "blocked" |
what's in the current sprint? | list_sprints → list_tasks filtered to active sprint |
review PR, update staging, write release notes | create_task × 3, one per item |
If Paca MCP is not connected
Paca MCP tools are not available. Run
/paca-setupto configure the connection.
Do not create local files as a fallback.
Tool reference
Tasks: create_task · list_tasks · get_task · get_task_by_number · update_task · delete_task
Documents: list_docs · read_doc · write_doc · delete_doc
Sprints: create_sprint · list_sprints · get_sprint · update_sprint · complete_sprint
Projects: list_projects · get_project · create_project · update_project
Comments: add_task_comment · update_task_comment · list_task_activities