plan-with-requirementslisted

# Plan with Requirements (Lite Pipeline) ## Skill Info Part of the **spec-manager** agent. This skill generates an implementation plan directly from `requirements.md`, skipping the `specs.md` step. It is the lite-pipeline counterpart to `/plan-with-specs`. Use it when: - `requirements.md` header has `Pipeline: lite`, **or** - The task is small enough that an intermediate technical spec adds no value (low difficulty). ## 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 that have `Pipeline: lite` in the header. 2. Ask the user which one to generate a plan for. If a task title (not slug) is provided, convert it to a slug to find the matching files. ## Process ### Step 1: Read the Requirements Document 1. Read `specs/{slug}/requirements.md`. If missing, stop and suggest `/init-specs`. 2. Read `specs/{slug}/plans.md`. It should exist as a placeholder from `/init-specs`. ### Step 2: Validate Pipeline Mode Inspect the `Pipeline:` header in `requirements.md`: - `Pipeline: lite` → proceed. - `Pipeline: full` → stop and tell the user: ``` This task uses the full pipeline. Use /specify-with-requirements then /plan-with-specs instead. If you want to switch to the lite pipeline, edit requirements.md header to set Pipeline: lite and remove specs.md (or run /init-specs with --pipeline lite for a new slug). ``` - Missing `Pipeline` header → treat as `fu