Update to AB

{
  "description": "Write, update, and organize project documents (wiki pages) in AB Projects (ActionBridge), and link them to the tasks they support. Use when the user wants to document a decision, write up meeting notes, create a guide or spec as a project document, update an existing wiki page, or attach a document to a task.",
  "included_files": [],
  "name": "ab-wiki-writer",
  "skill_md_contents": "---\r\nname: ab-wiki-writer\r\ndescription: Write, update, and organize project documents (wiki pages) in AB Projects (ActionBridge), and link them to the tasks they support. Use when the user wants to document a decision, write up meeting notes, create a guide or spec as a project document, update an existing wiki page, or attach a document to a task.\r\n---\r\n\r\n# Project documents (wiki) in AB Projects\r\n\r\nDocuments are Markdown pages per project, versioned on every save, with their own discussion threads and task links.\r\n\r\n## Before writing\r\n\r\n1. Resolve the project via `ab_get_my_projects` (ask if ambiguous).\r\n2. `ab_get_wiki_tree` for that project — see the existing folder structure and check whether a page on this topic already exists. **Prefer updating an existing page over creating a near-duplicate.**\r\n3. If updating, `ab_get_wiki_article` first and edit from the real current content — never overwrite from memory.\r\n\r\n## Creating\r\n\r\n`ab_create_wiki_article` with `project_id`, `title`, `content` (Markdown), and a `parent_path` that fits the existing tree (e.g. `/guides`); add `tags` for findability. Structure content for a team, not a chat: a one-paragraph summary at top, then headed sections, decisions stated with their why, and open questions listed explicitly at the end.\r\n\r\n## Updating\r\n\r\n`ab_update_wiki_article` with `article_id`, the **complete** new `content` (a save replaces the whole body and creates a new version), and an `edit_note` saying what changed — the note is the team's change log. Preserve sections you weren't asked to touch.\r\n\r\n## Linking to tasks\r\n\r\nWhen a document supports specific work — a spec for a feature task, notes from the meeting that spawned tasks — connect them: `ab_link_task_wiki` with `task_id` and `wiki_article_id` (idempotent). Mention the link in your summary so the user knows navigation exists in both directions. `ab_unlink_task_wiki` undoes only the association; it never deletes anything.\r\n\r\n## Discussion vs. content\r\n\r\nFeedback about a document goes to its thread via `ab_add_wiki_comment`, not into the body. Suggest a comment when the user's input is commentary (\"I think this section is outdated\") rather than replacement text.\r\n\r\n## Refusals\r\n\r\nViewer-role members and users without a seat can't write documents — if a tool refuses, explain that plainly rather than retrying (seats: Settings → Manage licenses).\r\n"
}