Update to DocuWriter.ai

{
  "description": "Explains repository connection, Full Tree Documentation, Spaces, on-demand repository documentation reviews, and Autopilot. Use for generating, organizing, updating from repository changes, or maintaining project documentation.",
  "included_files": [],
  "name": "docuwriter-documentation-lifecycle",
  "skill_md_contents": "---\nname: docuwriter-documentation-lifecycle\ndescription: Explains repository connection, Full Tree Documentation, Spaces, on-demand repository documentation reviews, and Autopilot. Use for generating, organizing, updating from repository changes, or maintaining project documentation.\n---\n\n# From repository to maintained documentation\n\nDocuWriter's main workflow takes a team from source code to a maintained, searchable documentation system:\n\n1. **Connect the code.** Authorize a GitHub, GitLab, Bitbucket, or Azure DevOps connection, then choose the repository, branch, and source paths to document.\n2. **Generate with Full Tree Documentation.** DocuWriter analyzes the selected source and proposes a documentation tree covering the project's architecture, modules, services, APIs, workflows, and implementation details. The team reviews or edits the tree before generation. DocuWriter then creates connected pages that explain related components in context.\n3. **Work in Spaces.** The generated pages live in a navigable Space. Engineers can search and ask questions across the documentation, edit or add their own knowledge, collaborate, and share or publish the result. A Space can bring documentation from multiple repositories together.\n4. **Maintain what changed.** Autopilot examines changes in connected repositories, identifies pages they may affect, and drafts targeted updates. Engineers can review, refine, accept, or reject the suggestions. Controlled automatic application is available for configured workflows.\n\nThe team should review generated pages before relying on or publishing them. Autopilot requires a connected repository and a configured Space link to respond to later code changes.\n\n## Composer mentions and existing tools\n\nIn supported desktop hosts, users can select accessible documents through native composer mentions before asking a question. Native composer mentions are not available on mobile. The host, not the model, invokes the app-only `search-documentation-mentions` tool to match document titles and Space names lexically, returning up to 20 recent documents for an empty query. Distinguish duplicate titles using the Space and selected URI. Read the selected private `docuwriter://spaces/{space_id}/documents/{document_id}` resource through `resources/read` as `text/markdown`; mention lookup and reads have no side effects.\n\nOther supported workflows remain ordinary prompt-based tool requests and do not require a mention. Use the existing generation tools for supplied code and supported repository workflows. Use `search-space-documents` or `global-search` for semantic content search; mention lookup does not replace them. To list pending Autopilot suggestions, discover an accessible Space with `list-spaces` and call `list-space-suggestions` with `status: \"pending\"`. Report the returned summary and status without promising a full before/after preview. Do not apply, discard, or snooze suggestions unless the user explicitly requests and authorizes the separate write tool. Attaching a mention never authorizes a write.\n\n## Review repository changes on demand\n\nWhen the user wants existing documentation checked against repository changes, use `inspect-documentation-update` before starting paid work. Infer the task from its meaning, not a particular phrase. Resolve the numeric Space ID with authorized discovery (`list-spaces`); ask for clarification when the Space or intent is ambiguous. A selected document or current browser page does not grant management permission.\n\nInspection reads provider state but queues no work, reserves no credits and invokes no models. Explain Space, repository branch, baseline and target commit, mode, affected or selected pages and rationale, maximum credits and available credits. Preserve any earlier named-page scope by resolving its actual page IDs. Page selection is supported only for first/full reviews; do not submit a partial selection for a diff review or silently broaden it. Omitting selection includes all reviewable pages.\n\nOnly after the user explicitly authorizes that scope and maximum cost, call `start-documentation-update` with the same Space ID and opaque `review_quote` from inspection. A quote, tool annotation, mention or generic request to update docs is not consent to spend credits. Quotes expire after 30 minutes and bind the requester, payer, source, commits, page scope/content and maximum cost. If approval facts changed, inspect again and request approval of the new facts. Repeating the same accepted quote returns the same authorized run, including terminal runs; it does not start or resume another paid attempt. A different active run returns a conflict and browser link.\n\nUse `get-documentation-update-status` with the Space ID and optional run ID for persisted progress, pending-change counts, credit usage and the existing browser review URL. Status never starts work or polls providers. Report “review queued/running” or the actual returned state, never “documentation updated.” Preserve the returned scope and credit explanations: settled review usage is not the account balance; a maximum review cost is not a new-page generation allowance. Paused or failed runs require browser guidance; do not retry automatically.\n\nOpen the returned browser URL for diff review, applying or rejecting changes, approving new pages, resuming or ending the run. These manual review decisions are not exposed through MCP. Existing Autopilot suggestion tools operate a separate workflow and must not be substituted for manual review decisions. Editorial content edits use `update-space-document`; Autopilot configuration uses repository-link tools; new documentation uses the appropriate generation tools. ZIP sources are excluded; follow returned provider reconnect, entitlement, permission, busy-work or credit guidance.\n"
}