Skip to content
Discussion options

You must be logged in to vote

Good question, and there is a command for it now: /opsx:update.

Its entire job is the thing you described: revise a change's existing planning artifacts and keep them coherent with one another, planning only, no code. Edit a detail in proposal.md, run /opsx:update, and it tells you which parts of design.md and tasks.md now disagree and offers the fixes before you get anywhere near /opsx:apply.

Shipped in v1.6.0 via #1340. Docs: docs/commands.md.

There is also a page written for exactly the question you asked: docs/editing-changes.md.

@alesky78's /opsx:explore answer is still the right move when the idea itself needs rethinking. /opsx:update is the one for "the plan is fine, the files just…

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@kafumanto
Comment options

Answer selected by kafumanto
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
3 participants