@brainervirus/workit-cursor 0.8.8 → 0.8.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brainervirus/workit-cursor",
-  "version": "0.8.8",
+  "version": "0.8.10",
   "private": false,
   "description": "Workit Cursor plugin: MCP server, hooks, rules, marketplace manifest (thin over @brainervirus/workit-core)",
   "keywords": [
@@ -39,7 +39,7 @@
     "build": "bun scripts/build.ts"
   },
   "dependencies": {
-    "@brainervirus/workit-core": "^0.8.8",
+    "@brainervirus/workit-core": "^0.8.10",
     "@modelcontextprotocol/sdk": "^1.12.0",
     "zod": "^3.24.0"
   },

package/rules/ask-question-only.mdc

@@ -37,7 +37,7 @@ One AskQuestion per turn when possible. Open-ended free text (no options) may st
 
 After writing a plan, **do not emit** Superpowers' inline text beginning “Two execution options”.
 
-After `workflow_docs_validate` succeeds on the saved spec/plan pair, call Cursor `AskQuestion` with exactly:
+After `workit_docs_validate` succeeds on the saved spec/plan pair, call Cursor `AskQuestion` with exactly:
 
 - Subagent-driven → **unsupported on Cursor** (the MCP rejects it as `unsupported_mode`; use OpenCode `wk-implement`)
 - Inline → execute in this session

package/rules/cursor-todowrite.mdc

@@ -7,8 +7,8 @@ alwaysApply: true
 
 When executing a plan / SDD handoff:
 
-1. MCP `workflow_sdd_context` returns `todos` — call Cursor **TodoWrite** with that array (`merge: false`) before Task 1.
+1. MCP `workit_sdd_context` returns `todos` — call Cursor **TodoWrite** with that array (`merge: false`) before Task 1.
 2. SDD under `docs/<slug>/sdd/` is persistence only — **not** a substitute for the Cursor task list UI.
-3. Per task: `in_progress` before dispatch; `completed` after `workflow_sdd_append_progress`.
+3. Per task: `in_progress` before dispatch; `completed` after `workit_sdd_append_progress`.
 
 Never skip TodoWrite because the SDD ledger exists.

package/rules/no-worktrees.mdc

@@ -16,10 +16,10 @@ alwaysApply: true
 
 ## Required flow (before Task 1)
 
-1. MCP `workflow_resolve_branch` with spec + plan paths
+1. MCP `workit_resolve_branch` with spec + plan paths
 2. If `needs_checkout` and `dirty` → native **AskQuestion** asks whether to stash before checkout
-3. MCP `workflow_branch_setup` with `target_branch` and `stash: yes|no`
-4. After all tasks, if manifest has `stash_ref` → AskQuestion → `workflow_branch_setup` action=`reapply_stash`
+3. MCP `workit_branch_setup` with `target_branch` and `stash: yes|no`
+4. After all tasks, if manifest has `stash_ref` → AskQuestion → `workit_branch_setup` action=`reapply_stash`
 
 ## Tools only
 

package/rules/sdd-docs-path.mdc

@@ -9,9 +9,9 @@ alwaysApply: true
 
 ## Required
 
-1. MCP `workflow_sdd_context` with `plan_path` — **always**, including fresh projects
+1. MCP `workit_sdd_context` with `plan_path` — **always**, including fresh projects
 2. Use returned `sdd_dir` (`docs/<slug>/sdd/`) for all SDD artifacts
-3. `workflow_sdd_task_brief`, `workflow_sdd_review_package`, `workflow_sdd_append_progress` — never Superpowers `sdd-workspace` script
+3. `workit_sdd_task_brief`, `workit_sdd_review_package`, `workit_sdd_append_progress` — never Superpowers `sdd-workspace` script
 
 ## Forbidden
 
@@ -19,4 +19,4 @@ alwaysApply: true
 - `cat .superpowers/sdd/progress.md` — missing file there does NOT mean "start fresh"
 - Superpowers `task-brief` / `review-package` scripts under `.agents/skills/`
 
-Fresh project with no ledger → `workflow_sdd_context` creates nothing; `progress.md` appears only on the first confirmed `workflow_sdd_append_progress`.
+Fresh project with no ledger → `workit_sdd_context` creates nothing; `progress.md` appears only on the first confirmed `workit_sdd_append_progress`.

