@brainervirus/workit-cursor 0.8.9 → 0.8.10

package/.cursor-plugin/plugin.json

@@ -2,7 +2,7 @@
   "name": "workit",
   "displayName": "Workit",
   "description": "OpenCode-style verify, PR, changelog, commit, and session handoff for Cursor",
-  "version": "0.8.9",
+  "version": "0.8.10",
   "author": {
     "name": "Cristhofer Pincetti"
   },

package/README.md

@@ -40,7 +40,7 @@ npx @brainervirus/workit-cli init
 
 ## What it provides
 
-- MCP server exposing the `workflow_*` tools (branch setup, PR create/context, docs validate/promote, YouTrack post/log/time, templates, rules, presentation, doctor, handoff, and plan lifecycle `workflow_plan_pause`/`resume`/`complete`).
+- MCP server exposing the `workit_*` tools (branch setup, PR create/context, docs validate/promote, YouTrack post/log/time, templates, rules, presentation, doctor, handoff, and plan lifecycle `workit_plan_pause`/`resume`/`complete`).
 - Session-start contract hook.
 - 4 rules and 12 `wk-*` skills (plus 14 sanitized Superpowers skills).
 
@@ -98,7 +98,7 @@ The repository root carries `.cursor-plugin/marketplace.json`, indexing `package
 - **Installing from Marketplace** — a Marketplace admin adds the repository URL through Cursor's authenticated publisher flow; end users then install the plugin from the Cursor Marketplace UI, which reads `.cursor-plugin/plugin.json` and the tracked components directly from Git.
 - **Submission** — Marketplace submission is a separate, later authenticated action at `https://cursor.com/marketplace/publish`. It is **not** performed here and no publication or acceptance is claimed; the repository is kept validated and submission-ready.
 - **Update review** — Git plugin metadata (manifest, rules, skills, assets) is reviewed by Cursor on Marketplace updates, while the npm runtime runs from `@latest` with `--prefer-online`. The selector is shared across `mcp.json`, `hooks-cursor.json`, and `run-cursor-mcp.sh`, and a stale `latest` resolution is prevented by the mandatory `--prefer-online` flag.
-- **Troubleshooting** — `workit doctor` (or the `workflow_doctor` tool) reports installation health including runtime, token, VCS/YouTrack, and log-writability checks; it exits nonzero on failure. An MCP/hook startup failure with no network is an `npx`/registry reachability issue, not a Workit defect.
+- **Troubleshooting** — `workit doctor` (or the `workit_doctor` tool) reports installation health including runtime, token, VCS/YouTrack, and log-writability checks; it exits nonzero on failure. An MCP/hook startup failure with no network is an `npx`/registry reachability issue, not a Workit defect.
 
 ## Auto-load repair
 

package/assets/templates/execution-contract.md

@@ -20,48 +20,48 @@ This session is a handoff destination for a continued plan. The originating sess
 ## Hard gates
 
 - The parent is coordinator-only: it does not edit product code or perform delegated exploration.
-- Never use a worktree. Branch changes are in-place through `workflow_branch_setup` on `feature/*` or `bugfix/*`; never commit on protected branches.
-- Working state, briefs, ledgers, and review diffs live only under gitignored `<SDD_DIR>` in `docs/<slug>/sdd/` and use `workflow_sdd_*` tools.
+- Never use a worktree. Branch changes are in-place through `workit_branch_setup` on `feature/*` or `bugfix/*`; never commit on protected branches.
+- Working state, briefs, ledgers, and review diffs live only under gitignored `<SDD_DIR>` in `docs/<slug>/sdd/` and use `workit_sdd_*` tools.
 - Use native `todowrite` for visible task state as well as the gitignored ledger.
 - Use native `question` for branch/stash choices and guarded external mutations; call mutation tools only after approval with `confirmed: true` (grounded in the recorded NativeChoiceEvidence).
