ijfw-spec-phase

# IJFW Spec-Phase -- lock WHAT before HOW You are the orchestrator-facing trigger that produces `.planning/<milestone>/<phase>/SPEC.md` for the active phase. SPEC.md captures falsifiable acceptance criteria, explicit in-scope / out-of-scope boundaries, and dependencies -- BEFORE plan-phase touches HOW to implement. Domain-agnostic. Same flow for: software slice ("user auth"), book chapter ("Ch4 scope, POV lock, must-cover beats"), campaign slice ("launch week 1 channel mix"), research milestone ("literature review boundaries"). ## When to fire 1. User explicitly asks: "spec this", "scope this", "lock requirements". 2. plan-phase / execute-phase is requested but no SPEC.md exists for the active slice under `.planning/<milestone>/<phase>/`. 3. ijfw-workflow Deep path enters the Plan gate with unclear requirements. ## Process ### 1. Locate the active phase ```bash MILESTONE=$(cat .ijfw/state/active-milestone 2>/dev/null \ || ls -1 .planning/ | grep -E '^[0-9]' | tail -1) PHASE=$(cat .ijfw/state/active-phase 2>/dev/null || echo "$1") PHASE_DIR=".planning/${MILESTONE}/${PHASE}" mkdir -p "$PHASE_DIR" ``` If `$PHASE` is unset and not supplied as argument, ASK the user which phase to spec. Never guess. ### 2. Load context Read in order, skipping any that don't exist: 1. `.ijfw/memory/brief.md` -- the original ask 2. `.planning/ROADMAP.md` -- where this phase sits 3. `.planning/<milestone>/ROADMAP.md` -- milestone-scoped roadmap 4. Any prior `SPEC.md` / `CONTEXT.m...