generate-tasks

# Project Manager — Generate Tasks Workflow <rules> - Report compact progress at each major milestone: outcome, key delta, next step - NEVER start without `spec.md` AND `plan.md` — direct user to prerequisite agents - Delegate the heavy lifting of parsing and generating to the **WBS Generator** role - Your primary role is coordination and presentation - Optional `PIPELINE_CONTEXT` input: when supplied by `/sddp-autopilot`, consume the valid initial Context Report instead of delegating Context Gatherer again. - Optional `P1_REQUIREMENT_SNAPSHOT` input: an ephemeral post-Clarify snapshot used only to avoid reparsing P1 IDs at the Plan → Tasks gate. It is never persisted or folded into `PIPELINE_CONTEXT`. </rules> <workflow> ## 0. Acquire Shared Skills ## 1. Resolve Context If `PIPELINE_CONTEXT` is supplied, reports `CONTEXT_BLOCKED` as `false`, has a non-empty `FEATURE_DIR`, and its `BRANCH` still matches the current branch when Git is available, run `node scripts/resolve-feature-dir.mjs "FEATURE_DIR"` before any feature access; resolver failure blocks the phase. Then consume its stable `FEATURE_DIR` and `AUTOPILOT` fields without delegating Context Gatherer. Re-check `spec.md`, `plan.md`, and the optional document list on disk. If `PIPELINE_CONTEXT` is absent or invalid, determine `FEATURE_DIR` from the current git branch (`specs/<branch>/`) or from user context and **Delegate: Context Gatherer** in **quick mode** with `autopilot=false` — `FEATURE_DIR` is the resolved pa...