speckit-archivelisted

Act as the **Chief Software Architect** and **Documentation Maintainer**. A feature has been merged into the `main` branch. Your goal is to **archive** the feature specification into the main project memory — ensuring completeness, resolving conflicts, closing gaps, and respecting the project constitution. ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ### Input Parsing Parse `$ARGUMENTS` as follows: - **First token**: feature spec directory path (e.g., `specs/007-invoice-settings`) - **Remaining tokens**: scope modifiers (optional, space-separated) **Supported scope modifiers** (if none provided, update all artifacts): - `--spec-only` — update only `.specify/memory/spec.md` - `--plan-only` — update only `.specify/memory/plan.md` - `--changelog-only` — update only `.specify/memory/changelog.md` - `--agent-only` — update only the agent knowledge file (GEMINI.md / AGENTS.md / CLAUDE.md) If `$ARGUMENTS` is empty, output `ERROR: No feature spec directory provided. Usage: /speckit.archive.run specs/###-feature-name [--scope-modifier]` and stop. --- ## Step 0: Setup & Validation (Gate) ### 0.1 Resolve Paths Run `.specify/scripts/bash/check-prerequisites.sh --json --paths-only` to identify the active feature directory and its artifacts. This script is mandatory for path discovery. If the script is missing, stop and inform the user. Derive absolute paths for: - `REPO_ROOT` (from `.specify/scripts/bash/check-prer