Requirement modification during purpose formulation

[LNqueen]

If there is a problem with the understanding of the AI during the purpose development, resulting in subsequent goals and design documents that are not what I expected, what command should I use to correct it?

[TabishB]

You don't need any slash commands. Just chat with your agent and ask it to modify the change proposal.

For example you can say:

Update the <change_name> change to add in this new goal.

The slash commands are a convenience feature they help you save time by not having to type repeated prompts.

Openspec works without any slash commands too, because it adds custom instructions to your AGENTS.md file.

Everything in openspec can work through pure chat with the agent.

[LNqueen]

Thank you very much for your reply. and I have another question, after using purpose instructions, which document should I check to determine whether AI are clear about my intentions? tasks.md or another document?

[TabishB]

@LNqueen The fastest way to answer your question is just go create a proposal! Check what files get created and what each file contains!

There's a section on the readme of the files is each change contains and why it exists: https://github.com/Fission-AI/OpenSpec?tab=readme-ov-file#example-how-ai-creates-openspec-files

But like I said go try out the tool and you'll learn much faster by doing :)

[LNqueen]

ok, got it. thanks a lot~~

[clay-good]

Answered above by Tabish, and now backed by both a command and a doc page, so closing.

No special command is required: tell the agent what it got wrong and it revises the artifact. If you also want the rest of the change kept coherent with that correction, /opsx:update does the reconciliation pass across proposal, specs, design and tasks. It ships in the default profile. Added in #1278, released in v1.6.0.

Written up in Editing & Iterating on a Change, which also answers your follow-up about which file to read: the proposal holds the intent, the specs hold what "done" means.