fix(cursor): update skill paths from .cursor/rules/ to .cursor/skills/

The Cursor Agent CLI now discovers skills from .cursor/skills/ instead
of the old .cursor/rules/ directory. Update all references across
create-plan and implement-plan Cursor variants and docs.

skills/create-plan/cursor/SKILL.md

@@ -15,7 +15,7 @@ This skill wraps the current Superpowers flow for the Cursor Agent CLI (`cursor-
 3. Review the plan iteratively with a second model/provider
 4. Persist a local execution package in `ai_plan/YYYY-MM-DD-<short-title>/`
 
-**Core principle:** Cursor Agent CLI discovers skills from `.cursor/rules/` (repo-local or `~/.cursor/rules/` global). It also reads `AGENTS.md` at the repo root for additional instructions.
+**Core principle:** Cursor Agent CLI discovers skills from `.cursor/skills/` (repo-local or `~/.cursor/skills/` global). It also reads `AGENTS.md` at the repo root for additional instructions.
 
 ## Prerequisite Check (MANDATORY)
 
@@ -23,7 +23,7 @@ Required:
 - Cursor Agent CLI: `cursor-agent --version` (install via `curl https://cursor.com/install -fsS | bash`). The binary is `cursor-agent` (installed to `~/.local/bin/`). Some environments alias it as `cursor agent` (subcommand of the Cursor IDE CLI) — both forms work, but this skill uses `cursor-agent` throughout.
 - `jq` (required only if using `cursor` as the reviewer CLI): `jq --version` (install via `brew install jq` or your package manager)
 - Superpowers repo: `https://github.com/obra/superpowers`
-- Superpowers skills installed under `.cursor/rules/` (repo-local) or `~/.cursor/rules/` (global)
+- Superpowers skills installed under `.cursor/skills/` (repo-local) or `~/.cursor/skills/` (global)
 - `superpowers:brainstorming`
 - `superpowers:writing-plans`
 
@@ -31,19 +31,19 @@ Verify before proceeding:
 
 ```bash
 cursor-agent --version
-test -f .cursor/rules/superpowers/brainstorming/SKILL.md || test -f ~/.cursor/rules/superpowers/brainstorming/SKILL.md
-test -f .cursor/rules/superpowers/writing-plans/SKILL.md || test -f ~/.cursor/rules/superpowers/writing-plans/SKILL.md
+test -f .cursor/skills/superpowers/brainstorming/SKILL.md || test -f ~/.cursor/skills/superpowers/brainstorming/SKILL.md
+test -f .cursor/skills/superpowers/writing-plans/SKILL.md || test -f ~/.cursor/skills/superpowers/writing-plans/SKILL.md
 # Only if using cursor as reviewer CLI:
 # jq --version
 ```
 
 If any dependency is missing, stop and return:
 
-`Missing dependency: Superpowers planning skills are required (superpowers:brainstorming, superpowers:writing-plans). Install from https://github.com/obra/superpowers and copy into .cursor/rules/ or ~/.cursor/rules/, then retry.`
+`Missing dependency: Superpowers planning skills are required (superpowers:brainstorming, superpowers:writing-plans). Install from https://github.com/obra/superpowers and copy into .cursor/skills/ or ~/.cursor/skills/, then retry.`
 
 ## Required Skill Invocation Rules
 
-- Invoke relevant skills through workspace discovery (`.cursor/rules/`).
+- Invoke relevant skills through workspace discovery (`.cursor/skills/`).
 - Announce skill usage explicitly:
   - `I've read the [Skill Name] skill and I'm using it to [purpose].`
 - For skills with checklists, track checklist items explicitly in conversation.

skills/create-plan/cursor/templates/continuation-runbook.md

@@ -16,7 +16,7 @@ Do NOT reference planner-private files during implementation.
 
 ## Skill Workflow Guardrails
 
-- Invoke relevant skills before action using workspace discovery (`.cursor/rules/`).
+- Invoke relevant skills before action using workspace discovery (`.cursor/skills/`).
 - Announce which skill is being used and why.
 - If a checklist-driven skill applies, track checklist execution explicitly.
 

skills/create-plan/cursor/templates/milestone-plan.md

@@ -7,7 +7,7 @@
 
 ## Planning Guardrails
 - This plan assumes design was validated before implementation planning.
-- Skills are invoked via workspace discovery (`.cursor/rules/`).
+- Skills are invoked via workspace discovery (`.cursor/skills/`).
 - Milestones require verification + local commits + explicit approval before proceeding.
 
 ## Context