feat(research-phase): load REQUIREMENTS.md for focused research

Research now loads concrete requirements (e.g., "AUTH-02: User receives
email verification") to inform research domains, not just high-level
roadmap descriptions.

Co-Authored-By: Claude <noreply@anthropic.com>

commands/gsd/research-phase.md

@@ -42,6 +42,14 @@ Phase number: $ARGUMENTS (required)
 **Load roadmap:**
 @.planning/ROADMAP.md
 
+**Load requirements:**
+@.planning/REQUIREMENTS.md
+
+Extract phase requirements before research:
+1. Find the phase in ROADMAP.md, get its `Requirements:` list
+2. Look up each REQ-ID in REQUIREMENTS.md for full description
+3. Use concrete requirements to focus research domains
+
 **Load phase context if exists:**
 Check for `.planning/phases/XX-name/{phase}-CONTEXT.md` - bonus context from discuss-phase.
 </context>

get-shit-done/workflows/research-phase.md

@@ -113,7 +113,24 @@ If CONTEXT.md exists, use it to understand:
 - Constraints mentioned
 - Any preferences stated
 
-**3. Prior phase decisions:**
+**3. Phase requirements:**
+```bash
+cat .planning/REQUIREMENTS.md 2>/dev/null
+```
+
+Extract requirements for this phase:
+1. Find phase in ROADMAP.md, get its `Requirements:` list (e.g., "AUTH-01, AUTH-02")
+2. Look up each REQ-ID in REQUIREMENTS.md for full description
+3. Present concrete requirements:
+   ```
+   Phase ${PHASE} Requirements:
+   - AUTH-01: User can sign up with email and password
+   - AUTH-02: User receives email verification after signup
+   ```
+
+Requirements inform research focus — "email verification" tells us to research email delivery, verification flows, etc.
+
+**4. Prior phase decisions:**
 ```bash
 cat .planning/STATE.md 2>/dev/null | grep -A20 "## Accumulated Decisions"
 ```
@@ -126,6 +143,10 @@ Research context for Phase ${PHASE}: ${PHASE_NAME}
 
 Roadmap description: ${PHASE_DESCRIPTION}
 
+Requirements:
+- [REQ-ID]: [requirement description]
+- [REQ-ID]: [requirement description]
+
 [If CONTEXT.md exists:]
 Phase context available - will incorporate user preferences.