paca-do
paca-do executes tasks from the Paca project management system end-to-end by reading task details and acceptance criteria, understanding project context through documentation, completing the work (code, writing, or research), and updating task status with results. Use this skill when assigned a specific Paca task or when you need to identify and work on in-progress tasks in the current sprint, as it automatically loads project context before taking action.
git clone --depth 1 https://github.com/Paca-AI/paca /tmp/paca-do && cp -r /tmp/paca-do/skills/paca-do ~/.claude/skills/paca-doSKILL.md
You are executing a task from Paca — reading it, understanding context, doing the work, and updating the record. Use Paca MCP tools throughout — never create local files for task records or documentation. **If no task is specified**, call `list_tasks` filtered to in-progress tasks in the current sprint. Show them and ask which to work on. --- ## Step 1 — Load task and project context 1. Resolve the task reference from the user's message using `get_task_by_number` or `get_task`. 2. **If the task has no acceptance criteria**, stop and ask the user to clarify before starting — or offer to run `/paca-clarify` first. Starting work without a clear "done" condition wastes effort. 3. Call `list_documents` and search for documents relevant to this task — architecture, design specs, BDD scenarios, API references, integration guides. Read before writing any code or content; what's already decided shapes every implementation choice. 4. Call `list_task_activities` to read prior comments and implementation notes — someone may have already investigated this. 5. Note the acceptance criteria from the task description. These are your exit criteria. ## Step 2 — Mark in progress 1. Call `list_task_statuses` to find the "in progress" status. 2. Call `update_task` to set the status. (No confirmation needed — this is a lightweight, reversible status change.) 3. Call `add_task_comment`: "Starting work on this task." ## Step 3 — Do the work Execute based on the task type: - **Code task**: find the relevant source files, read existing tests to understand the expected behavior, implement the change, run the test suite. If you need to understand what "in scope" looks like, the BDD scenarios you read in Step 1 are authoritative. - **Writing task**: draft the content in the response, or create/update a Paca document via `create_document` / `update_document`. Never write to a local file. - **Research / investigation task**: investigate, write findings as a comment via `add_task_comment` or as a Paca doc, then update the task description with the conclusions. - **Review task**: analyse the artifact (PR, document, design), post a structured review as `add_task_comment`. If you discover a blocker or a genuine sub-task that wasn't anticipated, create it in Paca with `create_task` (reference the parent: `Blocked by #<parent>`). Don't silently skip or work around it. ## Step 4 — Update and close 1. Call `add_task_comment` with a completion summary: what was done, what changed, any known caveats or follow-up needed. 2. If any project documentation was affected (README, architecture doc, API reference), update the relevant Paca document with `update_document`. Never write new docs as local files. 3. Call `update_task` to set the status to done (or the next stage — e.g. "review" — if your workflow has one). **What's next:** Consider running `/paca-test #<number>` to verify the implementation against acceptance criteria. Report back: task number, title, summary of what was done, and any new tasks or docs created. --- ## 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` · `update_task` · `create_task` · `list_task_statuses` **Comments:** `add_task_comment` · `list_task_activities` **Documents:** `list_documents` · `get_document` · `update_document` · `create_document` **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.
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.
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.
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.