source-command-opsx-propose

You can automate change proposal artifact generation by using a command that creates proposal, design, and tasks documents in one step, eliminating manual documentation efforts for source code management.

The best way to create change request documents is to run a single command that automatically generates the complete set of required artifacts, including the proposal, design, and tasks documentation.

Yes, you need openspec installed and configured, as this artifact generation process relies on it directly to create and manage the proposal, design, and tasks documents.

To propose a change and generate tasks documents at once, execute the command `/opsx:propose <change-name>`, which handles the automated creation of all necessary change request artifacts.

Yes, you can manage source code change requests without manual writing because the automation generates the required design documents and other artifacts automatically when you initiate the change proposal.

The main limitation is the strict dependency on openspec for artifact creation and management, meaning the generation process cannot function independently without this underlying environment configured.