package/skills/wk-changelog/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wk-changelog
-description: Update CHANGELOG.md via workflow_changelog_context + workflow_changelog_apply. Use for /wk-changelog or "update the changelog".
+description: Update CHANGELOG.md via workit_changelog_context + workit_changelog_apply. Use for /wk-changelog or "update the changelog".
 ---
 
 # Changelog — Keep a Changelog Update
@@ -9,14 +9,14 @@ Update `CHANGELOG.md` for the current repository.
 
 ## Step 1 — Gather facts (required)
 
-Call MCP tool `workflow_changelog_context` with arguments from the user's message (range, version, paths, etc.).
+Call MCP tool `workit_changelog_context` with arguments from the user's message (range, version, paths, etc.).
 
-**Repository calls:** For every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+**Repository calls:** For every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 
 Use the tool return value as ground truth. Do not read git, run npm, or infer repo state yourself.
 If the tool errors, report the error and stop.
 
-If `unreleased.needs_normalize` is true, call `workflow_changelog_apply` with `normalize_only: true` before merging new bullets.
+If `unreleased.needs_normalize` is true, call `workit_changelog_apply` with `normalize_only: true` before merging new bullets.
 
 ## Step 2 — Decide entries (do not edit the file yet)
 
@@ -31,7 +31,7 @@ Follow Keep a Changelog 1.1.0:
 
 ## Step 3 — Apply via tool (required)
 
-Call MCP `workflow_changelog_apply` with the new bullets. Examples:
+Call MCP `workit_changelog_apply` with the new bullets. Examples:
 
 ```json
 {

package/skills/wk-commit/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wk-commit
-description: Structured local commits via workflow_git_context. Use for /wk-commit or "use commit skill" only — not casual "ship it".
+description: Structured local commits via workit_git_context. Use for /wk-commit or "use commit skill" only — not casual "ship it".
 disable-model-invocation: true
 ---
 
@@ -8,9 +8,9 @@ disable-model-invocation: true
 
 ## Step 1 — Gather facts (required)
 
-Call MCP tool `workflow_git_context` with arguments from the user's message (paths after `/wk-commit`, etc.).
+Call MCP tool `workit_git_context` with arguments from the user's message (paths after `/wk-commit`, etc.).
 
-**Repository calls:** For every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+**Repository calls:** For every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 
 Use the tool return value as ground truth. Do not read git, run npm, or infer repo state yourself.
 If the tool errors, report the error and stop.

package/skills/wk-docs-refresh/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wk-docs-refresh
-description: Refresh stale README and docs via workflow_docs_context. Use for /wk-docs-refresh or "refresh readme/docs".
+description: Refresh stale README and docs via workit_docs_context. Use for /wk-docs-refresh or "refresh readme/docs".
 ---
 
 # Docs Refresh — Documentation Refresh
@@ -9,9 +9,9 @@ Inspect current changes and refresh stale documentation.
 
 ## Step 1 — Gather facts (required)
 
-Call MCP tool `workflow_docs_context` with arguments from the user's message (range, version, paths, etc.).
+Call MCP tool `workit_docs_context` with arguments from the user's message (range, version, paths, etc.).
 
-**Repository calls:** For every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+**Repository calls:** For every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 
 Use the tool return value as ground truth. Do not read git, run npm, or infer repo state yourself.
 If the tool errors, report the error and stop.

package/skills/wk-handoff/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wk-handoff
-description: Emit copy-paste implementation prompt for a new chat via workflow_handoff_prompt. Explicit /wk-handoff only.
+description: Emit copy-paste implementation prompt for a new chat via workit_handoff_prompt. Explicit /wk-handoff only.
 disable-model-invocation: true
 ---
 
@@ -10,20 +10,20 @@ Emit a copy-paste prompt for a **new** implementation chat.
 
 ## Step 1 — Gather facts (required)
 
-Call MCP tool `workflow_handoff_prompt` with the **full** user message as `message`.
+Call MCP tool `workit_handoff_prompt` with the **full** user message as `message`.
 
-**Repository calls:** For every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+**Repository calls:** For every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 
 **Thread context:** If this thread has a known spec/plan pair (from brainstorming, writing-plans, or open files), append both paths to `message` even when the user only typed `/wk-handoff`. Without explicit paths, the tool picks the **most recently touched** linked pair under `docs/<slug>/` (plan `**Spec:**` link + file mtimes) — not “only one file in the folder.”
 
 Use the tool return value as ground truth. Do not read git, run npm, or infer repo state yourself.
 If the tool errors, report the error and stop.
 
-The pasted prompt includes instructions to call `workflow_sdd_context`, **Cursor TodoWrite** (with returned `todos`), and `workflow_plan_tasks` in Chat B before Task 1. SDD artifacts go to `docs/<slug>/sdd/` — never `.superpowers/sdd`. TodoWrite is required for the native Cursor task list UI (remaining/completed); the SDD ledger is persistence only. The fenced `prompt` does not contain `section_text`. **Branch** is resolved automatically in the prompt (from spec/plan or derived as `feature/*` / `bugfix/*`). **No worktrees** — Chat B uses `workflow_resolve_branch` + `workflow_branch_setup` in-place. Commits use workit **/wk-commit** skill — no separate commit-policy field.
+The pasted prompt includes instructions to call `workit_sdd_context`, **Cursor TodoWrite** (with returned `todos`), and `workit_plan_tasks` in Chat B before Task 1. SDD artifacts go to `docs/<slug>/sdd/` — never `.superpowers/sdd`. TodoWrite is required for the native Cursor task list UI (remaining/completed); the SDD ledger is persistence only. The fenced `prompt` does not contain `section_text`. **Branch** is resolved automatically in the prompt (from spec/plan or derived as `feature/*` / `bugfix/*`). **No worktrees** — Chat B uses `workit_resolve_branch` + `workit_branch_setup` in-place. Commits use workit **/wk-commit** skill — no separate commit-policy field.
 
