Workflows should adapt for incremental editing of spec/plan/task files (when plan/spec files already exist).

[MRiabov]

Hello. So the unexpected behavior is this:
If you ask a LLM to edit a plan.md with a prompt like attached below, it starts editing it free-style, however it wants. Even after adding "adhere to plan-template.md` it still introduces many unwanted changes.

It's quite obvious that when plan.md already exists there is no need to rerun plan init scripts, however guidelines on how to edit plans should be provided instead.

In my case, the plan and tasks are already quite long; it took 1 day to edit it properly.

Prompt

/speckit.plan I've just added Functional Requirements FR-023 to FR-027@spec.md#L89-93 , acceptance criteria: @spec.md#L119-123 , and success criteria SC-011 to SC-013
@spec.md#L165-168.

Update the plan to follow these requirements @plan.md. Keep structure to @plan-template.md .

Also, after, edit @plan.md#L105-131 - instead of ...; if something belongs to devops put it into folder_123/devops/ folder, e.g. 123_456/123_456.py. Add 123_456/enums/ too, for only enums. I don't think runtime_checks.py is necessary since it is superseded by @123_utils.py as in@plan.md#L140, and producers.py is @base_456.py. @base_456.py should stay where it is.

DO NOT make major edits. Just add in what new edits are required.

The result still is worse than if I rewrite it completely. But I am losing so much detail if I do!