Name: planSafeDelete
Author: archubbuck

Prompt file imported from archubbuck/enterprise-support (.github/prompts/safe-delete/planSafeDelete.prompt.md). Copyright stays with the author.

Create a safety-first plan to delete only the files and folders provided in the prompt input.

Input

Treat the user argument as the deletion target list. The argument may include:

comma-separated paths
newline-separated paths
mixed file and folder paths

If no targets are provided, return: No deletion targets were provided. Provide one or more file/folder paths.

Objective

Return an execution-ready plan that safely removes the requested targets with minimal risk to the repository.

Safety Rules

Plan only. Do not delete anything.
Do not invent additional deletion targets.
Preserve user-provided order unless safety dependencies require reordering.
Identify blockers before deletion (imports, references, config links, docs links, scripts, tests, build/release impact).
Include rollback guidance before destructive actions.
If any target path appears ambiguous or unresolved, call it out and require confirmation.

Required Output Format

Produce the response with these sections in order:

1) Target Inventory

Normalized list of requested paths
For each target: file/folder classification and confidence (High/Medium/Low)

2) Preflight Checks (Read-Only)

Ordered list of non-destructive checks to run first
Include safe verification commands (search/list/status only)
Explain what each check validates

3) Deletion Plan

Step-by-step deletion sequence
For each step: target(s), reason for order, and risk note
Explicit hold points where user confirmation is required

4) Post-Delete Verification

Read-only validation steps to confirm no broken references
Build/test checks to run after deletion

5) Rollback Plan

Immediate recovery options if deletion causes issues
Git-based restore guidance and validation steps

6) Go/No-Go Summary

Final readiness statement
Open risks, assumptions, and required confirmations

Command Policy

You may include command examples only for:

listing files and folders
searching references
checking git working tree status and history
running validation checks

Do not include direct destructive execution as completed actions. If deletion commands are shown, present them only as planned steps under explicit user-confirmation gates.

Create a safety-first plan to delete only the files and folders provided in the prompt input. ## Input Treat the user argument as the deletion target list. The argument may include: - comma-separated paths - newline-separated paths - mixed file and folder paths If no targets are provided, return: `No deletion targets were provided. Provide one or more file/folder paths.` ## Objective Return an execution-ready plan that safely removes the requested targets with minimal risk to the repository. ## Safety Rules 1. Plan only. Do not delete anything. 2. Do not invent additional deletion targets. 3. Preserve user-provided order unless safety dependencies require reordering. 4. Identify blockers before deletion (imports, references, config links, docs links, scripts, tests, build/release impact). 5. Include rollback guidance before destructive actions. 6. If any target path appears ambiguous or unresolved, call it out and require confirmation. ## Required Output Format Produce the response with these sections in order: ### 1) Target Inventory - Normalized list of requested paths - For each target: file/folder classification and confidence (High/Medium/Low) ### 2) Preflight Checks (Read-Only) - Ordered list of non-destructive checks to run first - Include safe verification commands (search/list/status only) - Explain what each check validates ### 3) Deletion Plan - Step-by-step deletion sequence - For each step: target(s), reason for order, and risk note - Explicit hold points where user confirmation is required ### 4) Post-Delete Verification - Read-only validation steps to confirm no broken references - Build/test checks to run after deletion ### 5) Rollback Plan - Immediate recovery options if deletion causes issues - Git-based restore guidance and validation steps ### 6) Go/No-Go Summary - Final readiness statement - Open risks, assumptions, and required confirmations ## Command Policy You may include command examples only for: - listing files and folders - searching references - checking git working tree status and history - running validation checks Do not include direct destructive execution as completed actions. If deletion commands are shown, present them only as **planned** steps under explicit user-confirmation gates.

{ "prompt": "Create a safety-first plan to delete only the files and folders provided in the prompt input.\n\n## Input\nTreat the user argument as the deletion target list. The argument may include:\n- comma-separated paths\n- newline-separated paths\n- mixed file and folder paths\n\nIf no targets are provided, return:\n`No deletion targets were provided. Provide one or more file/folder paths.`\n\n## Objective\nReturn an execution-ready plan that safely removes the requested targets with minimal risk to the repository.\n\n## Safety Rules\n1. Plan only. Do not delete anything.\n2. Do not invent additional deletion targets.\n3. Preserve user-provided order unless safety dependencies require reordering.\n4. Identify blockers before deletion (imports, references, config links, docs links, scripts, tests, build/release impact).\n5. Include rollback guidance before destructive actions.\n6. If any target path appears ambiguous or unresolved, call it out and require confirmation.\n\n## Required Output Format\nProduce the response with these sections in order:\n\n### 1) Target Inventory\n- Normalized list of requested paths\n- For each target: file/folder classification and confidence (High/Medium/Low)\n\n### 2) Preflight Checks (Read-Only)\n- Ordered list of non-destructive checks to run first\n- Include safe verification commands (search/list/status only)\n- Explain what each check validates\n\n### 3) Deletion Plan\n- Step-by-step deletion sequence\n- For each step: target(s), reason for order, and risk note\n- Explicit hold points where user confirmation is required\n\n### 4) Post-Delete Verification\n- Read-only validation steps to confirm no broken references\n- Build/test checks to run after deletion\n\n### 5) Rollback Plan\n- Immediate recovery options if deletion causes issues\n- Git-based restore guidance and validation steps\n\n### 6) Go/No-Go Summary\n- Final readiness statement\n- Open risks, assumptions, and required confirmations\n\n## Command Policy\nYou may include command examples only for:\n- listing files and folders\n- searching references\n- checking git working tree status and history\n- running validation checks\n\nDo not include direct destructive execution as completed actions. If deletion commands are shown, present them only as **planned** steps under explicit user-confirmation gates.", "variables": [], "notes": "Switch to Plan mode and generate a safe, non-destructive deletion plan for user-provided files and folders. Tools: read, execute. Arguments: Provide the file(s) and folder(s) to remove. Accepts comma-separated, newline-separated, or mixed path lists..", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/archubbuck/enterprise-support", "path": ".github/prompts/safe-delete/planSafeDelete.prompt.md", "ref": "8fd72c7515b8b6430ad395778e00ef9abf9a8d1b", "url": "https://github.com/archubbuck/enterprise-support/blob/8fd72c7515b8b6430ad395778e00ef9abf9a8d1b/.github/prompts/safe-delete/planSafeDelete.prompt.md", "key": "archubbuck/enterprise-support/.github/prompts/safe-delete/planSafeDelete.prompt.md" } }, "model_hints": [ "Auto" ] }

planSafeDelete

About