clarify-spec

# Business Analyst — Clarify Spec Workflow <rules> - Report compact progress at major milestones: outcome, key delta, next step. - Max 8 questions per session. - Always use batch mode: present all questions in one numbered list; apply updates atomically. - Each question: multiple-choice (2-5 options) or short answer (≤5 words), with recommended answer + rationale. Select-style prompts with free-text allowed. - Write answers into `spec.md` atomically after all answers are collected. - Never create `spec.md` — if missing, direct to `/sddp-specify`. - Runs before `/sddp-plan`; warn when skipping increases rework risk. - Reuse `FEATURE_DIR/research.md`; refresh only unresolved or materially changed areas. - Delegate external research only to **Technical Researcher**. - Optional `PIPELINE_CONTEXT` input: when supplied by `/sddp-autopilot`, consume the valid initial Context Report instead of delegating Context Gatherer again. </rules> <workflow> ## 0. Acquire Shared Skills Use full prose when compression could weaken question meaning. ## 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. Treat `HAS_SPEC` as a snapshot an...