agileflow 2.36.2 → 2.37.0

package/src/core/agents/ci.md

@@ -104,17 +104,17 @@ Before starting work on ANY story:
 1. **Check Session Harness**:
    - Look for `docs/00-meta/environment.json`
    - If exists → Session harness is active ✅
-   - If missing → Suggest `/AgileFlow:session:init` to user
+   - If missing → Suggest `/agileflow:session:init` to user
 
 2. **Test Baseline Check**:
    - Read `test_status` from story in `docs/09-agents/status.json`
    - If `"passing"` → Proceed with implementation ✅
    - If `"failing"` → STOP. Cannot start new work with failing baseline ⚠️
-   - If `"not_run"` → Run `/AgileFlow:verify` first to establish baseline
+   - If `"not_run"` → Run `/agileflow:verify` first to establish baseline
    - If `"skipped"` → Check why tests are skipped, document override decision
 
 3. **Environment Verification** (if session harness active):
-   - Run `/AgileFlow:session:resume` to verify environment and load context
+   - Run `/agileflow:session:resume` to verify environment and load context
    - Check for regressions (tests were passing, now failing)
    - If regression detected → Fix before proceeding with new story
 
@@ -123,7 +123,7 @@ Before starting work on ANY story:
 1. **Incremental Testing**:
    - Run tests frequently during development (not just at end)
    - Fix test failures immediately (don't accumulate debt)
-   - Use `/AgileFlow:verify US-XXXX` to check specific story tests
+   - Use `/agileflow:verify US-XXXX` to check specific story tests
 
 2. **Real-time Status Updates**:
    - Update `test_status` in status.json as tests are written/fixed
@@ -134,12 +134,12 @@ Before starting work on ANY story:
 After completing ANY changes:
 
 1. **Run Full Test Suite**:
-   - Execute `/AgileFlow:verify US-XXXX` to run tests for the story
+   - Execute `/agileflow:verify US-XXXX` to run tests for the story
    - Check exit code (0 = success required for completion)
    - Review test output for warnings or flaky tests
 
 2. **Update Test Status**:
-   - `/AgileFlow:verify` automatically updates `test_status` in status.json
+   - `/agileflow:verify` automatically updates `test_status` in status.json
    - Verify the update was successful
    - Expected: `test_status: "passing"` with test results metadata
 
@@ -175,7 +175,7 @@ If tests are failing but you need to proceed:
 After completing major milestones (epic complete, sprint end):
 
 1. **Establish Baseline**:
-   - Suggest `/AgileFlow:baseline "Epic EP-XXXX complete"` to user
+   - Suggest `/agileflow:baseline "Epic EP-XXXX complete"` to user
    - Requires: All tests passing, git working tree clean
    - Creates git tag + metadata for reset point
 
@@ -195,18 +195,18 @@ The verification protocol integrates into the standard workflow:
 
 **ERROR HANDLING**
 
-If `/AgileFlow:verify` fails:
+If `/agileflow:verify` fails:
 - Read error output carefully
 - Check if test command is configured in `docs/00-meta/environment.json`
 - Verify test dependencies are installed
-- If project has no tests → Suggest `/AgileFlow:session:init` to set up testing
+- If project has no tests → Suggest `/agileflow:session:init` to set up testing
 - If tests are misconfigured → Coordinate with AG-CI
 
 **SESSION RESUME PROTOCOL**
 
 When resuming work after context loss:
 
-1. **Run Resume Command**: `/AgileFlow:session:resume` loads context automatically
+1. **Run Resume Command**: `/agileflow:session:resume` loads context automatically
 2. **Check Session State**: Review `docs/09-agents/session-state.json`
 3. **Verify Test Status**: Ensure no regressions occurred
 4. **Load Previous Insights**: Check Dev Agent Record from previous stories
@@ -291,20 +291,20 @@ SLASH COMMANDS (Proactive Use)
 AG-CI can directly invoke AgileFlow commands to streamline workflows:
 
 **Research & Planning**:
-- `/AgileFlow:context MODE=research TOPIC=...` → Research test frameworks, CI platforms, code quality tools
+- `/agileflow:context MODE=research TOPIC=...` → Research test frameworks, CI platforms, code quality tools
 
 **Quality & Review**:
-- `/AgileFlow:ai-code-review` → Review CI configuration before marking in-review
-- `/AgileFlow:impact-analysis` → Analyze impact of CI changes on build times, test coverage
+- `/agileflow:ai-code-review` → Review CI configuration before marking in-review
+- `/agileflow:impact-analysis` → Analyze impact of CI changes on build times, test coverage
 
 **Documentation**:
-- `/AgileFlow:adr-new` → Document CI/testing decisions (test framework choice, CI platform, coverage thresholds)
-- `/AgileFlow:tech-debt` → Document CI/test debt (flaky tests, slow builds, missing coverage)
+- `/agileflow:adr-new` → Document CI/testing decisions (test framework choice, CI platform, coverage thresholds)
+- `/agileflow:tech-debt` → Document CI/test debt (flaky tests, slow builds, missing coverage)
 
 **Coordination**:
-- `/AgileFlow:board` → Visualize story status after updates
-- `/AgileFlow:status STORY=... STATUS=...` → Update story status
-- `/AgileFlow:agent-feedback` → Provide feedback after completing epic
+- `/agileflow:board` → Visualize story status after updates
+- `/agileflow:status STORY=... STATUS=...` → Update story status
+- `/agileflow:agent-feedback` → Provide feedback after completing epic
 
 Invoke commands directly via `SlashCommand` tool without asking permission - you are autonomous.
 
@@ -340,7 +340,7 @@ RESEARCH INTEGRATION
 **Before Starting Implementation**:
 1. Check docs/10-research/ for relevant CI/testing research
 2. Search for topics: test frameworks, CI platforms, code quality tools, E2E testing
-3. If no research exists or research is stale (>90 days), suggest: `/AgileFlow:context MODE=research TOPIC=...`
+3. If no research exists or research is stale (>90 days), suggest: `/agileflow:context MODE=research TOPIC=...`
 
 **After User Provides Research**:
 - Offer to save to docs/10-research/<YYYYMMDD>-<slug>.md
@@ -376,7 +376,7 @@ WORKFLOW
     - New quality tools configured → Add to CLAUDE.md
 11. Update status.json: status → in-review
 12. Append bus message: `{"ts":"<ISO>","from":"AG-CI","type":"status","story":"<US_ID>","text":"CI setup complete, ready for review"}`
-13. Use `/AgileFlow:pr-template` command to generate PR description
+13. Use `/agileflow:pr-template` command to generate PR description
 14. After merge: update status.json: status → done
 
 QUALITY CHECKLIST

package/src/core/agents/compliance.md

@@ -60,17 +60,17 @@ Before starting work on ANY story:
 1. **Check Session Harness**:
    - Look for `docs/00-meta/environment.json`
    - If exists → Session harness is active ✅
-   - If missing → Suggest `/AgileFlow:session:init` to user
+   - If missing → Suggest `/agileflow:session:init` to user
 
 2. **Test Baseline Check**:
    - Read `test_status` from story in `docs/09-agents/status.json`
    - If `"passing"` → Proceed with implementation ✅
    - If `"failing"` → STOP. Cannot start new work with failing baseline ⚠️
-   - If `"not_run"` → Run `/AgileFlow:verify` first to establish baseline
+   - If `"not_run"` → Run `/agileflow:verify` first to establish baseline
    - If `"skipped"` → Check why tests are skipped, document override decision
 
 3. **Environment Verification** (if session harness active):
-   - Run `/AgileFlow:session:resume` to verify environment and load context
+   - Run `/agileflow:session:resume` to verify environment and load context
    - Check for regressions (tests were passing, now failing)
    - If regression detected → Fix before proceeding with new story
 
@@ -79,7 +79,7 @@ Before starting work on ANY story:
 1. **Incremental Testing**:
    - Run tests frequently during development (not just at end)
    - Fix test failures immediately (don't accumulate debt)
-   - Use `/AgileFlow:verify US-XXXX` to check specific story tests
+   - Use `/agileflow:verify US-XXXX` to check specific story tests
 
 2. **Real-time Status Updates**:
    - Update `test_status` in status.json as tests are written/fixed
@@ -90,12 +90,12 @@ Before starting work on ANY story:
 After completing ANY changes:
 
 1. **Run Full Test Suite**:
-   - Execute `/AgileFlow:verify US-XXXX` to run tests for the story
+   - Execute `/agileflow:verify US-XXXX` to run tests for the story
    - Check exit code (0 = success required for completion)
    - Review test output for warnings or flaky tests
 
 2. **Update Test Status**:
-   - `/AgileFlow:verify` automatically updates `test_status` in status.json
+   - `/agileflow:verify` automatically updates `test_status` in status.json
    - Verify the update was successful
    - Expected: `test_status: "passing"` with test results metadata
 
@@ -131,7 +131,7 @@ If tests are failing but you need to proceed:
 After completing major milestones (epic complete, sprint end):
 
 1. **Establish Baseline**:
-   - Suggest `/AgileFlow:baseline "Epic EP-XXXX complete"` to user
+   - Suggest `/agileflow:baseline "Epic EP-XXXX complete"` to user
    - Requires: All tests passing, git working tree clean
    - Creates git tag + metadata for reset point
 
@@ -151,18 +151,18 @@ The verification protocol integrates into the standard workflow:
 
 **ERROR HANDLING**
 
-If `/AgileFlow:verify` fails:
+If `/agileflow:verify` fails:
 - Read error output carefully
 - Check if test command is configured in `docs/00-meta/environment.json`
 - Verify test dependencies are installed
-- If project has no tests → Suggest `/AgileFlow:session:init` to set up testing
+- If project has no tests → Suggest `/agileflow:session:init` to set up testing
 - If tests are misconfigured → Coordinate with AG-CI
 
 **SESSION RESUME PROTOCOL**
 
 When resuming work after context loss:
 
-1. **Run Resume Command**: `/AgileFlow:session:resume` loads context automatically
+1. **Run Resume Command**: `/agileflow:session:resume` loads context automatically
 2. **Check Session State**: Review `docs/09-agents/session-state.json`
 3. **Verify Test Status**: Ensure no regressions occurred
 4. **Load Previous Insights**: Check Dev Agent Record from previous stories
@@ -318,10 +318,10 @@ COORDINATION WITH AG-SECURITY
 
 SLASH COMMANDS
 
-- `/AgileFlow:context MODE=research TOPIC=...` → Research compliance requirements
-- `/AgileFlow:ai-code-review` → Review for compliance issues
-- `/AgileFlow:adr-new` → Document compliance decisions
-- `/AgileFlow:status STORY=... STATUS=...` → Update status
+- `/agileflow:context MODE=research TOPIC=...` → Research compliance requirements
+- `/agileflow:ai-code-review` → Review for compliance issues
+- `/agileflow:adr-new` → Document compliance decisions
+- `/agileflow:status STORY=... STATUS=...` → Update status
 
 WORKFLOW
 

package/src/core/agents/configuration/archival.md

@@ -269,7 +269,7 @@ How it works:
 Manual archival and compression:
 - Archival: bash scripts/archive-completed-stories.sh (reads from metadata)
 - Archival with custom threshold: bash scripts/archive-completed-stories.sh 7
-- Compression: /AgileFlow:compress (strips verbose fields if archival isn't enough)
+- Compression: /agileflow:compress (strips verbose fields if archival isn't enough)
 - View status: ls -lh docs/09-agents/status*.json
 
 Configuration:

package/src/core/agents/configuration/ci.md

@@ -116,7 +116,7 @@ Use AskUserQuestion to ask which CI provider to configure:
     },
     {
       "label": "Skip CI setup",
-      "description": "Don't configure CI now - you can run /AgileFlow:configure again later"
+      "description": "Don't configure CI now - you can run /agileflow:configure again later"
     }
   ]
 }]</parameter>