-`workflow_handoff_prompt` also returns `tasks[]`, `branch`, `sdd_dir`, `completed_task_ids`, and `todos` for same-session MCP use — not copy-paste transport.
+`workit_handoff_prompt` also returns `tasks[]`, `branch`, `sdd_dir`, `completed_task_ids`, and `todos` for same-session MCP use — not copy-paste transport.
 
-A destination run that executes the plan must still end with `workflow_plan_complete` once the SDD ledger is complete and repository verification passes, and never finish the run while the plan is still `active`.
+A destination run that executes the plan must still end with `workit_plan_complete` once the SDD ledger is complete and repository verification passes, and never finish the run while the plan is still `active`.
 
 ## Output (success)
 

package/skills/wk-implement/SKILL.md

@@ -10,9 +10,9 @@ Execute the plan **inline in this coordinator session**. subagent-driven executi
 
 ## Step 1 — Gather facts (required)
 
-Call MCP tool `workflow_plan_tasks` with `plan_path` from the user's message and `spec_path` when known.
+Call MCP tool `workit_plan_tasks` with `plan_path` from the user's message and `spec_path` when known.
 
-**Repository calls:** For every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+**Repository calls:** For every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 
 Use the returned `tasks[]` as ground truth. Cache each `section_text` for subagent prompts. Do not read the plan file for task text.
 
@@ -20,7 +20,7 @@ Use the returned `tasks[]` as ground truth. Cache each `section_text` for subage
 
 Resolve plugin root: `WORKFLOW_TOOLKIT_ROOT` env or `~/.cursor/plugins/local/workit/`.
 
-Load `templates/execution-contract.md`. Substitute `<SPEC_PATH>`, `<PLAN_PATH>`, `<BRANCH>`, `<SDD_DIR>`, `<TASK_LIST>` from MCP. OMIT the `## Handoff destination` section and its `<workflow-handoff-destination>` marker line — that section is only for sessions started from a `workflow_handoff_prompt` destination prompt. This inline executor is NOT a destination and must never present itself as one (five-choice source menu, Handoff still available). If template missing, stop with error.
+Load `templates/execution-contract.md`. Substitute `<SPEC_PATH>`, `<PLAN_PATH>`, `<BRANCH>`, `<SDD_DIR>`, `<TASK_LIST>` from MCP. OMIT the `## Handoff destination` section and its `<workflow-handoff-destination>` marker line — that section is only for sessions started from a `workit_handoff_prompt` destination prompt. This inline executor is NOT a destination and must never present itself as one (five-choice source menu, Handoff still available). If template missing, stop with error.
 
 ## Step 3 — Follow contract
 
