By goworkwize
Generate business-focused feature documentation from code, Linear MCP, and Notion MCP. Saves markdown under the backend Documentation/features directory.
npx claudepluginhub goworkwize/wize-docExplore the Workwize codebase to find files relevant to a feature. Returns a structured analysis of business logic, endpoints, models, and key rules found. Used internally by the wize-doc agent.
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.
Write business-focused feature documentation using code analysis and optional external context (Linear, Notion). Saves markdown to wize-back/Documentation/features/. Used internally by the wize-doc agent.
Multi-LLM documentation review for catching inconsistencies, codebase mismatches, and gaps. Supports Opus, GPT, and Gemini in parallel with synthesis and guided resolution.
Documentation agents — technical writer, documentation architect
Upstash Context7 MCP server for up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your LLM context.
Access official Microsoft documentation, API references, and code samples for Azure, .NET, Windows, and more.
Connect to Atlassian products including Jira and Confluence. Search and create issues, access documentation, manage sprints, and integrate your development workflow with Atlassian's collaboration tools.
AI-powered wiki generator for code repositories. Generates comprehensive, Mermaid-rich documentation with dark-mode VitePress sites, onboarding guides, deep research, and source citations. Inspired by OpenDeepWiki and deepwiki-open.
External network access
Connects to servers outside your machine
Share bugs, ideas, or general feedback.
Cursor + Claude Code plugin to produce business-focused feature documentation from code, Linear (MCP), and Notion (MCP). Output is written to wize-back/Documentation/features/<kebab-case>.md in the Workwize repo (adjust if your backend root differs).
The plugin declares two hosted MCP servers (OAuth):
| Server | URL | Notes |
|---|---|---|
| linear | https://mcp.linear.app/mcp | Linear MCP docs |
| notion | https://mcp.notion.com/mcp | Notion MCP docs |
After enabling the plugin, complete authentication in your client (e.g. Cursor MCP panel; Claude Code /mcp).
Claude Code alternative install (per vendor docs):
claude mcp add --transport http linear-server https://mcp.linear.app/mcp
claude mcp add --transport http notion https://mcp.notion.com/mcp
If you manage MCP only via the plugin, rely on .mcp.json (referenced from .cursor-plugin/plugin.json).
Clients that only support stdio can bridge with npx -y mcp-remote <url> (see Linear/Notion docs).
.cursor-plugin/plugin.json.claude-plugin/plugin.json + .mcp.jsonskills/code-explorer/SKILL.md, skills/doc-writer/SKILL.mdagents/wize-doc.mdcommands/document.mdInstall or symlink the plugin under your project’s .claude/plugins/ (or enable it in .claude/settings.json) per Claude Code plugins.
If the plugin does not show up, Claude Code sometimes fails to detect local plugins. Run the CLI with an explicit plugin directory (from the monorepo root, adjust the path if yours differs):
claude --plugin-dir ./wize-doc/
That loads wize-doc directly from this folder (the one that contains .claude-plugin/plugin.json).
Validate the manifest with Claude Code’s CLI. The path is relative to your shell’s current directory:
…/wize-doc): use ., not ./wize-doc (otherwise it looks for wize-doc/wize-doc and fails).cd /path/to/workwize/wize-doc
claude plugin validate .
…/workwize):cd /path/to/workwize
claude plugin validate ./wize-doc
Coming soon: a marketplace.json for this plugin (or the monorepo) will be added so Claude Code can discover it reliably via a marketplace—until then, use --plugin-dir when auto-detection fails.
Cursor loads local plugins from a real directory under ~/.cursor/plugins/local/. A symlink to your repo often does not work — copy the plugin tree instead.
mkdir -p ~/.cursor/plugins/local
# Replace with your clone path. --exclude '.git' keeps the install small; omit the exclude if you prefer a full copy.
rsync -a --delete --exclude '.git' /absolute/path/to/workwize/wize-doc/ ~/.cursor/plugins/local/wize-doc/
After you change files in the repo, run the same rsync again to refresh the installed copy.
Enable the plugin in Cursor so commands load. In the project’s .cursor/settings.json (or your user settings), add:
{
"plugins": {
"wize-doc": { "enabled": true }
}
}
Restart Cursor; authenticate linear and notion MCPs.
If /document does not appear, try /wize-doc:document (namespaced form).
workwize/.cursor/settings.json (with "wize-doc": { "enabled": true }) applies. Opening only wize-back/ or wize-front/ skips that file unless you copy the same plugins block into User settings or that subfolder’s .vscode/settings.json / .cursor/settings.json.Developer: Reload Window).test -f ~/.cursor/plugins/local/wize-doc/.cursor-plugin/plugin.json && echo OK (not a broken symlink)./document or ask to document a feature (e.g. document auto-restock).Documentation/features → Linear/Notion prompts → code discovery → compose → Write markdown file.Previously a single documentation-mcp bundled list/save/Linear/Notion. That integration is removed. Listing and saving docs use workspace Glob/Write; Linear and Notion use official MCPs only.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claim