Should /speckit-plan invoke plan mode in cursor?

[ben-aggus-gateway]

I invoked /speckit-plan in a new agent discussion and it immediately said that it should operate in plan mode since I invoked speckit-plan. I proceeded with its suggestion and allowed the cursor mode to change to plan. Is this the expected behavior? Spec kit v 1.0.3

[hamedrabah]

In Spec Kit v1.0.3, /speckit-plan does not require switching Cursor's UI into Plan mode. The Cursor integration installs it as .cursor/skills/speckit-plan/SKILL.md; the plan template describes the workflow and its output files, without a requirement to change Cursor modes.

The workflow runs the setup script and writes plan.md, research.md, and the relevant design artifacts such as data-model.md, contracts/, and quickstart.md. It stops after planning; implementation is a separate step.

So the suggestion you saw appears to be the agent interpreting the word "plan", rather than a mode switch required by Spec Kit. If Cursor's Plan mode prevents it from running the setup script or writing those artifacts, use Agent mode with an explicit scope such as:

Run the speckit-plan skill through its completion report. Write the planning artifacts, but do not implement application code.

The useful completion check is whether the expected files were produced in the feature directory, not which mode label was selected.

AI-assisted response; checked against the v1.0.3 sources linked above. I have not reproduced your specific Cursor session.

[guilhermelinosp]

I don't think /speckit.plan requires Cursor's native Plan Mode.

They are two separate concepts.

speckit.plan is a Spec Kit workflow whose job is to take the specification and technical constraints and generate the implementation planning artifacts, primarily plan.md.

Conceptually:

/speckit.specify
      ↓
spec.md

/speckit.plan
      ↓
plan.md + design artifacts

/speckit.tasks
      ↓
tasks.md

/speckit.implement
      ↓
code

Cursor's Plan Mode, on the other hand, controls how the Cursor agent itself behaves while processing a request.

I don't see anything in the current speckit.plan command definition that explicitly requires switching the host agent into its native Plan Mode.

So if Cursor says something like:

/speckit.plan was invoked, therefore I should switch to Plan Mode

I would interpret that as Cursor inferring a relationship between two similarly named concepts, rather than a Spec Kit requirement.

Using Cursor Plan Mode may still be useful because /speckit.plan is intentionally a planning-heavy operation, but it shouldn't be necessary for correctness.

Spec Kit's actual contract is the generated artifact, not the editor mode:

input: spec + technical context
output: implementation plan

So I would expect both approaches to be valid:

Cursor Agent Mode + /speckit.plan

and:

Cursor Plan Mode + /speckit.plan

with the latter being an optional Cursor-specific behavior rather than something required by Spec Kit itself.