diff --git a/CLAUDE.md b/CLAUDE.md index 5dd077b75..75fb057be 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -124,8 +124,6 @@ If you're new to this repo and want to build your own consumer app or POC, follo | `/wb.create-template ` | Scaffold a new diagram template — asks for target app (default `demo`) | | `/wb.add-execution-handler ` | Wire a node type into execution-core + worker registry (global pipeline, no target) | | `/wb.run-locally` | Bring up the stack — Path A (`pnpm dev:demo`) or Path B (infra + backend + worker + AI Studio frontend) | -| `/wb.task` | Fetch assigned ClickUp tasks via MCP and recommend one to pick up | -| `/wb.task WB-42` | Pick up a specific task with an inline plan | | `/wb.changeset ""` | Add a changeset for SDK changes (`patch` / `minor` / `major`) — required before merging consumer-visible changes to `packages/sdk/**` | ### Releasing `@workflowbuilder/sdk` @@ -168,15 +166,3 @@ The skills under `.claude/commands/wb.*.md` mix three kinds of content: When executing a skill, if a snippet contradicts the canonical reference (or the live SDK source), **canonical wins**. Snippets are starting points; live code is truth. **Self-heal**: if you spot drift while executing a skill, refresh the affected snippet in the skill file as part of your change. Bundle it with the user's task in the same commit (or a follow-up commit titled `docs: refresh /wb. snippet for `). Frequent small refreshes are healthy — stale snippets accumulate friction. - -### ClickUp MCP - -ClickUp MCP is configured for this project in `.mcp.json` using the official remote server at `https://mcp.clickup.com/mcp`. - -First-time setup in Claude Code: - -1. Open a Claude Code session in this repo. -2. Run `/mcp`. -3. Authenticate the `clickup` server via the OAuth flow. - -The project provides a `/wb.task` wrapper command that uses ClickUp MCP to fetch assigned tasks or a specific task by ticket.