Feature Request: Allow assistant to trigger /spec:implement-next

What feature would you like to see?

Please add first-party support for Codex CLI assistants to invoke the /spec:implement-next slash command directly. Today the assistant can list tasks from the active spec, but it cannot advance the spec workflow without the human operator manually running /spec:implement-next. Enabling programmatic invocation (either by exposing the command through the API or allowing the CLI assistant to trigger it) would let agents follow the documented Requirements → Design → Tasks → Implementation flow end-to-end without unnecessary context switches.

Are you interested in implementing this feature?

Yes—happy to help test and validate the UX change once the CLI exposes a supported entry point.

Additional information

• Verified there is no existing issue covering this request (/spec:implement-next isn't mentioned in open or closed issues as of 2025-02-14).
• This would help teams using spec-driven development keep the assistant aligned with the enforced workflow while reducing manual overhead.