Skip to content
Development
Command

/from-plan

Convert a Claude Code plan (or any spec file) into a task file and optionally hand it off to Cursor.

From plugin
cursor-plugin-cc
2811 skills1 agent11 commands
Install
$ npx -y skills add freema/cursor-plugin-cc --agent claude-code

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/from-plan

Context preview

What this command does when you run it.

Convert a Claude Code plan (or any spec file) into a task file and optionally hand it off to Cursor.

Command definition

from-plan.md
description: Convert a Claude Code plan (or any spec file) into a task file and optionally hand it off to Cursor.
argument-hint: '[plan-name-fragment|path] [--delegate] [--out-dir <dir>] [--in-place] [--model <id>] [--background] [--list]'
allowed-tools: Bash(node:*)

!`node "${CLAUDE_PLUGIN_ROOT}/scripts/from-plan.mjs" -- "$ARGUMENTS"`

Render the output verbatim. The command has two modes:

  • **Preview + hand back** (default): it writes the task file, then prints the exact `/cursor:delegate @…` command. Run that command yourself after reviewing the task file.
  • **Auto-delegate** (`--delegate` or `--yes`): it writes the task file AND immediately calls `/cursor:delegate`, so the output merges into a single flow.

Without arguments it picks the newest plan under `~/.claude/plans/`. Pass a name fragment (e.g. `dark-mode`) or any path (e.g. `PRPs/dark-mode.md`) to pick a specific one. `--list` shows the 15 most recent plan files.

**Where the task file lands** — derived from the spec, most- to least-specific:

1. `--out-dir <dir>` for a single run 2. **the directory the source spec lives in** — pass `PRPs/018.md` and the task file joins it there, in whichever repo that is 3. the `CURSOR_PLUGIN_CC_TASKS_DIR` environment variable 4. the per-repo default: `/cursor:setup --tasks-dir PRPs` (reset with `--no-tasks-dir`) 5. `tasks/`

Rule 2 means spec-driven projects need no configuration, and it keeps working when specs are centralised in one repo while code lives in siblings. Rules 3–5 only come into play for Claude's own plan-mode files, which have no project location to inherit. Relative values resolve against the repo root, so the destination does not move when you run the command from a subdirectory.

The spec may live **outside** the current repo. When it does, Cursor is handed an absolute path instead of `@path` (which cannot leave the repo root), and told to apply its changes in the current repository. Report that note to the user when it appears.

**`--in-place`** skips the conversion entirely and delegates the source document as written — no task file is created. Use it when your spec already _is_ the task (PRP, Spec Kit, OpenSpec). Works across repos.

Read more
Ships withcursor-plugin-cc

Claude plans. Cursor writes. Claude reviews. A Claude Code plugin that delegates coding execution to Cursor's Composer — without ever leaving the Claude Code TUI.

Get the whole plugin, auto-invoked
Stats
28
Stars
0
Views
6
Forks
Active
Maintenance
JavaScript
Language
MIT
License
1d ago
Last commit
3mo ago
Created

Repo: freema/cursor-plugin-cc