How to add a requirement after implementation?

[simon-k]

I'm not sure about the flow here.

I've run the

/speckit.specify
/speckit.clarify
/speckit.plan
/speckit.tasks
/speckit.analyze and
/speckit.implement commands.

Now here's the thing. Everything looks good, but I have a few things that I want to add to the spec. Let's say I have a login form. When the user enters wrong credentials the form just resets. I want to add a functional requirement that the user should be informed if wrong credentials are entered. I assume when adding that the plan.md and tasks.md must be updated accordingly.

What's the best way to do this? I do not want to create an entire new feature for this.

[massimogentilini]

See my idea: #1255

I don't know if this the answer you want but the kind of change you describe is more in the realm of "made a small CR" than a "new feature".

Also because if you work with speckit and a coding agent a spec like a login form will have, 99% sure, the requirement to gracefully manage wrong credentials of forgotten passwords, if not in the specify phase for sure the clarify step.

But the question remains, a spec change like "show also this field from the database" how it should be managed? I did a proposal...

[simon-k]

So I did this.

After the implementation I wanted to change the hosting in Azure from Container App to App Service.

/speckit.plan Update the plan. I do not want to use Azure Container Apps. Instead I want to use Azure App Service forthe backend and Static Web App for the frontend

/speckit.tasks update the tasks list so it reflects the move from container apps to app service plan and static web app

/speckit.analyze

Task T166 was the one about creating bicep for hosting in Azure. So I just told Spec Kit to implement that one

T166 update existing bicep code to match plan of using app service and static web app instead oc fontainers. Also update the quickstart accordingly

Seemed to work fine. After that my spec 001 was done and dusted. I did not have to create a new spec where I changed the hosting from container to app service.

I don't know if this is the recommended way of doing it.