Can Spec Kit identify which completed tasks are affected by a requirement change?

[chuthuyquynh38-del]

requirement changes halfway through implementation.

For example, changing an authentication requirement might affect database design, API endpoints, and several tasks that are already marked complete.

Would rerunning /speckit.analyze be enough to identify those downstream impacts, or is there a better way to trace which completed tasks need to be revisited?

I've been exploring structured requirements and task planning with Myspec and this is one area I'm particularly interested in. Curious how others handle it with Spec Kit.

[markuswondrak]

Analyze should pick it up. It checks if spec, plan and tasks align. If you change spec, when tasks already in place this diff should recognized by the agent - given you use a capable model for it.