Best workflow to fix mistakes in a completed change?

[GitHubGeek]

First of all, thank you for this awesome project 🚀 The 1.0 upgrade is huge!

After running /opsx-apply, and agent has completed all tasks, I realised the feature has an incorrect requirement. What's the best approach to fix issue?

1. Archive the change and start a new one - Archiving incorrect requirements doesn't feel clean?
2. ???

Thanks!

[Darren-cy]

Same question. I wish there could be a documentation about real-life examples of: After running /opsx-apply, incorrect implementation, and adding requirements, etc.

[okansahin]

Artifacts (proposal, design, task) exist for this very reason. If you still encounter a problem even after examining these, it makes sense to define it as a new change.

[mgarciadelojo]

or you can commit more often and then checkout a previous commit to work on the requirements again before implementing. It seems the initial plan wasn't very thorough.

[clay-good]

Closing, there is a documented answer now. @Darren-cy, the real-life-examples page you asked for also exists.

Editing & Iterating on a Change covers this under "When to update vs. start a new change". Short version: same work refined means fix the requirement in place and keep going. Intent genuinely changed means open a new change. Archiving something you already know is wrong was never one of the options, which is the part that felt off to you, correctly.

If you would rather not hand-edit four files to make one requirement change stick, /opsx:update does the revise-and-reconcile pass. Added in #1278, in the default profile as of v1.6.0.