Archive specifications for completed work
<issue_number> [--force] [--skip-warnings]claude-haiku-4-5Archive specifications to cloud storage when work is complete. Specs are uploaded, indexed, linked from GitHub, and removed from local storage to prevent stale context. ## Usage ## Arguments - `<issue_number>`: GitHub issue number (required) ## Options - `--force`: Skip all pre-archive checks - `--skip-warnings`: Don't prompt for warnings, archive anyway ## Examples ### Basic Usage Performs all checks, prompts if warnings. ### Skip Warnings Archives even if docs not updated or validation partial. ### Force Archive Skips all checks, archives immediately. ## Pre-Archive C...
Properly archive completed orchestrations while preserving valuable data, metrics, and lessons learned for future reference.
Manually archive completed increments and sync living docs - NEVER auto-archives, explicit user action only
Archive a completed feature.
Archive all FABER workflow artifacts for completed work
Archive all logs for a completed issue to cloud storage