specify-with-requirementslisted

# Specify with Requirements ## Skill Info Part of the **spec-manager** agent. This skill analyzes requirements and generates detailed technical specifications. ## Input The user provides a task slug (or task title) as arguments: $ARGUMENTS If no arguments are provided: 1. List all `*/requirements.md` files in `specs/` directory 2. Ask the user which one to process If a task title (not slug) is provided, convert it to a slug to find the matching files. ## Process ### Step 1: Locate and Read Requirements 1. Find `specs/{slug}/requirements.md` 2. If the file doesn't exist, inform the user and suggest running `/init-specs` first 3. Read the full requirements document ### Step 1.5: Detect Pipeline Mode (Lite → Full Escalation) Inspect the `Pipeline:` header field in `requirements.md`: - `Pipeline: full` (or missing — treat missing as `full` for backward compatibility): proceed to Step 2 normally. - `Pipeline: lite`: this slug was initialized as a lite-pipeline task and does **not** yet have a `specs.md` file. Calling `/specify-with-requirements` on a lite task means the user wants to **escalate** to full pipeline. In this case: 1. Use AskUserQuestion to confirm: ``` 이 태스크는 lite 파이프라인(`Pipeline: lite`)으로 초기화되어 specs.md가 없습니다. full 파이프라인으로 escalate 하시겠습니까? ``` Options: `Escalate (recommended)` / `Cancel`. 2. If **Cancel**: print a one-line note ("Escalation cancelled — task remains lite") and stop. 3. If **Escalate**: a. Update `re