From wize-doc
Revise existing feature documentation using a change description and optional new context (code analysis, Linear, Notion). Preserves unchanged sections verbatim. Used internally by the /document command update flow.
How this skill is triggered — by the user, by Claude, or both
Slash command
/wize-doc:doc-updaterThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Revise an existing feature documentation file based on what changed.
Revise an existing feature documentation file based on what changed.
From the command:
Read the existing doc in full. Identify the sections present (headings and their content).
Based on the user's change description and any new context provided, identify which sections need updating:
Sections not touched by the change should be preserved verbatim.
For each affected section:
If critical information is missing or the change description is ambiguous, ask the user before rewriting.
Write the complete updated document back to the same file path (overwrite).
Keep all unaffected sections exactly as they were.
Report back:
If the doc's Related Resources section references a Notion page, offer once:
"Doc updated at
<path>. Want me to also update the Notion page?"
Only proceed if the user confirms. Use notion-update-page with the existing page ID.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub goworkwize/wize-doc