Mission · local progress
8 min read
Updated
Delete a project safely
Follow a safe project deletion mission: check scope and permission, rehearse cancellation, act in your test app and verify the outcome.
Direct answer
A dated result distinguishes cancellation with the project intact, confirmed deletion, failure and an unknown outcome. A disappearing card alone proves nothing.
Your journey, step by step
A concept explains, a comparison helps you choose, a recipe composes a screen. This mission connects screens and decisions to the result you must verify.
Use a fictional project or an explicitly authorized test environment. Know the owner, affected data and recovery policy before any real action.
No account required. Only completed step IDs stay in this browser, shared across EN and FR. No external action is executed. Checks are your declarations, not evidence collected by SkillCodex.
Loading progress…
0 / 5 steps declared verified
Resume the next step: Identify the project and consequences1 / 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.
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.
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.
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.
Result still to verify
A dated result distinguishes cancellation with the project intact, confirmed deletion, failure and an unknown outcome. A disappearing card alone proves nothing.
Keep evidence in your own environment. SkillCodex certifies neither a real action, human research, nor a mobile device.
01
What you verify
Use a fictional project or an explicitly authorized test environment. Know the owner, affected data and recovery policy before any real action.
Keep this
Final checklist
- 01The target, dependencies and recovery boundary are explicit.
- 02The scope and consequence are accepted explicitly.
- 03Cancellation, keyboard focus and duplicate blocking were observed in the specimen.
- 04The chosen test has an identifiable result, or is recorded as blocked. Continue only with an observed result.
- 05The recorded outcome matches both the operation and a fresh observation.
Primary sources
Technical claims in this guide connect to first-party specifications and documentation.