-- Flow-tool confirmations are never agent-typed booleans and never caller-supplied evidence objects: on OpenCode the plugin records the user's native-`question` answer as a host-observed one-use receipt (`attested: true`, `callID`, `selectedLabel`, `recordedAt`) consumed by `workflow_spec_approve` / `workflow_plan_approve` / `workflow_plan_menu` — no evidence argument exists, and delegated worker status comes from host session parentage (`parentID`), never a caller `role` field. On Cursor, confirmations are policy-only (`attested: false`) and subagent-driven execution is rejected as unsupported.
-- Delegated authority is direct-child-only: a worker is the session whose host `parentID` exactly equals the activating coordinator's recorded `coordinator_session_id`; missing, mismatched, or multi-owner lineage fails closed with `delegation_lineage_denied`, and nested `opencode` launches are denied during active delegated work. An authorized child receives only the compact worker contract (execute the supplied brief, follow TDD, land one contiguous non-empty commit range, report results) — never coordinator guidance, `wk-implement`, or ledger management; coordinator bookkeeping via `workflow_sdd_*` stays with the coordinator session.
-- On Cursor, for every repository-scoped `workflow_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
+- Flow-tool confirmations are never agent-typed booleans and never caller-supplied evidence objects: on OpenCode the plugin records the user's native-`question` answer as a host-observed one-use receipt (`attested: true`, `callID`, `selectedLabel`, `recordedAt`) consumed by `workit_spec_approve` / `workit_plan_approve` / `workit_plan_menu` — no evidence argument exists, and delegated worker status comes from host session parentage (`parentID`), never a caller `role` field. On Cursor, confirmations are policy-only (`attested: false`) and subagent-driven execution is rejected as unsupported.
+- Delegated authority is direct-child-only: a worker is the session whose host `parentID` exactly equals the activating coordinator's recorded `coordinator_session_id`; missing, mismatched, or multi-owner lineage fails closed with `delegation_lineage_denied`, and nested `opencode` launches are denied during active delegated work. An authorized child receives only the compact worker contract (execute the supplied brief, follow TDD, land one contiguous non-empty commit range, report results) — never coordinator guidance, `wk-implement`, or ledger management; coordinator bookkeeping via `workit_sdd_*` stays with the coordinator session.
+- On Cursor, for every repository-scoped `workit_*` call, pass the active Cursor workspace as `workspace_root`; never rely on the MCP process default.
 - Use native `task` with only the built-in `explore` and `general` agents.
 
 ## Flow gates (HARD)
 
 - `wk-implement` refuses to run unless the plan is `approved` (flow.json) and the post-plan menu was presented.
 - `wk-handoff` refuses to run unless both spec and plan are `approved`.
-- Sequence is enforced by tools: `workflow_spec_approve`, `workflow_plan_approve`, `workflow_plan_menu` — never skip a step (the spec/plan self-review runs automatically inside the transition; only the final approval asks for your confirmation).
+- Sequence is enforced by tools: `workit_spec_approve`, `workit_plan_approve`, `workit_plan_menu` — never skip a step (the spec/plan self-review runs automatically inside the transition; only the final approval asks for your confirmation).
 
 ## Setup
 
-0. Call `workflow_docs_validate` with the linked spec/plan paths. Hard-fail on any error before todos or branch setup.
-1. Call `workflow_sdd_context` with `<PLAN_PATH>` and initialize `todowrite` from returned tasks.
-2. Call `workflow_plan_tasks`; cache each top-level task's `section_text`.
+0. Call `workit_docs_validate` with the linked spec/plan paths. Hard-fail on any error before todos or branch setup.
+1. Call `workit_sdd_context` with `<PLAN_PATH>` and initialize `todowrite` from returned tasks.
+2. Call `workit_plan_tasks`; cache each top-level task's `section_text`.
 3. Mark IDs in `completed_task_ids` completed and never redispatch them.
-4. Call `workflow_resolve_branch`, then show the current branch, target branch, and stash behavior before any in-place checkout/setup mutation.
+4. Call `workit_resolve_branch`, then show the current branch, target branch, and stash behavior before any in-place checkout/setup mutation.
 5. Always use `question`: for a clean tree ask whether to proceed or cancel; for a dirty tree add the stash choice and describe what will be stashed.
-6. Call `workflow_branch_setup` with `confirmed: true` only after approval.
+6. Call `workit_branch_setup` with `confirmed: true` only after approval.
 
 ## Remaining-task loop
 
 For each top-level task absent from `completed_task_ids`:
 
 1. Mark it `in_progress` with `todowrite`.
-2. Create a working-state brief with `workflow_sdd_task_brief` and `confirmed: true`.
+2. Create a working-state brief with `workit_sdd_task_brief` and `confirmed: true`.
 3. Delegate read-only discovery, when needed, to an `explore` agent. Delegate implementation to a fresh `general` agent. Product changes follow TDD.
-4. Create a working-state diff with `workflow_sdd_review_package` and `confirmed: true`.
+4. Create a working-state diff with `workit_sdd_review_package` and `confirmed: true`.
 5. Delegate spec-compliance review and code-quality review to separate `general` agents.
-6. **Blocking** findings (Critical, Important, or spec-compliance) may trigger at most **two** fix+re-review rounds per task. **Advisory** findings (Minor, style, YAGNI, taste) never pause the loop — append them with `workflow_sdd_append_advisory` (`--task <id> --text <text>`, `confirmed: true`) instead of an unrestricted file edit.
-7. Append the validated ledger entry with `workflow_sdd_append_progress` and `confirmed: true`; mark the todo completed.
+6. **Blocking** findings (Critical, Important, or spec-compliance) may trigger at most **two** fix+re-review rounds per task. **Advisory** findings (Minor, style, YAGNI, taste) never pause the loop — append them with `workit_sdd_append_advisory` (`--task <id> --text <text>`, `confirmed: true`) instead of an unrestricted file edit.
+7. Append the validated ledger entry with `workit_sdd_append_progress` and `confirmed: true`; mark the todo completed.
 
 ## Final gate
 
-Run a separate full-branch code review, then `workflow_verify`. Present the full `<SDD_DIR>/advisories.md` roll-up once, then use native `question` so the user can choose which advisory items to fix, discuss, or discard. Report exact check results and never infer success. Use `workflow_git_context` for a commit preview and load `wk-commit` through `skill` for an approved commit. If working state contains a stash reference, preview reapplication through `question`, then call `workflow_branch_setup` with `confirmed: true` after approval.
+Run a separate full-branch code review, then `workit_verify`. Present the full `<SDD_DIR>/advisories.md` roll-up once, then use native `question` so the user can choose which advisory items to fix, discuss, or discard. Report exact check results and never infer success. Use `workit_git_context` for a commit preview and load `wk-commit` through `skill` for an approved commit. If working state contains a stash reference, preview reapplication through `question`, then call `workit_branch_setup` with `confirmed: true` after approval.
 
-**Mandatory:** end the run by calling `workflow_plan_complete` (OpenCode/Cursor) or the CLI `workit flow complete` (CLI host) 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 `workit_plan_complete` (OpenCode/Cursor) or the CLI `workit flow complete` (CLI host) 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`.
 
 ## Task order
 
