@brainervirus/workit-cursor 0.4.0

package/mcp.json

@@ -0,0 +1,12 @@
+{
+  "mcpServers": {
+    "workit": {
+      "command": "bash",
+      "args": [
+        "-lc",
+        "exec \"$HOME/.local/share/workflow-toolkit/packages/workit-core/scripts/run-cursor-mcp.sh\" \"$0\"",
+        "${workspaceFolder}"
+      ]
+    }
+  }
+}

package/package.json

@@ -0,0 +1,36 @@
+{
+  "name": "@brainervirus/workit-cursor",
+  "version": "0.4.0",
+  "private": false,
+  "description": "Workit Cursor plugin: MCP server, hooks, rules, marketplace manifest (thin over @brainervirus/workit-core)",
+  "license": "MIT",
+  "keywords": [
+    "cursor",
+    "mcp",
+    "workflow",
+    "agent"
+  ],
+  "bugs": {
+    "url": "https://github.com/BrainerVirus/workflow-toolkit/issues"
+  },
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/BrainerVirus/workflow-toolkit.git"
+  },
+  "files": [
+    "mcp/",
+    "hooks/",
+    "rules/",
+    "skills/",
+    ".cursor-plugin/",
+    "mcp.json",
+    "marketplace.json"
+  ],
+  "type": "module",
+  "publishConfig": {
+    "access": "public"
+  },
+  "dependencies": {
+    "@brainervirus/workit-core": "^0.4.0"
+  }
+}

package/rules/ask-question-only.mdc

@@ -0,0 +1,49 @@
+---
+description: ALL user choices must use Cursor AskQuestion — never A/B/C in chat
+alwaysApply: true
+---
+
+# AskQuestion only (HARD-GATE)
+
+**Overrides** Superpowers brainstorming “ask in chat / A/B/C text options” and any skill that suggests conversational multiple choice.
+
+## Required path for every decision
+
+When the user must choose (clarifying questions, product identity, layout, yes/no, confirm, branch, stash, YouTrack, approaches, or how to execute a completed plan):
+
+1. Call Cursor's native **`AskQuestion`** with a workflow-specific title, prompt, and options.
+2. Wait for the tool result — do **not** also paste the options in the chat message.
+3. If native `AskQuestion` is unavailable in the current mode, ask one concise plain-text question.
+
+## Forbidden (always)
+
+- Letter options in markdown: `A)`, `B)`, `C)`, `Reply with A, B, or C`
+- Bullet / numbered choice lists meant as the answer UI
+- “First clarifying question” blocks that list options in prose
+- Asking the user to type yes/no when `yes_no` + AskQuestion exists
+
+## Mapping
+
+| Need | Kind |
+|------|------|
+| 2+ custom choices (brainstorming, identity, layout, …) | `pick_option` + title, prompt, `id:label` args |
+| Yes / no | `yes_no` |
+| Branch / stash / YouTrack / VCS | named kinds from the tool |
+| Plan completed; choose execution method | `plan_execution` + saved plan path |
+
+One AskQuestion per turn when possible. Open-ended free text (no options) may stay in chat — **as soon as there are options, AskQuestion is mandatory**.
+
+## Superpowers writing-plans override
+
+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:
+
+- Subagent-driven → `wk-implement`
+- Inline → execute in this session
+- Handoff → `/wk-handoff` (new session only)
+- Review spec first
+- Review plan first
+- Cursor's built-in **Other** response, always last
+
+No `--stay` option in this menu.

package/rules/cursor-todowrite.mdc

@@ -0,0 +1,14 @@
+---
+description: SDD ledger AND Cursor TodoWrite — both required for plan execution
+alwaysApply: true
+---
+
+# TodoWrite UI (HARD-GATE)
+
+When executing a plan / SDD handoff:
+
+1. MCP `workflow_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`.
+
+Never skip TodoWrite because the SDD ledger exists.

package/rules/no-worktrees.mdc

@@ -0,0 +1,26 @@
+---
+description: NEVER use git worktrees — in-place feature/* or bugfix/* checkout only
+alwaysApply: true
+---
+
+# No worktrees (HARD-GATE)
+
+**Overrides** Superpowers `using-git-worktrees` skill and any execution contract that mentions worktrees.
+
+## Policy
+
+- **NEVER** invoke `using-git-worktrees`
+- **NEVER** run `git worktree add` or any worktree command
+- Branch work is **in-place only**: `feature/*` or `bugfix/*`
+- Never commit on `main`, `develop`, `master`, or `prod`
+
+## Required flow (before Task 1)
+
+1. MCP `workflow_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`
+
+## Tools only
+
+Do not infer branch or stash state from manual `git status`. Use MCP tools.

package/rules/sdd-docs-path.mdc

@@ -0,0 +1,22 @@
+---
+description: SDD artifacts live under docs/<slug>/sdd — never .superpowers/sdd
+alwaysApply: true
+---
+
+# SDD path (HARD-GATE)
+
+**Overrides** Superpowers `subagent-driven-development` ledger check at `.superpowers/sdd/progress.md`.
+
+## Required
+
+1. MCP `workflow_sdd_context` with `plan_path` — **always**, including fresh projects
+2. Use returned `sdd_dir` (`docs/<plan-basename>/sdd/`) for all SDD artifacts
+3. `workflow_sdd_task_brief`, `workflow_sdd_review_package`, `workflow_sdd_append_progress` — never Superpowers `sdd-workspace` script
+
+## Forbidden
+
+- `.superpowers/sdd/` for progress, briefs, or review diffs
+- `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** `docs/<slug>/sdd/progress.md`.

package/skills/wk-changelog/SKILL.md

@@ -0,0 +1,75 @@
+---
+name: wk-changelog
+description: Update CHANGELOG.md via workflow_changelog_context + workflow_changelog_apply. Use for /wk-changelog or "update the changelog".
+---
+
+# Changelog — Keep a Changelog Update
+
+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.).
+
+**Workspace root:** defaults to the Cursor workspace. Pass `workspace_root` when the user names a different repository path.
+
+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.
+
+## Step 2 — Decide entries (do not edit the file yet)
+
+Follow Keep a Changelog 1.1.0:
+
+- Target `## [Unreleased]` only (unless the user asks to cut a version).
+- Categories: `Added`, `Changed`, `Deprecated`, `Removed`, `Fixed`, `Security`.
+- Human-readable bullets, not raw commit messages.
+- Group by user-visible behavior, not by file.
+- Skip internal refactors / CI / tests / formatting unless they affect users.
+- If there are no meaningful user-visible changes, stop — do not invent entries.
+
+## Step 3 — Apply via tool (required)
+
+Call MCP `workflow_changelog_apply` with the new bullets. Examples:
+
+```json
+{
+  "entries": {
+    "Added": ["**Foo API** — public endpoint for bar"],
+    "Fixed": ["**Login redirect** — stop loop on expired session"]
+  }
+}
+```
+
+or
+
+```json
+{
+  "entries": [
+    { "category": "Added", "text": "**Foo API** — public endpoint for bar" }
+  ]
+}
+```
+
+### HARD-GATE
+
+- **NEVER** hand-edit `CHANGELOG.md` to append a new `### Added` / `### Changed` / … block under `[Unreleased]`.
+- The apply tool **merges** into the existing category heading (or creates one category once).
+- Duplicate identical bullets are skipped.
+- Do not update package versions or tags.
+- Do not commit.
+
+## Output
+
+After the tool returns ok, summarize:
+
+```md
+Changelog update:
+
+- <entry or reason no update was needed>
+
+Files changed:
+
+- CHANGELOG.md
+```