Update to DocuWriter.ai

{
  "description": "Explains DocuWriter's Full Tree Documentation, Spaces, repository documentation reviews, and Autopilot. Use for product introductions and capability overviews.",
  "included_files": [],
  "name": "docuwriter-overview",
  "skill_md_contents": "---\nname: docuwriter-overview\ndescription: Explains DocuWriter's Full Tree Documentation, Spaces, repository documentation reviews, and Autopilot. Use for product introductions and capability overviews.\n---\n\n# DocuWriter\n\nDocuWriter helps teams generate, manage, and maintain documentation for their software projects. Its core workflow combines Full Tree Documentation, Spaces, and Autopilot.\n\n## What the team gets\n\nFull Tree Documentation analyzes the selected repository source, proposes an outline for the team to review, then generates a connected set of pages about the project. The pages explain architecture, modules, services, APIs, workflows, and implementation details in context. For example, an API is explained alongside the service that owns it. The result is a navigable documentation tree in a Space.\n\nSpaces give teams one place to browse, search, edit, organize, share, and publish those pages, including knowledge added by engineers. A Space can bring documentation from multiple repositories together.\n\nAutopilot watches changes in connected repositories, identifies documentation that may be affected, and drafts focused updates for review. Teams can accept, refine, or reject suggestions, or configure controlled automatic application where appropriate.\n\n## Repository documentation reviews\n\nFor an existing repository-backed Space, `inspect-documentation-update` shows eligible page scope, repository changes and maximum credits without starting work. After the user explicitly approves that scope and maximum cost, `start-documentation-update` starts the quoted paid review. `get-documentation-update-status` returns persisted progress, costs and the browser review link. A quote or attached document is not authorization to spend credits. Applying or rejecting changes, approving new pages, resuming and ending remain browser actions. Use the documentation lifecycle skill for exact scope and consent rules. This workflow differs from editorial edits, new generation and Autopilot configuration.\n\n## Composer mentions\n\nIn supported desktop hosts, users can select an accessible document through native composer mentions before asking a question grounded in its content. Native composer mentions are not available on mobile. The host, not the model, invokes the app-only `search-documentation-mentions` tool for lexical lookup by document title or Space name; an empty query returns up to 20 recent documents. Distinguish duplicate titles by their Space context and use the selected resource URI, not a guessed ID.\n\nThe selected private resource is `docuwriter://spaces/{space_id}/documents/{document_id}` and is read through `resources/read` as `text/markdown` under the connected account's permissions. Mention lookup and reads have no side effects and do not authorize edits or publication. Existing generation, semantic search, suggestion listing, and official-guide workflows remain ordinary prompt-based tool requests and do not require a mention. Use `search-space-documents` or `global-search` for semantic search. Any requested write must use its separate MCP tool after an explicit request and authorization.\n"
}