spectra-proposelisted

Create a complete Spectra change proposal — from requirement to validated artifacts — in a single workflow. **Input**: The argument after `/spectra-propose` is the requirement description. Examples: - `/spectra-propose add dark mode` - `/spectra-propose fix the login page crash` - `/spectra-propose improve search performance` If no argument is provided, the workflow will extract requirements from conversation context or ask. **Prerequisites**: This skill requires the `spectra` CLI. If any `spectra` command fails with "command not found" or similar, report the error and STOP. **Steps** 1. **Determine the requirement source** a. **Argument provided** (e.g., "add dark mode") → use it as the requirement description, skip to deriving the change name below. b. **Plan file available**: - Check if the conversation context mentions a plan file path (plan mode system messages include the path like `~/.claude/plans/<name>.md`) - If found, check if the file exists at `~/.claude/plans/` - If a plan file is found, use the **AskUserQuestion tool** to ask: - Option 1: Use the plan file - Option 2: Use conversation context - If conversation context has no relevant discussion, mention this when presenting the choice - If the user picks the plan file → read it and extract: - `plan_title` (H1 heading) → use as requirement description - `plan_context` (Context section) → use as proposal Why/Motivation content - `plan_stages` (numbered implemen