What happened

The opsx-propose prompt/skill does not reliably activate when a user describes work that should flow through the OpenSpec proposal workflow. In practice I have to explicitly say something like "We must use the OpenSpec planning workflow" for the agent to engage opsx-propose. A natural request to build/change a feature should be enough to route into the propose workflow (or at least prompt me to), without the magic phrase.

What you expected instead

A feature/change request in an OpenSpec-enabled project should auto-select the opsx-propose workflow (or explicitly ask whether to use it), based on the skill's trigger description — without requiring the user to name the workflow.

Minimal steps to reproduce

1. In a repo already initialized with OpenSpec (openspec list --json returns a non-null root).
2. Ask the agent to implement a new feature in natural language, e.g. "/opsx-propose: Let's add a ValidateCustomer repository/service backed by a stored procedure."
3. Observe that the agent begins implementing instead of entering the opsx-propose workflow.
4. Re-issue the request adding "We must use the OpenSpec planning workflow."
5. Observe the agent now correctly runs opsx-propose.

OpenSpec version

1.31.1

Coding agent and model

Claude Opus 4.8

OS and Node version

Windows / PowerShell Node.js version v26.10.0