workflow-editor

To safely edit ACP workflows, apply validated, minimal changes to agents, commands, and ambient.json files. The process verifies target workflow existence and file naming conventions before applying changes, ensuring JSON validity and preserving structural integrity.

The best way to modify ambient.json and documentation is through guided, phase-based editing that enforces JSON and schema validation. This approach applies targeted edits while automatically generating change summaries to verify modifications.

Yes, you can rollback invalid workflow changes using built-in rollback guidance. If JSON or schema validation fails during the editing process, the safety-focused tooling provides error handling and instructions to revert the workflow directory to its previous state.

Yes, ACP workflow editing requires an existing workflows/ directory structure. The guided editing process first confirms the target workflow existence and verifies file naming conventions before allowing any modifications to agents, commands, or ambient.json files.

Workflow edits fail naming convention checks when modified agents or commands do not match the existing structural standards. The editing process verifies target workflow existence and enforces strict file naming validation before applying any changes.

You should use automated validation for workflow editing whenever modifying agents, commands, ambient.json, or README files. It enforces JSON validity, ensures minimal verifiable edits, and provides change summaries to maintain documentation and structural consistency.