You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
How to return to the Review phase after Implement Tasks? #355
In the workflow diagram, I see that after "Implement Tasks", besides "ship the change", there's also a "feedback loop" option. How
should I do this? The AI doesn't seem to automatically modify spec.md and tasks.md.
I usually need to explicitly tell it, now have a canned instruction/prompt that tells it to do so. The problem is usually related to the context window – it "forgets" to do things that are a part of a longer cycle, especially after any implementation.
I usually need to explicitly tell it, now have a canned instruction/prompt that tells it to do so. The problem is usually related to the context window – it "forgets" to do things that are a part of a longer cycle, especially after any implementation.
Kind of in a similar situation , have to do a custom prompt to modify what openspec-proposal do .
Hopefully we get some some new prompts like :
openspec-update ($put your instruction).
openspec-sync (summarize previous conversation and make change accordingly )
Editing & Iterating on a Change answers it under "How do I go back to review after implementing?". The honest answer is that you never left. Review is not a phase you exit, so there is nothing to return to: open the artifacts, edit them, keep going. For a structured pass, /opsx:verify reads your artifacts and your code and reports where they disagree.
@pexa-dnugent, on the "it forgets to update spec.md and tasks.md" problem: /opsx:update is the explicit way to ask for that revision instead of hoping the model remembers across a long cycle. Added in #1278, default profile as of v1.6.0. It may cover most of what your canned prompt has been doing.
Activity
pexa-dnugent commentedon Dec 10, 2025
I usually need to explicitly tell it, now have a canned instruction/prompt that tells it to do so. The problem is usually related to the context window – it "forgets" to do things that are a part of a longer cycle, especially after any implementation.
yl10030270 commentedon Dec 11, 2025
Kind of in a similar situation , have to do a custom prompt to modify what openspec-proposal do .
Hopefully we get some some new prompts like :
docs: close recurring gaps (existing projects, editing changes, unins…
docs: comprehensive overhaul — discoverability, explore-first, and cl…
docs: comprehensive overhaul — discoverability, explore-first, and cl…
clay-good commentedon Jul 23, 2026
Closing, this now has a page.
Editing & Iterating on a Change answers it under "How do I go back to review after implementing?". The honest answer is that you never left. Review is not a phase you exit, so there is nothing to return to: open the artifacts, edit them, keep going. For a structured pass,
/opsx:verifyreads your artifacts and your code and reports where they disagree.@pexa-dnugent, on the "it forgets to update spec.md and tasks.md" problem:
/opsx:updateis the explicit way to ask for that revision instead of hoping the model remembers across a long cycle. Added in #1278, default profile as of v1.6.0. It may cover most of what your canned prompt has been doing.