ring:cycle-management

To track development cycle status, use the /ring:dev-status command to inspect the current cycle ID, start time, task counts, current gate, and elapsed time. It discovers active state across multiple known JSON file locations.

To safely cancel a development cycle, use the /ring:dev-cancel command. By default it requires confirmation and preserves current cycle state in JSON format for future resumption, generating a partial feedback report.

Yes, you can force cancel a development cycle by appending the --force flag to the /ring:dev-cancel command. This bypasses the confirmation prompt while still preserving state for later resumption.

If no active development cycle exists, the state discovery mechanism gracefully signals that no cycle is currently running after checking known JSON file locations like docs/ring:dev-cycle/current-cycle.json.

Yes, cycle management supports multiple workflows by discovering active state across different file locations, integrating with /ring:dev-status, /ring:dev-cancel, and /ring:dev-cycle commands for iterative development.

Development cycle status reporting provides read-only inspection of cycle ID, start time, elapsed time, current task and gate, plus task counts for completed, in progress, and pending items.