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.