ghs:force-archive

Force Archive All Sprints

Archive all sprints, including those that are in-progress, planning, or on-hold. This is a destructive operation — always confirm with the user first.

Prerequisites

Resolve the project directory:

python3 ${CLAUDE_PLUGIN_ROOT}/shared/scripts/resolve_project_dir.py

Workflow

Step 1: List ALL Sprints

Show the user what will be archived:

python3 ${CLAUDE_PLUGIN_ROOT}/shared/scripts/archive_sprint.py --list --force --project-dir "<PROJECT_DIR>"

Step 2: Confirm with User

WARNING: Display all sprints that will be archived and their statuses. Ask the user to explicitly confirm. Example:

The following sprints will be archived:
  - Sprint 1: Authentication (s1) [in_progress] - 3/6 features completed
  - Sprint 2: Dashboard (s2) [planning] - 0/4 features completed

This action will move all sprint data to .ghs/archived/ and reset .ghs/progress.md.
Are you sure you want to proceed?

Do NOT proceed without explicit user confirmation.

Step 3: Archive

After confirmation:

python3 ${CLAUDE_PLUGIN_ROOT}/shared/scripts/archive_sprint.py --force --project-dir "<PROJECT_DIR>"

This will:

• Archive all sprints to .ghs/archived/
• Remove all sprints from .ghs/features.json (project info is preserved)
• Reset .ghs/progress.md to the default template

No git commit needed — .ghs/ tracking files are local metadata (gitignored by ghs:init).

After Force Archive

The project still has .ghs/features.json and .ghs/progress.md — just with no active sprints. The user can run /ghs:sprint to plan a new sprint from scratch.

Archived data is preserved in .ghs/archived/ for reference.