AugmentClaude
EngineeringDocs

Paca Doc Writer

By Paca-AI· Paca-AI/paca· 0

Write and update documentation for features, guides, and specs in Paca Docs.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/paca-doc-paca-ai/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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.

What this skill does

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.

Step 1 — Load project context

  1. Resolve any reference from the user's message:
    • #42, ABC-42 → get_task_by_number to read the feature being documented
    • Doc title or ID → list_documents → get_document to load the existing doc
    • Free-text topic → list_documents first to verify no duplicate already exists; if a similar doc is found, offer to update it instead of creating a new one
  2. Call list_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.
  3. If documenting a task, call 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.

Step 2 — Identify doc type and draft outline

Based on context, identify the type:

  • Guide / tutorial — step-by-step, outcome-oriented, written for someone doing it for the first time
  • Reference — exhaustive API, config, or CLI reference
  • Architecture / design doc — decisions, tradeoffs, diagrams (as Markdown)
  • BDD / acceptance spec — Gherkin-style scenarios
  • Runbook — operational steps for a known procedure

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.

Step 3 — Write the documentation

Write complete, clear Markdown:

  • Active voice and present tense
  • Code examples and command snippets where they aid understanding
  • Link to related Paca docs by title or task number
  • No "last updated" timestamps, no "Created by Claude" lines — Paca tracks history
  • No placeholder sections ("TBD", "coming soon") — write real content or omit the section

Step 4 — Save to Paca

  • New document: call 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.
  • Existing document: call update_document. Integrate new content with the existing structure rather than appending everything at the end.
  • If the doc is tied to a task, call 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.

If Paca MCP is not connected

Paca MCP tools are not available. Run /paca-setup to configure the connection.

Tool reference

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

Related skills

W

Word Document Editor

anthropics

Create, edit, and format Word documents with tables, images, and tracked changes.

OfficialProprietary. LICENSE.txt has complete terms
A

Ask Questions If Underspecified

trailofbits

Ask clarifying questions before starting work on ambiguous requests.

C

CLAUDE.md Optimizer

daymade

Optimize your CLAUDE.md file for clarity, efficiency, and maintainability.

C

Claude Skills Troubleshooter

daymade

Diagnose and fix plugin installation, enablement, and activation problems.