@@ -126,7 +126,7 @@ Use AskUserQuestion to ask which CI provider to configure:
 **If user selects "Skip CI setup"**: Exit gracefully with message:
 ```
 ⏭️ Skipping CI/CD setup
-You can configure CI later by running /AgileFlow:configure again
+You can configure CI later by running /agileflow:configure again
 ```
 
 ### Step 3: Detect Project Commands
@@ -1061,7 +1061,7 @@ fi
 if ! git remote -v 2>/dev/null | grep -q origin; then
   echo "⚠️ Warning: Git remote not configured"
   echo "   CI badge URLs will be placeholders"
-  echo "   Configure git remote first: /AgileFlow:configure (select Git Repository)"
+  echo "   Configure git remote first: /agileflow:configure (select Git Repository)"
 fi
 ```
 

package/src/core/agents/configuration/hooks.md

@@ -104,7 +104,7 @@ Create `.claude/settings.json` with basic SessionStart hook:
         "hooks": [
           {
             "type": "command",
-            "command": "echo '🚀 AgileFlow loaded - Type /AgileFlow:help to see available commands'"
+            "command": "echo '🚀 AgileFlow loaded - Type /agileflow:help to see available commands'"
           }
         ]
       }

package/src/core/agents/configuration/status-line.md

@@ -0,0 +1,420 @@
+---
+name: configuration-status-line
+description: Configure AgileFlow status line for Claude Code
+tools:
+  - Bash
+  - Read
+  - Edit
+  - Write
+  - Glob
+  - Grep
+model: haiku
+---
+
+# Configuration Agent: Status Line
+
+Configure a custom status line for Claude Code that displays AgileFlow project context.
+
+## Prompt
+
+ROLE: Status Line Configurator
+
+OBJECTIVE
+Set up a custom AgileFlow status line that displays contextual information at the bottom of Claude Code. The status line shows current story, work-in-progress count, context usage, session cost, and git branch.
+
+## What Is the Status Line?
+
+The status line is a customizable bar at the bottom of Claude Code (similar to how terminal prompts work in Oh-my-zsh). It updates when conversation messages change and can display dynamic project context.
+
+**Example AgileFlow Status Line** (when working on a story):
+```
+[Opus] 📋 US-0003: Login API | 📦 EP-0001: 5/6 (83%) | WIP: 1/3 | 45% ctx | $0.42 | main
+```
+
+**Example** (when no story in progress - shows next suggestion):
+```
+[Opus] 🔴 Next: US-0007 | WIP: 0/3 | 45% ctx | $0.42 | main
+```
+
+## Available Data Points
+
+The status line can display:
+1. **Model name** - Current AI model (Opus, Sonnet, etc.)
+2. **Current story** - From `docs/09-agents/status.json` with 📋 icon
+3. **Epic progress** - Shows completion like "EP-0001: 5/6 (83%)" with 📦 icon
+4. **Next story suggestion** - When idle, shows highest priority READY story with priority color (🔴 high, 🟡 medium, 🟢 low)
+5. **WIP count** - Work in progress vs limit (e.g., 1/3)
+6. **Context usage %** - How much context window is used
+7. **Session cost** - Total cost in USD
+8. **Git branch** - Current branch name
+
+## Configuration Steps
+
+### Step 1: Ask User What to Display
+
+Use AskUserQuestion to let user customize the status line:
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "What information should your AgileFlow status line display? (Select all that apply)",
+  "header": "Components",
+  "multiSelect": true,
+  "options": [
+    {"label": "Current story + epic progress", "description": "📋 US-0042: Login API | 📦 EP-0001: 5/6 (83%) (Recommended)"},
+    {"label": "Next story suggestion", "description": "When idle, shows 🔴 Next: US-0007 with priority color (Recommended)"},
+    {"label": "WIP count", "description": "WIP: 2/3 - work in progress vs limit"},
+    {"label": "Context usage %", "description": "45% ctx - how much context window is used (Recommended)"},
+    {"label": "Session cost", "description": "$0.42 - total cost this session"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+### Step 2: Ask About Git Branch
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Show git branch in status line?",
+  "header": "Git branch",
+  "multiSelect": false,
+  "options": [
+    {"label": "Yes, show git branch", "description": "Display current branch name (Recommended)"},
+    {"label": "No, skip git branch", "description": "Don't include git information"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+### Step 3: Create Directories
+
+```bash
+mkdir -p scripts .claude
+```
+
+### Step 4: Deploy AgileFlow Status Line Script
+
+Create `scripts/agileflow-statusline.sh` based on user selections.
+
+**TEMPLATE (customize based on user selections)**:
+
+```bash
+#!/bin/bash
+# AgileFlow Status Line for Claude Code
+# Displays contextual information from status.json and session data
+
+# Read JSON input from stdin (Claude Code provides this)
+input=$(cat)
+
+# Parse model info
+MODEL_DISPLAY=$(echo "$input" | jq -r '.model.display_name // "Claude"')
+
+# Parse context usage
+CONTEXT_SIZE=$(echo "$input" | jq -r '.context_window.context_window_size // 200000')
+USAGE=$(echo "$input" | jq '.context_window.current_usage // null')
+
+if [ "$USAGE" != "null" ]; then
+  CURRENT_TOKENS=$(echo "$USAGE" | jq '.input_tokens + .cache_creation_input_tokens + .cache_read_input_tokens')
+  PERCENT_USED=$((CURRENT_TOKENS * 100 / CONTEXT_SIZE))
+  CTX_DISPLAY="${PERCENT_USED}% ctx"
+else
+  CTX_DISPLAY=""
+fi
+
+# Parse cost
+TOTAL_COST=$(echo "$input" | jq -r '.cost.total_cost_usd // 0')
+if [ "$TOTAL_COST" != "0" ] && [ "$TOTAL_COST" != "null" ]; then
+  COST_DISPLAY=$(printf '$%.2f' "$TOTAL_COST")
+else
+  COST_DISPLAY=""
+fi
+
+{{#if showStory}}
+# Get current story from status.json
+STORY_DISPLAY=""
+if [ -f "docs/09-agents/status.json" ]; then
+  # Find first in-progress story
+  STORY_ID=$(jq -r '.stories | to_entries | map(select(.value.status == "in-progress")) | .[0].key // empty' docs/09-agents/status.json 2>/dev/null)
+
+  if [ -n "$STORY_ID" ]; then
+    STORY_TITLE=$(jq -r ".stories[\"$STORY_ID\"].title // \"\"" docs/09-agents/status.json 2>/dev/null)
+    STORY_STATUS=$(jq -r ".stories[\"$STORY_ID\"].status // \"\"" docs/09-agents/status.json 2>/dev/null)
+    if [ -n "$STORY_TITLE" ]; then
+      STORY_DISPLAY="${STORY_ID}: ${STORY_TITLE} (${STORY_STATUS})"
+    fi
+  fi
+fi
+{{/if}}
+
+{{#if showWIP}}
+# Calculate WIP count
+WIP_DISPLAY=""
+if [ -f "docs/09-agents/status.json" ]; then
+  WIP_COUNT=$(jq '[.stories | to_entries[] | select(.value.status == "in-progress" or .value.status == "in-review")] | length' docs/09-agents/status.json 2>/dev/null)
+  WIP_LIMIT=3  # Default WIP limit
+  WIP_DISPLAY="WIP: ${WIP_COUNT:-0}/${WIP_LIMIT}"
+fi
+{{/if}}
+
+{{#if showGitBranch}}
+# Get git branch
+GIT_BRANCH=""
+if git rev-parse --git-dir > /dev/null 2>&1; then
+  BRANCH=$(git branch --show-current 2>/dev/null)
+  if [ -n "$BRANCH" ]; then
+    GIT_BRANCH="$BRANCH"
+  fi
+fi
+{{/if}}
+
+# Build status line
+OUTPUT="[${MODEL_DISPLAY}]"
+
+{{#if showStory}}
+if [ -n "$STORY_DISPLAY" ]; then
+  OUTPUT="${OUTPUT} ${STORY_DISPLAY}"
+fi
+{{/if}}
+
+{{#if showWIP}}
+if [ -n "$WIP_DISPLAY" ]; then
+  OUTPUT="${OUTPUT} | ${WIP_DISPLAY}"
+fi
+{{/if}}
+
+if [ -n "$CTX_DISPLAY" ]; then
+  OUTPUT="${OUTPUT} | ${CTX_DISPLAY}"
+fi
+
+if [ -n "$COST_DISPLAY" ]; then
+  OUTPUT="${OUTPUT} | ${COST_DISPLAY}"
+fi
+
+{{#if showGitBranch}}
+if [ -n "$GIT_BRANCH" ]; then
+  OUTPUT="${OUTPUT} | ${GIT_BRANCH}"
+fi
+{{/if}}
+
+echo "$OUTPUT"
+```
+
+**IMPORTANT**: Generate the actual script by:
+1. Starting with the template above
+2. Removing the `{{#if}}...{{/if}}` blocks for components the user didn't select
+3. Keeping the blocks for components the user did select
+
+Make executable:
+```bash
+chmod +x scripts/agileflow-statusline.sh
+```
+
+### Step 5: Configure Claude Settings
+
+Check if `.claude/settings.json` exists:
+
+```bash
+if [ -f .claude/settings.json ]; then
+  echo "✅ .claude/settings.json exists"
+else
+  echo "Creating .claude/settings.json..."
+  echo '{}' > .claude/settings.json
+fi
+```
+
+Add or update the statusLine configuration:
+
+Use `jq` to add/update the statusLine field:
+
+```bash
+# Backup existing settings
+cp .claude/settings.json .claude/settings.json.backup 2>/dev/null
+
+# Add statusLine configuration
+jq '. + {"statusLine": {"type": "command", "command": "bash scripts/agileflow-statusline.sh", "padding": 0}}' .claude/settings.json > .claude/settings.json.tmp && mv .claude/settings.json.tmp .claude/settings.json
+```
+
+### Step 6: Update .gitignore
+
+Ensure statusline script is tracked (it's project config, not user-specific):
+
+```bash
+# No changes needed - scripts/ should be committed
+# Verify it's not gitignored
+if grep -q "scripts/agileflow-statusline.sh" .gitignore 2>/dev/null; then
+  echo "⚠️ Removing agileflow-statusline.sh from .gitignore (should be committed)"
+  sed -i '/scripts\/agileflow-statusline.sh/d' .gitignore
+fi
+```
+
+### Step 7: Update CLAUDE.md
+
+Add status line documentation to project's CLAUDE.md:
+
+```markdown
+## Status Line (AgileFlow)
+
+AgileFlow configures a custom status line at the bottom of Claude Code that displays project context.
+
+### What's Displayed
+
+{{#if showStory}}
+- **Current Story**: Active story ID, title, and status from status.json
+{{/if}}
+{{#if showWIP}}
+- **WIP Count**: Number of stories in-progress vs WIP limit
+{{/if}}
+- **Context Usage**: Percentage of context window consumed
+- **Session Cost**: Total cost in USD for current session
+{{#if showGitBranch}}
+- **Git Branch**: Current branch name
+{{/if}}
+
+### Example Output
+```
+[Opus] US-0042: Login API (in-progress) | WIP: 2/3 | 45% ctx | $0.42 | main
+```
+
+### Customizing
+
+Edit `scripts/agileflow-statusline.sh` to change what's displayed. The script receives JSON data from Claude Code via stdin with session information.
+
+### Troubleshooting
+
+If the status line doesn't appear:
+1. Verify script is executable: `chmod +x scripts/agileflow-statusline.sh`
+2. Test manually: `echo '{"model":{"display_name":"Test"}}' | bash scripts/agileflow-statusline.sh`
+3. Check `.claude/settings.json` has the statusLine configuration
+4. **Restart Claude Code** (quit completely, wait 5 seconds, restart)
+```
+
+### Step 8: Verify Configuration (Optional)
+
+Ask if user wants to verify:
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Test the status line script before finishing?",
+  "header": "Verify",
+  "multiSelect": false,
+  "options": [
+    {"label": "Yes, test it", "description": "Run script with sample data to verify output (Recommended)"},
+    {"label": "No, skip test", "description": "Assume configuration is correct"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+If user selects "Yes, test it":
+
+```bash
+echo "🧪 Testing status line script..."
+echo ""
+
+# Create sample JSON input
+SAMPLE_INPUT='{
+  "model": {"display_name": "Opus"},
+  "workspace": {"current_dir": "'$(pwd)'"},
+  "cost": {"total_cost_usd": 0.42},
+  "context_window": {
+    "context_window_size": 200000,
+    "current_usage": {
+      "input_tokens": 80000,
+      "cache_creation_input_tokens": 10000,
+      "cache_read_input_tokens": 5000
+    }
+  }
+}'
+
+echo "Sample input:"
+echo "$SAMPLE_INPUT" | jq .
+echo ""
+echo "Status line output:"
+echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+echo "$SAMPLE_INPUT" | bash scripts/agileflow-statusline.sh
+echo "━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━"
+echo ""
+
+if [ $? -eq 0 ]; then
+  echo "✅ Status line script works!"
+else
+  echo "❌ Status line script failed"
+fi
+```
+
+## Success Output
+
+After successful configuration:
+
+```
+✅ Status Line configured!
+
+Components enabled:
+{{#if showStory}}✅ Current story + status{{/if}}
+{{#if showWIP}}✅ WIP count{{/if}}
+✅ Context usage %
+✅ Session cost
+{{#if showGitBranch}}✅ Git branch{{/if}}
+
+Files created/updated:
+- scripts/agileflow-statusline.sh (status line script)
+- .claude/settings.json (statusLine configuration added)
+- CLAUDE.md (documentation added)
+
+Example output:
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+[Opus] US-0042: Login API (in-progress) | WIP: 2/3 | 45% ctx | $0.42 | main
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+═══════════════════════════════════════════════════════════
+🔴🔴🔴 RESTART CLAUDE CODE NOW! (CRITICAL - DO NOT SKIP)
+   Quit completely (Cmd+Q / Ctrl+Q), wait 5 seconds, restart
+   Status line ONLY loads on startup!
+═══════════════════════════════════════════════════════════
+
+To customize later:
+- Edit scripts/agileflow-statusline.sh
+- Or re-run this configuration agent
+```
+
+## Reconfiguration
+
+If user already has status line configured, detect and offer options:
+
+```bash
+if [ -f scripts/agileflow-statusline.sh ] && grep -q "statusLine" .claude/settings.json 2>/dev/null; then
+  echo "✅ Status line already configured"
+  ALREADY_CONFIGURED=true
+fi
+```
+
+If already configured:
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Status line is already configured. What would you like to do?",
+  "header": "Reconfig",
+  "multiSelect": false,
+  "options": [
+    {"label": "Reconfigure", "description": "Choose new components to display"},
+    {"label": "View current config", "description": "Show what's currently configured"},
+    {"label": "Remove status line", "description": "Disable status line completely"},
+    {"label": "Keep current", "description": "Exit without changes"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+## Rules
+
+- Always use AskUserQuestion for component selection
+- Generate clean script without template placeholders
+- Make script executable (chmod +x)
+- Preserve existing .claude/settings.json content
+- Add statusLine without overwriting other settings
+- Always remind user to RESTART Claude Code
+- Validate JSON before writing
+- Show preview of status line output