reset

To reset workflow runtime state safely, reinitialize the state.yaml file while preserving core configuration, prompts, architecture, and logs. This clears progress and lifecycle data without touching essential project instructions.

A full reset removes state, reports, and lifecycle logs while keeping configuration and architecture. A hard reset displays a deletion preview and deletes the entire pipeline workspace, requiring explicit confirmation for this destructive operation.

Clear corrupted workflow state and reports by running a full reset with the --full flag. This removes lifecycle data and report artifacts while retaining your core project instructions, prompts, and architectural files.

Yes, a hard reset deletes the entire pipeline workspace while preserving core project instructions. It enforces safety by displaying a deletion preview and requiring explicit confirmation before executing the destructive deletion.

Use a hard reset when you need to completely delete the pipeline workspace and all associated artifacts. Use a partial reset when you only need to reinitialize runtime state or clear reports while keeping configuration and architecture intact.