Optional Handler for Automatic Context Refresh

[Giannoulakos]

Summary

Introduce an opt-in handler that triggers a context refresh whenever a user runs a speckit command (or a subset of commands defined by the user).

Problem

Currently, running speckit commands doesn’t automatically detect or sync changes that might not yet be reflected in the corresponding Markdown (.md) files. This can lead to inconsistencies between the project state and documentation.

Proposed Solution

•	Add an optional handler that runs a context refresh before or after executing selected commands.
•	Allow users to specify which commands should trigger the refresh.
•	The handler would check for any unsynced changes and prompt or auto-update the relevant .md files as needed.

Benefits

•	Keeps documentation consistently in sync with project changes.
•	Reduces manual refresh steps.
•	Provides a configurable experience, developers can opt in per workflow.

[efargas]

It would be great that before run out of context tokens size, auto refresh the status, then after summarize chat launch implementation prompt again to continue