@@ -28,17 +28,17 @@ Announce: "Using implement + inline."
 
 **Before Task 1 — validate + SDD + TodoWrite UI + branch (no worktrees):**
 
-0. `workflow_docs_validate` with spec + plan paths — hard-fail before any SDD mutation
-1. `workflow_sdd_context` with `plan_path` — cache `sdd_dir`, `completed_task_ids`, **`todos`**
+0. `workit_docs_validate` with spec + plan paths — hard-fail before any SDD mutation
+1. `workit_sdd_context` with `plan_path` — cache `sdd_dir`, `completed_task_ids`, **`todos`**
 2. **TodoWrite** with `todos` from step 1 (`merge: false`) — required for Cursor native task list UI (SDD is not a UI substitute)
-3. `workflow_resolve_branch` with spec + plan paths
+3. `workit_resolve_branch` with spec + plan paths
 4. If `needs_checkout` and `dirty` → native **AskQuestion** asks whether to stash before checkout
-5. `workflow_branch_setup` with `target_branch`, `stash`, `sdd_dir` from step 1
+5. `workit_branch_setup` with `target_branch`, `stash`, `sdd_dir` from step 1
 
-Follow the contract verbatim. Keep TodoWrite `in_progress`/`completed` in sync each task. At verify/commit phase use `workflow_verify` and `workflow_git_context` MCP tools.
+Follow the contract verbatim. Keep TodoWrite `in_progress`/`completed` in sync each task. At verify/commit phase use `workit_verify` and `workit_git_context` MCP tools.
 
 Each task lands exactly one contiguous non-empty commit range (`base..head`): fix rounds append commits to that range and never rewrite/amend an active review range; each progress line records the task's real base..head shas.
 
 Do not emit a handoff fence — this is in-session execution.
 
-**Mandatory:** end the run by calling MCP `workflow_plan_complete` after the final task once the SDD ledger is complete (all task IDs appended) and `workflow_verify` passes — a complete ledger and green verification are the tool's gates. Never finish the run while the plan is still `active`.
+**Mandatory:** end the run by calling MCP `workit_plan_complete` after the final task once the SDD ledger is complete (all task IDs appended) and `workit_verify` passes — a complete ledger and green verification are the tool's gates. Never finish the run while the plan is still `active`.

package/skills/wk-issue-update/SKILL.md

@@ -14,7 +14,7 @@ Post a Spanish comment and log time on a **task** issue (not the meeting issue).
 
 **Audience:** @Alejandra.Flores — not a developer. Clarify technical terms in plain language when they appear.
 
-**Repository calls:** For every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+**Repository calls:** For every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 
 ## Step 0 — Toolkit ready
 
@@ -27,12 +27,12 @@ If unsure, call `workit_status`. Stop if `ready: false`.
 1. If the user did **not** already paste a YouTrack URL or issue id (`NSR-40`) in the message that started this flow, ask:
    > Paste the YouTrack issue URL or id for this update (e.g. `https://…/issue/NSR-40` or `NSR-40`).
 2. Wait for their reply. Do **not** guess from spec/plan unless they explicitly say to use the plan's issue.
-3. Call `workflow_youtrack_parse_issue` with `issue_ref` = what they pasted.
+3. Call `workit_youtrack_parse_issue` with `issue_ref` = what they pasted.
 4. On error, ask again with the parse error. On success, note `issueId`.
 
 ## Step 2 — Context (required)
 
-Call `workflow_youtrack_context` with `issue_id` from Step 1 (or `issue_url` / `issue_ref` directly). Stop on error.
+Call `workit_youtrack_context` with `issue_id` from Step 1 (or `issue_url` / `issue_ref` directly). Stop on error.
 
 Show the resolved issue once in chat: `Updating **{issueId}**` (+ `issueUrl` if returned).
 