@@ -70,4 +70,4 @@ Run a separate full-branch code review, then `workflow_verify`. Present the full
 ## Quality gate (HARD)
 
 - Specs/plans are written from `templates/spec-template.md` / `templates/plan-template.md`.
-- After `workflow_docs_validate`, surface `quality` findings (spec scan). Hard findings (missing required section, missing CA-XX) block task start unless the user explicitly waives them. Warnings are advisory.
+- After `workit_docs_validate`, surface `quality` findings (spec scan). Hard findings (missing required section, missing CA-XX) block task start unless the user explicitly waives them. Warnings are advisory.

package/assets/templates/plan-template.md

@@ -10,7 +10,7 @@
 ## Global Constraints
 
 - 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.
-- The final task ends execution with `workflow_plan_complete` (or the CLI `workit flow complete`) once the SDD ledger is complete and repository verification passes — a run never finishes while the plan is still `active`.
+- The final task ends execution with `workit_plan_complete` (or the CLI `workit flow complete`) once the SDD ledger is complete and repository verification passes — a run never finishes while the plan is still `active`.
 - <project-wide requirements, one line each>
 
 ---

package/assets/templates/spec-template.md

@@ -16,13 +16,13 @@
 
 ## Architecture
 
-<!-- REQUIRED if this spec has flows or architecture: render a mermaid diagram (workflow_present_flow). -->
+<!-- REQUIRED if this spec has flows or architecture: render a mermaid diagram (workit_present_flow). -->
 ```mermaid
 flowchart TD
   A[Start] --> B[Step]
 ```
 
-<!-- REQUIRED if this spec touches UI: render an ASCII wireframe (workflow_present_ascii). -->
+<!-- REQUIRED if this spec touches UI: render an ASCII wireframe (workit_present_ascii). -->
 ```text
 ┌──────────────┐
 │ Header       │

package/assets/templates/superpowers-doc-contract.md

@@ -27,31 +27,31 @@ Plans require:
 
 `bugfix/<slug>` is also valid. Never use `main`, `develop`, `master`, or `prod`. Use plain backtick paths. Top-level headings are exactly `### Task N: Title`; steps use `- [ ] **Step N:** ...`; task headings never appear inside fences.
 
-Before writing **Branch:** into a new spec or plan, call `workflow_docs_branch` and write the returned `branch` verbatim. When `action` is `keep`, use the current feature/bugfix branch. When `action` is `create_from_develop` or `create_from_base`, create the branch only through `workflow_branch_setup`; it uses the configured workspace/global target branch.
+Before writing **Branch:** into a new spec or plan, call `workit_docs_branch` and write the returned `branch` verbatim. When `action` is `keep`, use the current feature/bugfix branch. When `action` is `create_from_develop` or `create_from_base`, create the branch only through `workit_branch_setup`; it uses the configured workspace/global target branch.
 
 ## Execution and handoff
 
 - Implementation uses `wk-implement` and subagent-driven development, with native `todowrite` and `task`.
 - Commits use `wk-commit` after its native `question` confirmation.
-- Continuation uses `wk-handoff`, whose `workflow_handoff_session` creates and seeds the OpenCode session automatically.
-- Never use worktrees. Resolve the declared branch with `workflow_resolve_branch`, preview dirty-tree stash choices with `question`, and apply an approved in-place checkout through `workflow_branch_setup` with `confirmed: true` (grounded in the recorded NativeChoiceEvidence).
-- Flow-tool confirmations are never agent-typed booleans and never caller-supplied evidence objects: on OpenCode the plugin records the user's native-`question` answer as a host-observed one-use receipt (`attested: true`, `callID`, `selectedLabel`, `recordedAt`) consumed by `workflow_spec_approve` / `workflow_plan_approve` / `workflow_plan_menu` — no evidence argument exists, and delegated worker status comes from host session parentage (`parentID`), never a caller `role` field. On Cursor, confirmations are policy-only (`attested: false`) and subagent-driven execution is rejected as unsupported.
-- Keep all SDD state under the gitignored `docs/<slug>/sdd/`; use `workflow_sdd_context` and the registered `workflow_sdd_*` tools.
-- After implementation, use `question` before an approved stash reapply through `workflow_branch_setup` with `confirmed: true`.
+- Continuation uses `wk-handoff`, whose `workit_handoff_session` creates and seeds the OpenCode session automatically.
+- Never use worktrees. Resolve the declared branch with `workit_resolve_branch`, preview dirty-tree stash choices with `question`, and apply an approved in-place checkout through `workit_branch_setup` with `confirmed: true` (grounded in the recorded NativeChoiceEvidence).
+- Flow-tool confirmations are never agent-typed booleans and never caller-supplied evidence objects: on OpenCode the plugin records the user's native-`question` answer as a host-observed one-use receipt (`attested: true`, `callID`, `selectedLabel`, `recordedAt`) consumed by `workit_spec_approve` / `workit_plan_approve` / `workit_plan_menu` — no evidence argument exists, and delegated worker status comes from host session parentage (`parentID`), never a caller `role` field. On Cursor, confirmations are policy-only (`attested: false`) and subagent-driven execution is rejected as unsupported.
+- Keep all SDD state under the gitignored `docs/<slug>/sdd/`; use `workit_sdd_context` and the registered `workit_sdd_*` tools.
+- After implementation, use `question` before an approved stash reapply through `workit_branch_setup` with `confirmed: true`.
 
 ## YouTrack content
 
