Delete a project safely

1 / 5 · Information

Identify the project and consequences

Screen: project settings. In the fictional Atlas project, list files, members and dependent links. State what is permanently lost and what can be recovered. Keep a safe exit visible.

Expected result: The target, dependencies and recovery boundary are explicit.

Common mistake: Do not infer permission from the presence of a Delete button.

• Explain persistent consequences

2 / 5 · Decision

Decide whether to proceed

Before the confirmation screen, check authorization for this exact project and an accepted recovery or permanent-loss policy. If either is missing, pause and resolve it outside this mission.

Expected result: The scope and consequence are accepted explicitly.

Common mistake: A local choice never grants real deletion permission.

• Compare confirmation and editing

3 / 5 · Verification

Rehearse cancellation before confirmation

Screen: confirmation. Open the existing generic workspace recipe. Cancel first: the object remains and focus returns. Then rehearse pending and completion. A workspace specimen teaches the pattern; adapt the project scope yourself.

Expected result: Cancellation, keyboard focus and duplicate blocking were observed in the specimen.

Common mistake: Restarting this example is not undoing a real deletion.

• Try the confirmation recipe

4 / 5 · External action

Perform only the authorized test

In your own test application, select the exact project and cancel or confirm deliberately. Keep the operation receipt outside SkillCodex. On timeout, reconcile the existing operation before retrying; do not send a second deletion blindly.

Perform this yourself in your tool, only if authorized. This button updates local progress; it runs no operation.

Expected result: The chosen test has an identifiable result, or is recorded as blocked. Continue only with an observed result.

Common mistake: SkillCodex executes no deletion and cannot inspect your server.

5 / 5 · Verification

Verify the durable outcome

Screen: project list after refresh. For cancellation, verify the project and data still exist. For deletion, cross-check the server receipt and authorized read-back, dependent access and the persistent result. If evidence disagrees, leave this step incomplete.

Expected result: The recorded outcome matches both the operation and a fresh observation.

Common mistake: A toast or an empty screen is insufficient evidence. Unknown remains unknown.