Skip to content

v0.6.0 — spec-derived task destination, lossless section mapping, multi-repo from-plan

Latest

Choose a tag to compare

@freema freema released this 02 Aug 16:51

Fixed

  • /cursor:from-plan no longer drops sections that map to no task slot (#16). 0.5.1's verbatim pass-through only fires when zero intents match, so a spec that partially matched still lost everything else (a PRP's Goal, What and All Needed Context — including its CRITICAL: gotchas). Unclaimed sections are now carried through under ## Additional specification context with the author's original heading casing; only reviewer-facing commentary is still dropped. A ## Goal section now fills the Goal slot.

Changed

  • The task destination is derived from the spec instead of imposed by config (#16). Point /cursor:from-plan at a project spec and the task file is written next to it — PRPs/018-wizard.mdPRPs/<stamp>-018-wizard.md. Resolution order: --out-dir → the spec's own directory → CURSOR_PLUGIN_CC_TASKS_DIR → per-repo tasksDir config → tasks/ (the last three apply only to Claude's own plan-mode files).

Added

  • Multi-repo support (#16): a central spec directory in one repo can drive work in sibling repos — the task file lands beside its spec siblings and Cursor receives an absolute path (@path cannot leave the repo); code changes still land in the invoking repo.
  • /cursor:setup --tasks-dir <dir> / --no-tasks-dir persists a per-repo fallback directory, surfaced in --doctor.
  • /cursor:from-plan --in-place delegates the source spec exactly as written, creating no task file. Works across repos.

Defaults are unchanged for the plan-mode flow: with no spec path, flag, env var or config, output still lands in tasks/ and conversions are byte-identical.

Thanks @willywg for the contribution (#24).