-Chat follows the user's language. YouTrack task comments are Spanish (`es-CL`) and use `workflow_youtrack_draft` followed by reviewed `workflow_youtrack_post` with `confirmed: true`. Preserve the user's paragraph voice; do not inject commits, file paths, or robotic bullet reports.
+Chat follows the user's language. YouTrack task comments are Spanish (`es-CL`) and use `workit_youtrack_draft` followed by reviewed `workit_youtrack_post` with `confirmed: true`. Preserve the user's paragraph voice; do not inject commits, file paths, or robotic bullet reports.
 
 ## Final self-check
 
-Before handoff, call `workflow_docs_validate` on the linked spec/plan pair. Hard-fail on any error; never offer execution when validation fails.
+Before handoff, call `workit_docs_validate` on the linked spec/plan pair. Hard-fail on any error; never offer execution when validation fails.
 
 Before handoff, verify the saved spec path, plan path, declared branch, top-level task numbering, and workflow-managed SDD directory through the registered read-only workflow tools. Report structured failures; never infer success.
 
 ## Post-plan execution choice
 
-After saving a plan, call `workflow_docs_validate` on the spec/plan pair. On failure, stop and fix docs — do not offer execution.
+After saving a plan, call `workit_docs_validate` on the spec/plan pair. On failure, stop and fix docs — do not offer execution.
 
 On success, use native `question` / Cursor `AskQuestion` with exactly these options (no stay, no A/B/C prose duplicate):
 
@@ -62,7 +62,7 @@ On success, use native `question` / Cursor `AskQuestion` with exactly these opti
 5. Review plan first
 6. Change model first
 
-`Change model first` is display-only deferral: it ends the turn without calling `workflow_plan_menu` and re-presents the menu on the next turn. Every other choice must call `workflow_plan_menu` immediately after the answer and before any skill, branch question, mutation, or handoff.
+`Change model first` is display-only deferral: it ends the turn without calling `workit_plan_menu` and re-presents the menu on the next turn. Every other choice must call `workit_plan_menu` immediately after the answer and before any skill, branch question, mutation, or handoff.
 
 Never emit Superpowers text beginning “Two execution options”.
 

package/dist/cursor-session-start.js

@@ -322,14 +322,14 @@ var REMINDER_TEXT = `<workflow-contract-reminder>
 - Bounded user choices → call the native \`question\` tool (never A/B/C or 1/2/3 lists in prose).
 - After a plan is approved → native \`question\` menu with exactly: ${SOURCE_MENU_LABELS_DISPLAY.join(", ")}.
 - Tools with \`confirmed\` → call them; never fabricate their result.
-- Before the first \`workflow_spec_approve\`/\`workflow_plan_approve\` (self-review) run the superpowers writing-plans Self-Review checklist: spec coverage (every spec requirement maps to a task), placeholder scan, type consistency; fix findings inline.
+- Before the first \`workit_spec_approve\`/\`workit_plan_approve\` (self-review) run the superpowers writing-plans Self-Review checklist: spec coverage (every spec requirement maps to a task), placeholder scan, type consistency; fix findings inline.
 - Delivering docs → clickable markdown link \`[spec.md](docs/<slug>/spec.md)\` + 3-5 bullet summary.
 </workflow-contract-reminder>`;
 var DESTINATION_REMINDER_TEXT = `<workflow-contract-reminder>
 - Bounded user choices → call the native \`question\` tool (never A/B/C or 1/2/3 lists in prose).
 - This session is a handoff destination: present the post-plan menu with exactly: ${DESTINATION_MENU_LABELS.join(", ")}.
 - Tools with \`confirmed\` → call them; never fabricate their result.
-- Before the first \`workflow_spec_approve\`/\`workflow_plan_approve\` (self-review) run the superpowers writing-plans Self-Review checklist: spec coverage (every spec requirement maps to a task), placeholder scan, type consistency; fix findings inline.
+- Before the first \`workit_spec_approve\`/\`workit_plan_approve\` (self-review) run the superpowers writing-plans Self-Review checklist: spec coverage (every spec requirement maps to a task), placeholder scan, type consistency; fix findings inline.
 - Delivering docs → clickable markdown link \`[spec.md](docs/<slug>/spec.md)\` + 3-5 bullet summary.
 ${HANDOFF_DESTINATION_MARKER}
 </workflow-contract-reminder>`;
@@ -416,19 +416,19 @@ HARD-GATE: Any user choice with options → call Cursor AskQuestion directly wit
 </workit-askquestion-hard-gate>
 
 <workit-visual-companion>
-HARD-GATE: NEVER offer Superpowers visual companion or open a browser tab. For UI wireframes use workflow_present_ascii; for flows use workflow_present_flow. Overrides Superpowers brainstorming visual companion offer.
+HARD-GATE: NEVER offer Superpowers visual companion or open a browser tab. For UI wireframes use workit_present_ascii; for flows use workit_present_flow. Overrides Superpowers brainstorming visual companion offer.
 </workit-visual-companion>
 
 <workit-no-worktrees>
