Clean Room Start Over
Start a clean-room run over without overwriting or deleting existing artifacts in place.
Use the canonical clean-room skill workflow and references in this plugin. Preserve the same clean-room boundary, role separation, artifact schemas, leakage rules, implementation-root rules, and hook expectations.
Archive First
Require explicit user confirmation before changing artifact locations. Stop if confirmation is absent, authorization is unclear, or the archive target overlaps a source root in a way that would make provenance unclear.
Archive or quarantine previous artifacts before creating new ones:
- Prefer the
task-manifest.json artifact_paths.quarantine path.
- Use a user-supplied quarantine path only when it is separated from source roots, contaminated artifact roots, clean roots, and implementation roots.
- Keep contaminated artifacts only under a contaminated-domain archive or quarantine directory.
- Keep clean artifacts only under a clean-domain archive or quarantine directory.
- Do not mix contaminated and clean archives.
- Do not delete artifacts.
- Do not overwrite an existing archive path; create a unique archive directory.
- In the project layout, archive scope is the task folder only. Never archive, move, or quarantine the project root,
clean-room-project.json, or the shared project-level implementation/ root; sibling tasks depend on them, and implementation content is destination state, not per-task artifact state.
- Preserve existing
preflight-goal.json, task-manifest.json, ledgers, handoff packages, behavior specs, skeleton manifests, implementation plans, implementation reports, QC reports, incident records, and open delta tickets.
If safe archive targets cannot be proven from task-manifest.json, root environment, or explicit user input, stop before moving anything.
Restart Gate
Start from the preflight gate, not from prior QC:
- Create a new
preflight-goal.json or explicitly reuse a reviewed goal contract before recreating active artifacts.
- Reconfirm requester authorization, source or visual evidence scope, allowed actions, prohibited actions, and evidence handling.
- Reconfirm source roots or visual roots, contaminated artifact roots, clean roots, implementation roots, and clean allowed-read roots are separated, and that root path names are not source-derived.
- Preserve source or visual roots and authorization only when they are still valid for the requested restart.
- Create a fresh neutral
task_id by default. Use task- plus 8 lowercase hex characters unless the user provides an explicitly approved neutral ID. Do not derive the new ID or output directory names from source folder names.
- In the project layout, the new task joins the same project by default. Starting a new project instead requires an explicit user choice and a fresh neutral project name (random word pair or
proj- plus 8 lowercase hex, never source-derived).
- Record
run_state.generation, run_state.started_at, optional run_state.previous_generation_ref, and run_state.restart_reason.
- Recreate
clean-run-context.json from the new effective preflight and initialization choices; do not carry forward an old clean context by default.
- Rebuild
source-index.json, or visual-index.json for visual fallback runs, unless the user explicitly says the source or visual scope is unchanged and a recorded old index hash can still be validated.
- Preserve the selected controller mode only if the user reconfirms it or it is recorded in the still-valid manifest.
Do not carry forward prior chat history or unapproved clean artifacts. Treat archived artifacts as audit history, not active task state.
Output
Return a concise restart summary:
- Archived artifact roots and archive targets.
- Authorization and root-separation status.
- New
task_id or generation identifier.
- Whether a new or reviewed
preflight-goal.json is active.
- Whether
source-index.json or visual-index.json must be rebuilt.
- The next scope-gate action.
Do not carry forward unapproved implementation code as active task state.
Source: hashgraph-online/awesome-codex-plugins → plugins/whit3rabbit/clean-room-skill/skills/start-over/SKILL.md
1---2name: start-over3description: Archives or quarantines current Clean Room artifacts and restarts from the scope gate with a fresh task id.4---567# Clean Room Start Over89Start a clean-room run over without overwriting or deleting existing artifacts in place.1011Use the canonical `clean-room` skill workflow and references in this plugin. Preserve the same clean-room boundary, role separation, artifact schemas, leakage rules, implementation-root rules, and hook expectations.1213## Archive First1415Require explicit user confirmation before changing artifact locations. Stop if confirmation is absent, authorization is unclear, or the archive target overlaps a source root in a way that would make provenance unclear.1617Archive or quarantine previous artifacts before creating new ones:1819- Prefer the `task-manifest.json` `artifact_paths.quarantine` path.20- Use a user-supplied quarantine path only when it is separated from source roots, contaminated artifact roots, clean roots, and implementation roots.21- Keep contaminated artifacts only under a contaminated-domain archive or quarantine directory.22- Keep clean artifacts only under a clean-domain archive or quarantine directory.23- Do not mix contaminated and clean archives.24- Do not delete artifacts.25- Do not overwrite an existing archive path; create a unique archive directory.26- In the project layout, archive scope is the task folder only. Never archive, move, or quarantine the project root, `clean-room-project.json`, or the shared project-level `implementation/` root; sibling tasks depend on them, and implementation content is destination state, not per-task artifact state.27- Preserve existing `preflight-goal.json`, `task-manifest.json`, ledgers, handoff packages, behavior specs, skeleton manifests, implementation plans, implementation reports, QC reports, incident records, and open delta tickets.2829If safe archive targets cannot be proven from `task-manifest.json`, root environment, or explicit user input, stop before moving anything.3031## Restart Gate3233Start from the preflight gate, not from prior QC:3435- Create a new `preflight-goal.json` or explicitly reuse a reviewed goal contract before recreating active artifacts.36- Reconfirm requester authorization, source or visual evidence scope, allowed actions, prohibited actions, and evidence handling.37- Reconfirm source roots or visual roots, contaminated artifact roots, clean roots, implementation roots, and clean allowed-read roots are separated, and that root path names are not source-derived.38- Preserve source or visual roots and authorization only when they are still valid for the requested restart.39- Create a fresh neutral `task_id` by default. Use `task-` plus 8 lowercase hex characters unless the user provides an explicitly approved neutral ID. Do not derive the new ID or output directory names from source folder names.40- In the project layout, the new task joins the same project by default. Starting a new project instead requires an explicit user choice and a fresh neutral project name (random word pair or `proj-` plus 8 lowercase hex, never source-derived).41- Record `run_state.generation`, `run_state.started_at`, optional `run_state.previous_generation_ref`, and `run_state.restart_reason`.42- Recreate `clean-run-context.json` from the new effective preflight and initialization choices; do not carry forward an old clean context by default.43- Rebuild `source-index.json`, or `visual-index.json` for visual fallback runs, unless the user explicitly says the source or visual scope is unchanged and a recorded old index hash can still be validated.44- Preserve the selected controller mode only if the user reconfirms it or it is recorded in the still-valid manifest.4546Do not carry forward prior chat history or unapproved clean artifacts. Treat archived artifacts as audit history, not active task state.4748## Output4950Return a concise restart summary:5152- Archived artifact roots and archive targets.53- Authorization and root-separation status.54- New `task_id` or generation identifier.55- Whether a new or reviewed `preflight-goal.json` is active.56- Whether `source-index.json` or `visual-index.json` must be rebuilt.57- The next scope-gate action.5859Do not carry forward unapproved implementation code as active task state.6061---6263**Source:** [`hashgraph-online/awesome-codex-plugins`](https://github.com/hashgraph-online/awesome-codex-plugins) → `plugins/whit3rabbit/clean-room-skill/skills/start-over/SKILL.md`