spec-pack-abandon (Discard/Revoke Spec Pack: List + Double Confirmation + Branch Deletion)

Overview

spec-context

{FEATURE_DIR}

When to Use / Not to Use

• Usage Scenarios
  • Major issues occur in requirements/constraints, and it is decided to discard the current spec pack (no longer continue clarification/design/implementation).
  • You need to delete:

    .aisdlc/specs/{CURRENT_BRANCH}/

    and the

    {CURRENT_BRANCH}

    branch (local + remote).
• Do Not Use When
  • You just want to "roll back a commit" or "redo the requirement document": prioritize normal git rollback/new commits instead of deleting branches.
  • You are not currently on a spec branch (branch name does not conform to

    {num}-{short-name}

    ): switch to the target spec branch first; otherwise stop.

Hard Rules (Must Be Followed)

• REQUIRED SUB-SKILL: First meet the

  spec-context

  access control and echo

  FEATURE_DIR=...

  in the conversation (allow

  (reuse)

  ).
• Prohibit guessing paths/branches: Only use

  CURRENT_BRANCH

  and

  FEATURE_DIR

  from

  Get-SpecContext

  .
• Must output deletion list: Before any deletion command, first output the "list of content to be deleted" (directory/branch/remote branch existence/overview of uncommitted changes).
• Must double confirm:
  • First confirmation: The user confirms that "the deletion list is correct".
  • Second confirmation: The user confirms that "the specific deletion command to be executed is correct".
  • Both confirmations require the user to reply with exact phrases (see below).
• Prohibit discarding the entire workspace by default: Do not suggest/execute "full cleanup" commands like

  git clean -fd

  to save trouble.
• Stop when any verification fails: Do not continue to give "direct deletion" commands.

Deletion List Generation (PowerShell)

This section is only used for generating list and risk prompts, no deletion is performed.

. (Join-Path (git rev-parse --show-toplevel) "skills\spec-context\scripts\spec-common.ps1")
$context = Get-SpecContext
$FEATURE_DIR = $context.FEATURE_DIR
Write-Host ("FEATURE_DIR={0}" -f $FEATURE_DIR)
Write-Host ("CURRENT_BRANCH={0}" -f $context.CURRENT_BRANCH)

$repoRoot = $context.REPO_ROOT
$branch = $context.CURRENT_BRANCH
$featureDir = $context.FEATURE_DIR
$demoDir = Join-Path $repoRoot ("demo\prototypes\{0}" -f $branch)

$hasRemote = $false
git ls-remote --exit-code --heads origin $branch *> $null
if ($LASTEXITCODE -eq 0) { $hasRemote = $true }

$dirty = git status --porcelain
$aheadBehind = git rev-list --left-right --count ("origin/{0}...{0}" -f $branch) 2>$null

Write-Host "=== Deletion List (Pending Confirmation) ==="
Write-Host ("REPO_ROOT: {0}" -f $repoRoot)
Write-Host ("CURRENT_BRANCH (to be deleted): {0}" -f $branch)
Write-Host ("FEATURE_DIR (to be deleted/cleaned): {0}" -f $featureDir)
Write-Host ("demo/prototypes (to be deleted/cleaned if exists): {0}" -f $demoDir)
Write-Host ("Whether remote branch origin/{0} exists: {1}" -f $branch, $hasRemote)
Write-Host ""
Write-Host "=== Workspace Risk Prompt ==="
if ($dirty) {
  Write-Host "Uncommitted changes detected (will be lost when the branch is deleted). git status --porcelain:"
  $dirty | ForEach-Object { Write-Host ("  {0}" -f $_) }
} else {
  Write-Host "No uncommitted changes detected."
}
if ($aheadBehind) {
  Write-Host ("Ahead/behind count with origin/{0} (may be empty/error if the branch is not pushed): {1}" -f $branch, $aheadBehind)
}

First Confirmation (Mandatory)

• First confirmation phrase:

  确认删除清单

Deletion Command Preparation (Only Displayed After First Confirmation)

This section still does not perform deletion; only lists the "commands to be executed" in full as the object of the second confirmation.

. (Join-Path (git rev-parse --show-toplevel) "skills\spec-context\scripts\spec-common.ps1")
$context = Get-SpecContext
$branch = $context.CURRENT_BRANCH
$featureDir = $context.FEATURE_DIR
$repoRoot = $context.REPO_ROOT
$demoDir = Join-Path $repoRoot ("demo\prototypes\{0}" -f $branch)

$hasRemote = $false
git ls-remote --exit-code --heads origin $branch *> $null
if ($LASTEXITCODE -eq 0) { $hasRemote = $true }

@"
【Deletion commands to be executed (pending final confirmation)】

1) Switch to main (avoid deleting while on the branch to be deleted)
git switch main
git pull

2) Clean up local residual directories (if exist)
if (Test-Path -LiteralPath `"$featureDir`") { Remove-Item -LiteralPath `"$featureDir`" -Recurse -Force }
if (Test-Path -LiteralPath `"$demoDir`") { Remove-Item -LiteralPath `"$demoDir`" -Recurse -Force }

3) Delete local branch
git branch -D $branch

4) Delete remote branch (if exists)
"@ | Write-Host

if ($hasRemote) {
  Write-Host ("git push origin --delete {0}" -f $branch)
} else {
  Write-Host ("(Skip remote deletion: origin/{0} not detected)" -f $branch)
}

Second Confirmation (Mandatory)

• Second confirmation phrase:

  最终确认执行删除

Perform Deletion (Only After Double Confirmation)

git branch --list $branch
git branch -r | Select-String ("origin/{0}" -f $branch)
Test-Path -LiteralPath $featureDir

• git branch --list $branch

  has no output
• No match for remote branch query (if you performed remote deletion)

• Test-Path $featureDir

  returns

  False

Common Errors (Stop According to Hard Rules Immediately When Occur)

• Skip

  spec-context

  : Splice paths by "looking at directories/looking at open files/guessing branch names".
• Delete without outputting list: Directly give

  git branch -D

  /

  git push --delete

  /

  Remove-Item

  commands.
• Only confirm once: The user saying "delete it" does not equal completing the double confirmation access control.
• Clear the repository with

  git clean -fd

  : This is a full disk deletion, which is very easy to accidentally injure non-spec pack files.
• Delete main / delete wrong branch: You must stop if any branch name is inconsistent with

  Get-SpecContext.CURRENT_BRANCH

  .