-HARD-GATE: NEVER using-git-worktrees or git worktree. In-place feature/* or bugfix/* checkout only via workflow_resolve_branch + workflow_branch_setup. Dirty tree → native AskQuestion before checkout.
+HARD-GATE: NEVER using-git-worktrees or git worktree. In-place feature/* or bugfix/* checkout only via workit_resolve_branch + workit_branch_setup. Dirty tree → native AskQuestion before checkout.
 </workit-no-worktrees>
 
 <workit-sdd-path>
-HARD-GATE: NEVER .superpowers/sdd. ALWAYS workflow_sdd_context with plan_path first — resolves canonical docs/<slug>/sdd/ and creates nothing (no empty ledger; progress.md appears only on the first confirmed append). workflow_sdd_task_brief, workflow_sdd_review_package, workflow_sdd_append_progress only.
+HARD-GATE: NEVER .superpowers/sdd. ALWAYS workit_sdd_context with plan_path first — resolves canonical docs/<slug>/sdd/ and creates nothing (no empty ledger; progress.md appears only on the first confirmed append). workit_sdd_task_brief, workit_sdd_review_package, workit_sdd_append_progress only.
 </workit-sdd-path>
 
 <workit-todowrite>
-HARD-GATE: After workflow_sdd_context, call Cursor TodoWrite with returned todos (merge: false). SDD ledger is persistence — TodoWrite is the native task list UI. Keep in_progress/completed in sync each task.
+HARD-GATE: After workit_sdd_context, call Cursor TodoWrite with returned todos (merge: false). SDD ledger is persistence — TodoWrite is the native task list UI. Keep in_progress/completed in sync each task.
 </workit-todowrite>
 
 <workit-superpowers-doc-contract>

package/dist/mcp-server.js

@@ -20868,7 +20868,7 @@ var resolveBranchPolicyFor = (workspaceRoot) => resolveBranchPolicy(readConfig()
     if (dirty) {
       if (stash !== "yes") {
         return {
-          error: "dirty working tree — ask with native question, then call workflow_branch_setup with stash=yes"
+          error: "dirty working tree — ask with native question, then call workit_branch_setup with stash=yes"
         };
       }
       try {
@@ -21621,7 +21621,7 @@ var runGit = (cwd, args) => {
 - Entries should be human-readable and user-facing.
 - Do not use raw commit messages as changelog bullets.
 - MERGE into existing ### Category under [Unreleased] — never append a second ### Added / ### Fixed block.
-- Apply with the native workflow_changelog_apply tool only (not hand-edits under Unreleased).
+- Apply with the native workit_changelog_apply tool only (not hand-edits under Unreleased).
 - If Unreleased already has duplicate category headings, normalize_only first.`;
 var init_repo_context = __esm(() => {
   init_vcs_config();
@@ -24182,7 +24182,7 @@ function sddContext({
     task_count,
     flow: { spec: flow.spec, plan: flow.plan, menu: flow.menu },
     todowrite_required: true,
-    todowrite_hint: "REQUIRED: Call OpenCode todowrite with todos from this result so the native task list shows progress. Before each task set status in_progress; after workflow_sdd_append_progress set it completed."
+    todowrite_hint: "REQUIRED: Call OpenCode todowrite with todos from this result so the native task list shows progress. Before each task set status in_progress; after workit_sdd_append_progress set it completed."
   };
 }
 function sddTaskBrief({
@@ -24636,7 +24636,7 @@ var COORDINATOR_RECOVERY_TEXT, CURSOR_SUBAGENT_UNSUPPORTED_TEXT, MENU_CHOICES, e
   const file = flowPath(root, slug);
   const rel = path20.posix.join("docs", slug, "sdd", "flow.json");
   if (!existsSync12(file)) {
-    return err2("flow_not_activated", `flow not activated for ${slug} — run workflow_flow_status first`);
+    return err2("flow_not_activated", `flow not activated for ${slug} — run workit_flow_status first`);
   }
   let text;
   try {
@@ -25397,13 +25397,13 @@ var COORDINATOR_RECOVERY_TEXT, CURSOR_SUBAGENT_UNSUPPORTED_TEXT, MENU_CHOICES, e
     return effective;
   const state = effective.state;
   if (state.spec.status !== "approved") {
-    return err2("spec_not_approved", `spec not approved (status: ${state.spec.status}). Run workflow_spec_approve after the user's approval.`);
+    return err2("spec_not_approved", `spec not approved (status: ${state.spec.status}). Run workit_spec_approve after the user's approval.`);
   }
   if (state.plan.status !== "approved") {
-    return err2("plan_not_approved", `plan not approved (status: ${state.plan.status}). Run workflow_plan_approve after the user's approval.`);
+    return err2("plan_not_approved", `plan not approved (status: ${state.plan.status}). Run workit_plan_approve after the user's approval.`);
   }
   if (opts.requireMenu && !state.menu.presented) {
-    return err2("menu_not_presented", "post-plan menu not presented. Record the native question answer with workflow_plan_menu.");
+    return err2("menu_not_presented", "post-plan menu not presented. Record the native question answer with workit_plan_menu.");
   }
   if (opts.requireDocs) {
     const validated = docsValidate({
@@ -26054,7 +26054,7 @@ var configPath = () => process.env.WORKFLOW_DOCS_REPO_CONFIG ?? path22.join(conf
   const workspaceRootCanonical = resolved.layout.workspace;
   const repoPath = docsRepoPath();
   if (!repoPath)
-    return { ok: false, error: "docs repo not linked — run workflow_docs_repo_link" };
+    return { ok: false, error: "docs repo not linked — run workit_docs_repo_link" };
   const repoValid = validateDocsRepo(repoPath);
   if (!repoValid.ok)
     return { ok: false, error: repoValid.error };
@@ -26985,7 +26985,7 @@ async function postUpdate({
         postedComment: true,
         loggedMinutes: 0,
         error: time3.error,
-        retry: "workflow_youtrack_log_time"
+        retry: "workit_youtrack_log_time"
       };
     }
     return { ok: true, issueId, postedComment: true, loggedMinutes: minutes };
@@ -27659,7 +27659,7 @@ var logger, readServerVersion = () => {
     }
   });
 }, changelogCategorySchema, lifecycleTool = (action, description) => {
-  registerTool(`workflow_plan_${action}`, {
+  registerTool(`workit_plan_${action}`, {
     description,
     inputSchema: {
       plan_path: exports_external.string(),
@@ -27739,7 +27739,7 @@ var init_server3 = __esm(async () => {
     name: "workit",
     version: VERSION
   });
-  registerTool("workflow_verify", {
+  registerTool("workit_verify", {
     description: "Run project validation scripts (verify-project.sh). Defaults to Cursor workspace; pass workspace_root when the target repo differs.",
     inputSchema: {
       dry_run: exports_external.boolean().optional(),
@@ -27756,7 +27756,7 @@ var init_server3 = __esm(async () => {
       workspace_root: cwd
     }));
   });
-  registerTool("workflow_doctor", {
+  registerTool("workit_doctor", {
     description: "Run the offline workit doctor and report installation health. Defaults to Cursor workspace; pass workspace_root when the target repo differs.",
     inputSchema: {
       workspace_root: workspaceRootSchema
@@ -27765,7 +27765,7 @@ var init_server3 = __esm(async () => {
     const report = runDoctor({ host: "cursor", cwd: workspace_root });
     return jsonResult(report);
   });
-  registerTool("workflow_pr_context", {
+  registerTool("workit_pr_context", {
     description: "Gather PR-ready repository context. On feature/* or bugfix/*, fetches and fast-forwards develop + current branch before diffing against develop.",
     inputSchema: {
       range: exports_external.string().optional(),
@@ -27829,7 +27829,7 @@ var init_server3 = __esm(async () => {
       stderr: stderr || undefined
     }));
   });
-  registerTool("workflow_pr_create", {
+  registerTool("workit_pr_create", {
     description: "Create GitLab MR or GitHub PR via glab/gh using vcs.json — requires confirmed: true",
     inputSchema: {
       confirmed: exports_external.boolean(),
@@ -27857,7 +27857,7 @@ var init_server3 = __esm(async () => {
     }
     return jsonResult(withWorkspace(workspace_root, { ...data }));
   });
-  registerTool("workflow_changelog_context", {
+  registerTool("workit_changelog_context", {
     description: "Gather changelog update context. Defaults to Cursor workspace; pass workspace_root when the target repo differs.",
     inputSchema: {
       range: exports_external.string().optional(),
@@ -27874,7 +27874,7 @@ var init_server3 = __esm(async () => {
       diff_stat: sections["Diff Stat"] ?? "",
       files: sections["Changed Files"] ?? "",
       unreleased,
-      apply_hint: "ALWAYS merge via workflow_changelog_apply — never hand-edit ### Added/Changed/… under [Unreleased].",
+      apply_hint: "ALWAYS merge via workit_changelog_apply — never hand-edit ### Added/Changed/… under [Unreleased].",
       workspace_root: cwd,
       stdout,
       exitCode,
@@ -27889,7 +27889,7 @@ var init_server3 = __esm(async () => {
     "Fixed",
     "Security"
   ]);
-  registerTool("workflow_changelog_apply", {
+  registerTool("workit_changelog_apply", {
     description: "Merge Keep a Changelog bullets into ## [Unreleased] under the correct ### category. Collapses duplicate category headings. NEVER append a second ### Added block.",
     inputSchema: {
       entries: exports_external.union([
@@ -27917,7 +27917,7 @@ var init_server3 = __esm(async () => {
       unreleased: changelogUnreleasedStats(workspace_root, changelogPath)
     }));
   });
-  registerTool("workflow_release_notes_context", {
+  registerTool("workit_release_notes_context", {
     description: "Gather release notes context. Defaults to Cursor workspace; pass workspace_root when the target repo differs.",
     inputSchema: {
       range_or_tag: exports_external.string().min(1),
@@ -27941,7 +27941,7 @@ var init_server3 = __esm(async () => {
       stderr: stderr || undefined
     }));
   });
-  registerTool("workflow_docs_context", {
+  registerTool("workit_docs_context", {
     description: "Gather docs refresh context. Defaults to Cursor workspace; pass workspace_root when the target repo differs.",
     inputSchema: {
       range: exports_external.string().optional(),
@@ -27961,7 +27961,7 @@ var init_server3 = __esm(async () => {
       stderr: stderr || undefined
     }));
   });
-  registerTool("workflow_git_context", {
+  registerTool("workit_git_context", {
     description: "Gather git status for commit skill. Defaults to Cursor workspace; pass workspace_root when the target repo differs.",
     inputSchema: {
       paths: exports_external.array(exports_external.string()).optional(),
@@ -27971,7 +27971,7 @@ var init_server3 = __esm(async () => {
     const data = gitContext(workspace_root, paths ?? []);
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_resolve_branch", {
+  registerTool("workit_resolve_branch", {
     description: "Resolve feature/* or bugfix/* branch from spec/plan. Returns current_branch, dirty, needs_checkout. No worktrees.",
     inputSchema: {
       spec_path: exports_external.string(),
@@ -27984,7 +27984,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_branch_setup", {
+  registerTool("workit_branch_setup", {
     description: "In-place checkout of feature/* or bugfix/* branch. Stash required when dirty. NEVER uses worktrees.",
     inputSchema: {
       action: exports_external.enum(["setup", "reapply_stash"]).optional(),
@@ -28005,7 +28005,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_sdd_context", {
+  registerTool("workit_sdd_context", {
     description: "Resolve canonical docs/<slug>/sdd/ paths; creates nothing (progress.md appears only on the first confirmed append). NEVER use .superpowers/sdd.",
     inputSchema: {
       slug: exports_external.string().optional(),
@@ -28018,7 +28018,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_sdd_task_brief", {
+  registerTool("workit_sdd_task_brief", {
     description: "Write task-N-brief.md under docs/<slug>/sdd/",
     inputSchema: {
       sdd_dir: exports_external.string(),
@@ -28041,7 +28041,7 @@ var init_server3 = __esm(async () => {
     });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_sdd_review_package", {
+  registerTool("workit_sdd_review_package", {
     description: "Write review diff under SDD dir between base and head SHAs",
     inputSchema: {
       sdd_dir: exports_external.string(),
@@ -28066,7 +28066,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_sdd_append_progress", {
+  registerTool("workit_sdd_append_progress", {
     description: "Append one validated line to docs/<slug>/sdd/progress.md",
     inputSchema: {
       progress_path: exports_external.string(),
@@ -28085,7 +28085,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_sdd_append_advisory", {
+  registerTool("workit_sdd_append_advisory", {
     description: "Append a validated advisory line to docs/<slug>/sdd/advisories.md (coordinator-owned)",
     inputSchema: {
       advisories_path: exports_external.string(),
@@ -28105,7 +28105,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error, code: data.code });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_docs_branch", {
+  registerTool("workit_docs_branch", {
     description: "Resolve branch for spec/plan authors: keep current feature|bugfix or create from the configured base.",
     inputSchema: {
       plan_path: exports_external.string().optional(),
@@ -28118,7 +28118,7 @@ var init_server3 = __esm(async () => {
       return jsonResult(withWorkspace(workspace_root, { error: data.error }));
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_docs_layout", {
+  registerTool("workit_docs_layout", {
     description: "Canonical docs layout: prepare creates missing docs/ and docs/<slug>/; migrate detects legacy docs/superpowers/ and copies safe pairs after a native Migrate safely / Not now question",
     inputSchema: {
       action: exports_external.enum(["prepare", "migrate"]).default("prepare"),
@@ -28162,7 +28162,7 @@ var init_server3 = __esm(async () => {
       return jsonResult(withWorkspace(workspace_root, { error: result.error }));
     return jsonResult(withWorkspace(workspace_root, result));
   });
-  registerTool("workflow_docs_validate", {
+  registerTool("workit_docs_validate", {
     description: "Hard-fail validate spec/plan headers, link, branch, task order; returns quality findings (hard/warning). Defaults to Cursor workspace; pass workspace_root when paths are relative to another repo.",
     inputSchema: {
       spec_path: exports_external.string(),
@@ -28176,7 +28176,7 @@ var init_server3 = __esm(async () => {
     }
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_plan_tasks", {
+  registerTool("workit_plan_tasks", {
     description: "Parse plan ### Task N sections into structured tasks with section_text. Defaults to Cursor workspace; pass workspace_root when paths are relative to another repo.",
     inputSchema: {
       plan_path: exports_external.string(),
@@ -28200,7 +28200,7 @@ var init_server3 = __esm(async () => {
     }
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_handoff_prompt", {
+  registerTool("workit_handoff_prompt", {
     description: "Build copy-paste handoff prompt for next session. Defaults to Cursor workspace; pass workspace_root when spec/plan paths are relative to another repo.",
     inputSchema: {
       message: exports_external.string(),
@@ -28388,7 +28388,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(data.data);
   });
-  registerTool("workflow_youtrack_verify_token", {
+  registerTool("workit_youtrack_verify_token", {
     description: "Read-only YouTrack token test (GET /api/users/me). No work items created.",
     inputSchema: {}
   }, async () => {
@@ -28400,7 +28400,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error ?? "token invalid", ...data });
     return jsonResult(data);
   });
-  registerTool("workflow_youtrack_parse_issue", {
+  registerTool("workit_youtrack_parse_issue", {
     description: "Parse YouTrack issue URL or bare id (e.g. NSR-40) into issueId",
     inputSchema: {
       issue_ref: exports_external.string().describe("YouTrack URL or issue id, e.g. https://…/issue/NSR-40 or NSR-40")
@@ -28411,7 +28411,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(data);
   });
-  registerTool("workflow_youtrack_context", {
+  registerTool("workit_youtrack_context", {
     description: "YouTrack config, greeting, issue resolution (from issue_url/id or meetings)",
     inputSchema: {
       mode: exports_external.enum(["meetings", "task"]).optional(),
@@ -28440,7 +28440,7 @@ var init_server3 = __esm(async () => {
     }
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_youtrack_parse_duration", {
+  registerTool("workit_youtrack_parse_duration", {
     description: "Parse duration text (e.g. 1h 30m) to integer minutes",
     inputSchema: {
       text: exports_external.string(),
@@ -28452,7 +28452,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_youtrack_log_time", {
+  registerTool("workit_youtrack_log_time", {
     description: "POST YouTrack work item (time only, no comment)",
     inputSchema: {
       issueId: exports_external.string(),
@@ -28473,7 +28473,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_youtrack_draft", {
+  registerTool("workit_youtrack_draft", {
     description: "Build ES-CL comment markdown without posting (envelope only by default)",
     inputSchema: {
       issueId: exports_external.string(),
@@ -28485,7 +28485,7 @@ var init_server3 = __esm(async () => {
       facts: exports_external.record(exports_external.any()).optional()
     }
   }, async (input) => jsonResult(buildDraft(input)));
-  registerTool("workflow_youtrack_post", {
+  registerTool("workit_youtrack_post", {
     description: "Post YouTrack comment and optional time — requires confirmed: true",
     inputSchema: {
       confirmed: exports_external.boolean(),
@@ -28506,7 +28506,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(withWorkspace(workspace_root, data));
   });
-  registerTool("workflow_present_ascii", {
+  registerTool("workit_present_ascii", {
     description: "Render deterministic ASCII UI wireframe from JSON spec",
     inputSchema: {
       title: exports_external.string().optional(),
@@ -28519,7 +28519,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(data.data);
   });
-  registerTool("workflow_present_flow", {
+  registerTool("workit_present_flow", {
     description: "Render mermaid flowchart from JSON nodes/edges",
     inputSchema: {
       title: exports_external.string().optional(),
@@ -28541,7 +28541,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: data.error });
     return jsonResult(data.data);
   });
-  registerTool("workflow_flow_status", {
+  registerTool("workit_flow_status", {
     description: "Read the spec/plan approval flow state for a workflow; on first read it records flow activation and canonical document paths (FG-01)",
     inputSchema: {
       plan_path: exports_external.string().optional(),
@@ -28577,7 +28577,7 @@ var init_server3 = __esm(async () => {
       flow_path: `docs/${slug}/sdd/flow.json`
     });
   });
-  registerTool("workflow_spec_approve", {
+  registerTool("workit_spec_approve", {
     description: "Advance spec status with the Cursor policy-only confirmation: draft -> approved in a single call. The self-review validation runs automatically inside the transition; only the final approval asks for your confirmation. Cursor records attested: false (the MCP cannot observe AskQuestion results); there is no evidence argument (CA-42).",
     inputSchema: {
       spec_path: exports_external.string(),
@@ -28593,7 +28593,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: result.error, code: result.code });
     return jsonResult({ spec: spec_path, status: readFlowState(workspace, slug).spec.status });
   });
-  registerTool("workflow_plan_approve", {
+  registerTool("workit_plan_approve", {
     description: "Advance plan status with the Cursor policy-only confirmation: draft -> approved in a single call. The self-review validation runs automatically inside the transition; only the final approval asks for your confirmation. Requires approved spec. Cursor records attested: false; there is no evidence argument (CA-42).",
     inputSchema: {
       plan_path: exports_external.string(),
@@ -28609,7 +28609,7 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: result.error, code: result.code });
     return jsonResult({ plan: plan_path, status: readFlowState(workspace, slug).plan.status });
   });
-  registerTool("workflow_plan_menu", {
+  registerTool("workit_plan_menu", {
     description: "Record the answered post-plan choice menu with the Cursor policy-only confirmation. subagent-driven is rejected as unsupported on Cursor (CA-42); there is no evidence argument.",
     inputSchema: {
       plan_path: exports_external.string(),
@@ -28629,7 +28629,7 @@ var init_server3 = __esm(async () => {
   lifecycleTool("pause", "Pause a running plan with the Cursor policy-only confirmation: active -> paused. The MCP cannot observe AskQuestion results, so it records attested: false; there is no evidence argument (CA-42). Requires plan_path and workspace_root.");
   lifecycleTool("resume", "Resume a paused plan with the Cursor policy-only confirmation: paused -> active. The MCP cannot observe AskQuestion results, so it records attested: false; there is no evidence argument (CA-42). Requires plan_path and workspace_root.");
   lifecycleTool("complete", "Complete a running plan with the Cursor policy-only confirmation: active/paused -> completed, after the SDD ledger is complete and repository verification passes. The MCP cannot observe AskQuestion results, so it records attested: false; there is no evidence argument (CA-42). Requires plan_path and workspace_root.");
-  registerTool("workflow_docs_repo_link", {
+  registerTool("workit_docs_repo_link", {
     description: "Link the component docs repo in the toolkit config",
     inputSchema: {
       path: exports_external.string(),
@@ -28641,11 +28641,11 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: result.error });
     return jsonResult({ path: result.path });
   });
-  registerTool("workflow_docs_list", {
+  registerTool("workit_docs_list", {
     description: "List local specs with docs-repo promotion status",
     inputSchema: { workspace_root: workspaceRootSchema }
   }, async ({ workspace_root }) => jsonResult(listSpecs(workspace_root)));
-  registerTool("workflow_docs_promote", {
+  registerTool("workit_docs_promote", {
     description: "Promote a spec (+plan) to the linked docs repo with quality gate",
     inputSchema: {
       slug: exports_external.string(),
@@ -28663,11 +28663,11 @@ var init_server3 = __esm(async () => {
       index_updated: result.index_updated
     });
   });
-  registerTool("workflow_template_list", {
+  registerTool("workit_template_list", {
     description: "List editable templates with their source",
     inputSchema: { workspace_root: workspaceRootSchema }
   }, async () => jsonResult({ templates: listTemplates() }));
-  registerTool("workflow_template_edit", {
+  registerTool("workit_template_edit", {
     description: "Write an edited template to the toolkit config dir",
     inputSchema: {
       name: exports_external.enum(["issue-update", "greeting", "headers"]),
@@ -28680,11 +28680,11 @@ var init_server3 = __esm(async () => {
       return jsonResult({ error: result.error });
     return jsonResult({ path: result.path });
   });
-  registerTool("workflow_rule_list", {
+  registerTool("workit_rule_list", {
     description: "List canonical rules (config) with platforms",
     inputSchema: { workspace_root: workspaceRootSchema }
   }, async () => jsonResult({ rules: listRules() }));
-  registerTool("workflow_rule_edit", {
+  registerTool("workit_rule_edit", {
     description: "Write a canonical rule to the toolkit config dir",
     inputSchema: {
       name: exports_external.string(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@brainervirus/workit-cursor",
-  "version": "0.8.9",
+  "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.9",
+    "@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