update-requirementslisted

# Update Requirements ## Skill Info Part of the **spec-manager** agent. This skill updates requirements and cascades changes through specs and plans. ## Input The user provides a change description as arguments: $ARGUMENTS The change description is a natural language instruction describing what to add, remove, or modify in the requirements. **Examples**: - `/update-requirements Third requirements should be removed` - `/update-requirements Add new requirements. API docs should be updated.` - `/update-requirements Change FR-2 acceptance criteria to include error handling` - `/update-requirements Performance requirement should be <200ms instead of <500ms` If no arguments are provided, ask the user what changes they want to make. ## Process ### Step 1: Identify Target Spec Set 1. List all `*/requirements.md` files in `specs/` directory 2. If only one spec set exists, use it automatically 3. If multiple exist, ask the user which one to update 4. Read the available files for the selected slug: - `specs/{slug}/requirements.md` (always exists) - `specs/{slug}/specs.md` (only for `Pipeline: full`; absent for lite) - `specs/{slug}/plans.md` (always exists) ### Step 1.5: Detect Pipeline Mode Read the `Pipeline:` header field from `requirements.md`: - `Pipeline: full` (or missing — treat missing as `full`): cascade through `specs.md` and `plans.md` as usual (Steps 4 + 5). - `Pipeline: lite`: **skip Step 4 entirely** (no `specs.md` exists). Cascade only to `plans.md`