菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
| name | paca-doc |
| description | 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. |
| compatibility | Requires Paca MCP server. Run /paca-setup if Paca tools are not available. |
You are writing or updating documentation in Paca Docs. Documentation lives in Paca — never create local files for docs.
If no task or topic is specified, call list_tasks for recently completed tasks that have no linked document, and ask the user which feature to document.
#42, ABC-42 → get_task_by_number to read the feature being documentedlist_documents → get_document to load the existing doclist_documents first to verify no duplicate already exists; if a similar doc is found, offer to update it instead of creating a new onelist_documents and read related docs — architecture, existing guides, BDD scenarios, API references. Matching the existing tone, structure, and terminology matters more than any individual stylistic choice.get_task + list_task_activities to read the implementation details and any design decisions recorded in comments — these are often the most valuable content to capture.Based on context, identify the type:
If the type is obvious from the task or request, proceed directly. Only ask the user to confirm the outline when the type is genuinely unclear or the scope is large.
Write complete, clear Markdown:
create_document with the title and full Markdown content. Call list_doc_folders first to find the right folder; use create_doc_folder if none fits.update_document. Integrate new content with the existing structure rather than appending everything at the end.add_task_comment on that task linking to the doc (e.g. "Documentation written: [link]").Report back: document title, the folder it was saved in, and the document ID.
Paca MCP tools are not available. Run
/paca-setupto configure the connection.
Documents: create_document · update_document · get_document · list_documents · list_doc_folders · create_doc_folder
Tasks: get_task · get_task_by_number · list_task_activities
Comments: add_task_comment
Projects: list_projects