@@ -46,7 +46,7 @@ Ask user to paste rough notes, half-written update, or bullets. Skip to Step 5.
 
 ### Mode `remind` — Help me remember
 
-1. Optionally call `workflow_git_context` (and read spec/plan title) **only to remind the user in English chat** — short prose: what repo, branch, themes of commits, not a pasteable comment.
+1. Optionally call `workit_git_context` (and read spec/plan title) **only to remind the user in English chat** — short prose: what repo, branch, themes of commits, not a pasteable comment.
 2. Ask conversational follow-ups: *¿Qué te costó más? ¿Qué queda para mañana? ¿Algo bloqueado?*
 3. User replies in their words (Spanish messy notes OK).
 4. Treat their reply as the draft → Step 5.
@@ -55,14 +55,14 @@ Ask user to paste rough notes, half-written update, or bullets. Skip to Step 5.
 
 ### Mode `auto` — Draft for me to edit
 
-1. Use `workflow_git_context` + conversation context to infer what they likely worked on.
+1. Use `workit_git_context` + conversation context to infer what they likely worked on.
 2. Write a **first draft in Spanish** per **youtrack-update-style.md** (paragraphs, manager-friendly, no file paths).
 3. Show draft in a fenced block. Ask user to correct, add, or replace — user may reply with a full rewrite.
 4. Use their corrected version as input → Step 5.
 
 ## Step 4 — Duration
 
-Ask time spent on this task issue. User text → `workflow_youtrack_parse_duration`. **Do not compute minutes yourself.**
+Ask time spent on this task issue. User text → `workit_youtrack_parse_duration`. **Do not compute minutes yourself.**
 
 ## Step 5 — Polish (ChatGPT pass)
 
@@ -73,7 +73,7 @@ Polish the approved draft per **youtrack-update-style.md**:
 - Keep `# Actualización` + greeting — if user already included them, do not duplicate `@Alejandra.Flores`
 - `## Off-topic` only if user's material has a clear tangent section
 
-Call `workflow_youtrack_draft` with:
+Call `workit_youtrack_draft` with:
 
 - `issueId` from Step 1
 - `userNotes` = polished **body only** (no `# Actualización`, no greeting line)
