What's the suggested way to create openspec proposal, /workflow or directly chat?

[sunpeinju]

I'm using OpenSpec + Kilo Code + QWen3-Coder modal combination in my project. I'm very confusing how to trigger the agent to follow OpenSpec instruction flow strictly.

1. When I directly input "create spec", the agent will load the "/openspec/AGENTS.md" and follow the 3 "Stage" there. It may directly start to 'apply' after 'proposal' stage. The openspec-proposal.md flow file isn't loaded during the whole process.
2. When I use "/openspec-proposal.md" to launch the proposal flow, the agent usually won't look into the AGENTS.md to learn 'openspec' details. It may use ls to check changes folder and ignore the usage of openspec ls.

So what's the suggested way to tell Kilo Code strictly follow the openspec flow instructions?

[clay-good]

Closing as outdated — both halves of this question describe a structure that no longer exists.

openspec/AGENTS.md and the openspec-*.md prompt files were removed. OpenSpec now generates skills (openspec-propose, openspec-apply-change, openspec-archive-change, …) plus native slash commands per tool, and openspec update deletes the legacy files when you upgrade.

That also removes the failure mode you described: the flow instructions are no longer in a file the agent may or may not read — they're delivered by the skill the command invokes, so there's no "did it load AGENTS.md?" branch to worry about.

• How Commands Work — the terminal half vs. the chat half
• Supported Tools — what Kilo Code gets generated

Run openspec update in your project to pick this up. Reopen if the agent still ignores the flow after upgrading.