@@ -88,9 +88,9 @@ Show returned `markdown` in a fenced block. User may edit in chat (apply edits a
 
 Use native `AskQuestion`: title `Post to YouTrack`; prompt `Post this reviewed update to YouTrack and log the approved time?`; options `Post and log time` and `Cancel`. On confirm:
 
-`workflow_youtrack_post` with `confirmed: true`, `issueId`, `markdown`, `minutes`. **Do not pass `date`.**
+`workit_youtrack_post` with `confirmed: true`, `issueId`, `markdown`, `minutes`. **Do not pass `date`.**
 
-If the result has `partial: true`, the comment already posted. Report the time-log failure and retry only with `workflow_youtrack_log_time` using the same `issueId` and `minutes`; never call `workflow_youtrack_post` again.
+If the result has `partial: true`, the comment already posted. Report the time-log failure and retry only with `workit_youtrack_log_time` using the same `issueId` and `minutes`; never call `workit_youtrack_post` again.
 
 ## Rules
 

package/skills/wk-issue-update/references/youtrack-update-style.md

@@ -1,6 +1,6 @@
 # YouTrack update style (Cristhofer / es-CL)
 
-Use when writing or polishing the comment body before `workflow_youtrack_draft`. **Preserve the author's voice** — like the ChatGPT revision thread: grammar, flow, and light structure, not a changelog.
+Use when writing or polishing the comment body before `workit_youtrack_draft`. **Preserve the author's voice** — like the ChatGPT revision thread: grammar, flow, and light structure, not a changelog.
 
 ## Audience
 

package/skills/wk-meetings/SKILL.md

@@ -16,7 +16,7 @@ If unsure, call `workit_status`. Stop if `ready: false`.
 
 ## Step 1 — Context (required)
 
-Call MCP `workflow_youtrack_context` with `mode: "meetings"` (no `issue_id` yet). Stop on error.
+Call MCP `workit_youtrack_context` with `mode: "meetings"` (no `issue_id` yet). Stop on error.
 
 ## Step 2 — Pick meeting type (required)
 
@@ -30,7 +30,7 @@ Use native **AskQuestion** with `meetingOptions` from context:
 
 ## Step 3 — Duration
 
-Ask how much meeting time today (English UI). User text → `workflow_youtrack_parse_duration`. **Do not compute minutes yourself.**
+Ask how much meeting time today (English UI). User text → `workit_youtrack_parse_duration`. **Do not compute minutes yourself.**
 
 ## Step 4 — Preview + confirm
 
@@ -40,9 +40,9 @@ Use native **AskQuestion** to confirm logging the shown meeting time; on yes:
 
 ## Step 5 — Log time only
 
-Call `workflow_youtrack_log_time` with `issueId`, `minutes`, `text` (from `workItemText`). **Do not pass `date`** — tool uses epoch ms automatically.
+Call `workit_youtrack_log_time` with `issueId`, `minutes`, `text` (from `workItemText`). **Do not pass `date`** — tool uses epoch ms automatically.
 
-**Never** call `workflow_youtrack_post` from this skill.
+**Never** call `workit_youtrack_post` from this skill.
 
 ## Rules
 

package/skills/wk-pr/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wk-pr
-description: Draft or create PR/MR via workflow_pr_context + glab/gh. Squash on merge + delete source branch. Use /wk-pr.
+description: Draft or create PR/MR via workit_pr_context + glab/gh. Squash on merge + delete source branch. Use /wk-pr.
 ---
 
 # PR — Draft or Create
@@ -9,13 +9,13 @@ Draft a merge request / pull request body, or create it on GitLab (`glab`) / Git
 
 **Setup:** `/wk-init` → pick provider → VCS scaffold → edit active token file.
 
-**Active provider:** read `vcs_config.provider` from `workflow_pr_context` (or `provider` in `~/.config/workit/vcs.json`). That decides `glab` vs `gh`.
+**Active provider:** read `vcs_config.provider` from `workit_pr_context` (or `provider` in `~/.config/workit/vcs.json`). That decides `glab` vs `gh`.
 
 ## Step 1 — Gather facts (required)
 
-Call MCP `workflow_pr_context` with **no `range` argument** unless the user supplied an explicit git range string.
+Call MCP `workit_pr_context` with **no `range` argument** unless the user supplied an explicit git range string.
 
-**Repository calls:** For every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+**Repository calls:** For every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 
 On `feature/*` or `bugfix/*`, the tool compares **only against `develop`** (never `main`).
 
@@ -62,9 +62,9 @@ Body:
 
 Use native `AskQuestion`: title `Create MR/PR`; prompt `Create the reviewed MR/PR now?`; options `Create` and `Cancel`. On `Create`:
 
-`workflow_pr_create` with `confirmed: true`, `title`, `body`, optional `target_branch` (defaults from vcs.json).
+`workit_pr_create` with `confirmed: true`, `title`, `body`, optional `target_branch` (defaults from vcs.json).
 
-**On failure:** show the tool `error` / `stderr` / `hint` and stop. **Never** fall back to running `glab` or `gh` in the shell — creation must go through `workflow_pr_create` only.
+**On failure:** show the tool `error` / `stderr` / `hint` and stop. **Never** fall back to running `glab` or `gh` in the shell — creation must go through `workit_pr_create` only.
 
 Creation uses vcs.json flags (both default `true`):
 
@@ -86,5 +86,5 @@ GitHub: use **Squash and merge** + **Delete branch** in the UI (or `gh pr merge
 
 - Do not edit product files in this skill (except user asks to fix PR template).
 - Never paste VCS tokens in chat.
-- **Never run `glab` or `gh` directly** — only `workflow_pr_create`.
+- **Never run `glab` or `gh` directly** — only `workit_pr_create`.
 - Do not claim validation passed unless evidence exists.

package/skills/wk-release-notes/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wk-release-notes
-description: Draft release notes via workflow_release_notes_context. Use for /wk-release-notes or "draft release notes".
+description: Draft release notes via workit_release_notes_context. Use for /wk-release-notes or "draft release notes".
 ---
 
 # Release Notes — User-Facing Release Notes
@@ -11,9 +11,9 @@ Draft release notes for a given release, version, tag, or commit range.
 
 If the user did not provide an exact tag, version, or commit range, ask for it before calling the tool.
 
-Call MCP tool `workflow_release_notes_context` with arguments from the user's message (range, version, paths, etc.).
+Call MCP tool `workit_release_notes_context` with arguments from the user's message (range, version, paths, etc.).
 
-**Repository calls:** For every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+**Repository calls:** For every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 
 Use the tool return value as ground truth. Do not read git, run npm, or infer repo state yourself.
 If the tool errors, report the error and stop.

package/skills/wk-status/SKILL.md

@@ -82,4 +82,4 @@ Use `items[youtrack_token].token_create_url` / `token_edit_path`, or top-level `
 
 - Do not call YouTrack HTTP directly — `workit_status` includes verify.
 - Do not ask user to paste token — point them to edit the token file if `placeholder: true`.
-- Optional: `workflow_youtrack_verify_token` only if user asks to re-test API alone.
+- Optional: `workit_youtrack_verify_token` only if user asks to re-test API alone.

package/skills/wk-verify/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: wk-verify
-description: Run project validation via workflow_verify MCP tool. Use for /wk-verify or when user says "use verify skill".
+description: Run project validation via workit_verify MCP tool. Use for /wk-verify or when user says "use verify skill".
 disable-model-invocation: true
 ---
 
@@ -10,9 +10,9 @@ Run the repository's validation checks and report exact results.
 
 ## Step 1 — Gather facts (required)
 
-Call MCP tool `workflow_verify` with arguments from the user's message (range, version, paths, etc.).
+Call MCP tool `workit_verify` with arguments from the user's message (range, version, paths, etc.).
 
-**Repository calls:** For every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+**Repository calls:** For every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 
 Use the tool return value as ground truth. Do not read git, run npm, or infer repo state yourself.
 If the tool errors, report the error and stop.

package/vendor/superpowers/skills/subagent-driven-development/SKILL.md

@@ -63,7 +63,7 @@ digraph process {
     "Read plan, note context and global constraints, create todos" [shape=box];
     "More tasks remain?" [shape=diamond];
     "Dispatch final code reviewer subagent (../requesting-code-review/code-reviewer.md)" [shape=box];
-    "Run verification, then workflow_plan_complete once the ledger is complete and verification passes" [shape=box];
+    "Run verification, then workit_plan_complete once the ledger is complete and verification passes" [shape=box];
     "Use superpowers:finishing-a-development-branch" [shape=box style=filled fillcolor=lightgreen];
 
     "Read plan, note context and global constraints, create todos" -> "Dispatch implementer subagent (./implementer-prompt.md)";
@@ -79,12 +79,12 @@ digraph process {
     "Mark task complete in todo list and progress ledger" -> "More tasks remain?";
     "More tasks remain?" -> "Dispatch implementer subagent (./implementer-prompt.md)" [label="yes"];
     "More tasks remain?" -> "Dispatch final code reviewer subagent (../requesting-code-review/code-reviewer.md)" [label="no"];
-    "Dispatch final code reviewer subagent (../requesting-code-review/code-reviewer.md)" -> "Run verification, then workflow_plan_complete once the ledger is complete and verification passes";
-    "Run verification, then workflow_plan_complete once the ledger is complete and verification passes" -> "Use superpowers:finishing-a-development-branch";
+    "Dispatch final code reviewer subagent (../requesting-code-review/code-reviewer.md)" -> "Run verification, then workit_plan_complete once the ledger is complete and verification passes";
+    "Run verification, then workit_plan_complete once the ledger is complete and verification passes" -> "Use superpowers:finishing-a-development-branch";
 }
 ```
 
-**Mandatory completion:** after the final whole-branch review, run repository verification. Once the SDD ledger is complete and verification passes, end the run by calling `workflow_plan_complete` (or the CLI `workit flow complete`) — a complete ledger and green verification are the tool's gates. Never finish while the plan is still `active`.
+**Mandatory completion:** after the final whole-branch review, run repository verification. Once the SDD ledger is complete and verification passes, end the run by calling `workit_plan_complete` (or the CLI `workit flow complete`) — a complete ledger and green verification are the tool's gates. Never finish while the plan is still `active`.
 
 ## Pre-Flight Plan Review