agileflow 2.36.2 → 2.37.0

package/src/core/commands/configure.md

@@ -1,5 +1,5 @@
 ---
-description: Configure advanced AgileFlow features (git, hooks, archival, CI)
+description: Configure advanced AgileFlow features (git, hooks, archival, CI, status line)
 argument-hint: (interactive menu)
 ---
 
@@ -33,6 +33,7 @@ Each feature is handled by a specialized agent:
 - **Hooks System** (`AgileFlow:agents:configuration:hooks`) - Event-driven automation
 - **Auto-Archival** (`AgileFlow:agents:configuration:archival`) - Status.json size management
 - **CI/CD** (`AgileFlow:agents:configuration:ci`) - Automated testing and quality checks
+- **Status Line** (`AgileFlow:agents:configuration:status-line`) - Custom Claude Code status bar with AgileFlow context
 
 ## Detection Phase (Run First)
 
@@ -112,6 +113,15 @@ else
   CI_CONFIGURED=false
 fi
 
+# Check status line
+if [ -f scripts/agileflow-statusline.sh ] && grep -q "statusLine" .claude/settings.json 2>/dev/null; then
+  echo "✅ Status line configured"
+  STATUSLINE_CONFIGURED=true
+else
+  echo "❌ Status line not configured"
+  STATUSLINE_CONFIGURED=false
+fi
+
 echo "===================================="
 echo ""
 ```
@@ -151,7 +161,8 @@ The AskUserQuestion tool allows you to prompt the user for input. It requires XM
     {"label": "Attribution Settings", "description": "Configure CLAUDE.md attribution policy"},
     {"label": "Hooks System", "description": "Set up event-driven automation"},
     {"label": "Auto-Archival", "description": "Manage status.json file size"},
-    {"label": "CI/CD", "description": "Set up automated testing"}
+    {"label": "CI/CD", "description": "Set up automated testing"},
+    {"label": "Status Line", "description": "Custom status bar with story/WIP/context info"}
   ]
 }]</parameter>
 </invoke>
@@ -169,7 +180,8 @@ The AskUserQuestion tool allows you to prompt the user for input. It requires XM
     {"label": "Attribution Settings", "description": "Configure CLAUDE.md attribution policy"},
     {"label": "Hooks System", "description": "Set up event-driven automation"},
     {"label": "Auto-Archival", "description": "Manage status.json file size"},
-    {"label": "CI/CD", "description": "Set up automated testing"}
+    {"label": "CI/CD", "description": "Set up automated testing"},
+    {"label": "Status Line", "description": "Custom status bar with story/WIP/context info"}
   ]
 }]</parameter>
 </invoke>
@@ -190,6 +202,7 @@ Available options:
 3. Hooks System (event-driven automation)
 4. Auto-Archival (status.json size management)
 5. CI/CD (automated testing and quality checks)
+6. Status Line (custom status bar with story/WIP/context info)
 
 You can select multiple options. Features already configured are marked with ✅.
 
@@ -199,6 +212,7 @@ Current status:
 - Hooks System: [✅ Configured / ❌ Not configured]
 - Auto-Archival: [✅ Configured / ❌ Not configured]
 - CI/CD: [✅ Configured / ❌ Not configured]
+- Status Line: [✅ Configured / ❌ Not configured]
 
 Select features to configure:
 ```
@@ -261,6 +275,16 @@ Task({
 })
 ```
 
+#### Status Line Agent
+
+```javascript
+Task({
+  subagent_type: "AgileFlow:agents:configuration:status-line",
+  description: "Configure status line",
+  prompt: "Set up a custom AgileFlow status line for Claude Code. Ask user which components to display (story, WIP, context %, cost, git branch), create the statusline script, configure .claude/settings.json, and document in CLAUDE.md."
+})
+```
+
 ### Parallel Execution
 
 **CRITICAL**: Spawn multiple agents in a **single message** for parallel execution:
@@ -281,12 +305,14 @@ Task({ subagent_type: "AgileFlow:agents:configuration:hooks", ... })
 
 Some agents have dependencies:
 - **Auto-Archival** depends on **Hooks System** (needs .claude/settings.json to exist)
+- **Status Line** depends on **Hooks System** (needs .claude/settings.json to exist)
 - **Git Config**, **Attribution**, and **CI/CD** are independent (can run in parallel)
 
 **Execution Strategy**:
 1. If user selects Git + Attribution + CI: Run in parallel (no dependencies)
 2. If user selects Hooks + Archival: Run hooks FIRST, then archival (dependency)
-3. If user selects all 5: Run Git + Attribution + CI in parallel, wait, then run Hooks, wait, then run Archival
+3. If user selects Hooks + Status Line: Run hooks FIRST, then status line (dependency)
+4. If user selects all 6: Run Git + Attribution + CI in parallel, wait, then run Hooks, wait, then run Archival + Status Line in parallel
 
 ## Agent Result Handling
 
@@ -301,6 +327,7 @@ Results:
 - Hooks System: [✅ Configured / ❌ Failed / ⏭️ Skipped]
 - Auto-Archival: [✅ Configured / ❌ Failed / ⏭️ Skipped]
 - CI/CD: [✅ Configured / ❌ Failed / ⏭️ Skipped]
+- Status Line: [✅ Configured / ❌ Failed / ⏭️ Skipped]
 
 Next steps:
 [Agent-specific next steps from results]
@@ -360,10 +387,17 @@ If an agent fails:
 - Create workflow file (`.github/workflows/ci.yml`, `.gitlab-ci.yml`, or `.circleci/config.yml`)
 - Document in CLAUDE.md with CI status, badge URL, and troubleshooting
 
+### 6. Status Line (status-line agent)
+- Ask user which components to display (story, WIP, context %, cost, git branch)
+- Create `scripts/agileflow-statusline.sh` script
+- Add `statusLine` configuration to `.claude/settings.json`
+- Document in CLAUDE.md
+- **CRITICAL**: Remind user to restart Claude Code
+
 ## Example Workflow
 
 ```
-1. User runs: /AgileFlow:configure
+1. User runs: /agileflow:configure
 
 2. Orchestrator detects current status:
    ✅ Git initialized
@@ -372,9 +406,10 @@ If an agent fails:
    ❌ Hooks system not configured
    ❌ Auto-archival not configured
    ❌ CI/CD not configured
+   ❌ Status line not configured
 
 3. Orchestrator presents menu using AskUserQuestion:
-   "Select features to configure: [Git Repository, Attribution Settings, Hooks System, Auto-Archival, CI/CD]"
+   "Select features to configure: [Git Repository, Attribution Settings, Hooks System, Auto-Archival, CI/CD, Status Line]"
 
 4. User selects: ["Attribution Settings", "Hooks System", "CI/CD"]
 
@@ -399,9 +434,9 @@ If an agent fails:
 - ALWAYS run detection phase first
 - Use AskUserQuestion tool for interactive menus
 - Spawn agents in parallel when possible (single message)
-- Respect agent dependencies (hooks before archival)
+- Respect agent dependencies (hooks before archival, hooks before status-line)
 - Display clear results summary after completion
-- Remind user to restart Claude Code if hooks were configured
+- Remind user to restart Claude Code if hooks or status line were configured
 - Be idempotent (safe to run multiple times)
 
 ## Output
@@ -411,4 +446,4 @@ If an agent fails:
 - Agent spawn confirmations
 - Final results summary
 - Next steps (agent-specific guidance)
-- **CRITICAL reminder** if hooks configured: "🔴 RESTART CLAUDE CODE NOW!"
+- **CRITICAL reminder** if hooks or status line configured: "🔴 RESTART CLAUDE CODE NOW!"

package/src/core/commands/context.md

@@ -197,18 +197,18 @@ When user pastes research results back:
 
 ```bash
 # Generate/refresh full context brief (default)
-/AgileFlow:context
-/AgileFlow:context MODE=full
+/agileflow:context
+/agileflow:context MODE=full
 
 # Export concise excerpt for pasting
-/AgileFlow:context MODE=export
+/agileflow:context MODE=export
 
 # Add a quick note
-/AgileFlow:context MODE=note NOTE="User reported auth bug in production"
+/agileflow:context MODE=note NOTE="User reported auth bug in production"
 
 # Build research prompt
-/AgileFlow:context MODE=research TOPIC="Implement OAuth 2.0 with Google"
-/AgileFlow:context MODE=research TOPIC="Add Stripe payments" DETAILS="Launch by end of sprint"
+/agileflow:context MODE=research TOPIC="Implement OAuth 2.0 with Google"
+/agileflow:context MODE=research TOPIC="Add Stripe payments" DETAILS="Launch by end of sprint"
 ```
 
 ---

package/src/core/commands/debt.md

@@ -250,7 +250,7 @@ Suggest adding to CI (weekly):
 ```yaml
 - cron: '0 0 * * 1'  # Monday
 - name: Technical debt scan
-  run: npx claude-code /AgileFlow:tech-debt SCAN=full OUTPUT=report
+  run: npx claude-code /agileflow:tech-debt SCAN=full OUTPUT=report
 ```
 
 RULES

package/src/core/commands/deps.md

@@ -508,40 +508,40 @@ USAGE EXAMPLES
 
 ### Show all dependencies
 ```bash
-/AgileFlow:dependencies
+/agileflow:dependencies
 ```
 
 ### Specific epic dependencies
 ```bash
-/AgileFlow:dependencies EPIC=EP-0010
+/agileflow:dependencies EPIC=EP-0010
 ```
 
 ### Specific story dependencies
 ```bash
-/AgileFlow:dependencies STORY=US-0032
+/agileflow:dependencies STORY=US-0032
 ```
 
 ### Only critical path analysis
 ```bash
-/AgileFlow:dependencies ANALYSIS=critical-path
+/agileflow:dependencies ANALYSIS=critical-path
 ```
 
 ### Export as Mermaid diagram
 ```bash
-/AgileFlow:dependencies FORMAT=mermaid > dependencies.mmd
+/agileflow:dependencies FORMAT=mermaid > dependencies.mmd
 ```
 
 ### Check for circular dependencies
 ```bash
-/AgileFlow:dependencies ANALYSIS=circular
+/agileflow:dependencies ANALYSIS=circular
 ```
 
 INTEGRATION WITH OTHER COMMANDS
 
-- Before `/AgileFlow:board`: Run `/AgileFlow:dependencies` to understand blockers
-- After `/AgileFlow:story-new`: Run `/AgileFlow:dependencies` to visualize impact
-- In `/AgileFlow:babysit`: Check `/AgileFlow:dependencies` before starting work
-- With `/AgileFlow:metrics`: Correlate cycle time with dependency depth
+- Before `/agileflow:board`: Run `/agileflow:dependencies` to understand blockers
+- After `/agileflow:story-new`: Run `/agileflow:dependencies` to visualize impact
+- In `/agileflow:babysit`: Check `/agileflow:dependencies` before starting work
+- With `/agileflow:metrics`: Correlate cycle time with dependency depth
 
 RULES
 - Parse dependencies from story frontmatter first (authoritative)

package/src/core/commands/diagnose.md

@@ -10,6 +10,16 @@ Run comprehensive AgileFlow system health checks to identify potential issues be
 
 ROLE: System Diagnostician
 
+INPUTS
+(no arguments - runs full system diagnostics)
+
+ACTIONS
+1) Validate all JSON files (status.json, metadata, settings)
+2) Check file structure (docs/, .agileflow/, .claude/)
+3) Verify git state and hooks
+4) Check for common issues (stale stories, invalid references)
+5) Generate health report with recommendations
+
 OBJECTIVE: Validate AgileFlow system health, identify issues, and provide actionable recommendations.
 
 **Run these diagnostic checks**:
@@ -173,7 +183,7 @@ else
   echo "1. Fix JSON validation errors using: bash scripts/validate-json.sh <file>"
   echo "2. Add missing files to .gitignore if needed"
   echo "3. Run archival if status.json is too large: bash scripts/archive-completed-stories.sh 7"
-  echo "4. Re-run diagnostics after fixes: /AgileFlow:diagnose"
+  echo "4. Re-run diagnostics after fixes: /agileflow:diagnose"
   exit 1
 fi
 ```

package/src/core/commands/docs.md

@@ -1,5 +1,6 @@
 ---
 description: Synchronize documentation with code changes
+argument-hint: [BRANCH=<name>] [BASE=<branch>] [AUTO_CREATE=yes|no]
 ---
 
 # docs-sync
@@ -148,7 +149,7 @@ CI INTEGRATION
 Suggest adding to PR checks:
 ```yaml
 - name: Check docs sync
-  run: npx claude-code /AgileFlow:docs-sync BRANCH=${{ github.head_ref }}
+  run: npx claude-code /agileflow:docs-sync BRANCH=${{ github.head_ref }}
   # Fail if critical docs missing (e.g., public API endpoints)
 ```
 

package/src/core/commands/handoff.md

@@ -1,5 +1,6 @@
 ---
 description: Document work handoff between agents
+argument-hint: STORY=<US-ID> FROM=<id> TO=<id> [SUMMARY=<text>] [BLOCKERS=<list>]
 ---
 
 # handoff

package/src/core/commands/help.md

@@ -10,6 +10,15 @@ Display a concise overview of the AgileFlow system.
 
 ROLE: System Guide
 
+INPUTS
+(no arguments - displays system overview)
+
+ACTIONS
+1) Print folder map (docs/*) and what lives where
+2) Explain Epics, Stories, ADRs, status.json, bus/log.jsonl
+3) Show daily workflow
+4) List all available commands with examples
+
 TASK
 Print a concise, one-screen overview:
 - Folder map (docs/*) and what lives where

package/src/core/commands/impact.md

@@ -1,5 +1,6 @@
 ---
 description: Analyze change impact across codebase
+argument-hint: [FILES=<paths>] [BASE=<branch>] [RUN_TESTS=yes|no]
 ---
 
 # impact-analysis
@@ -165,7 +166,7 @@ INTEGRATION
 Suggest optimized CI that only runs affected tests:
 ```yaml
 - name: Impact analysis
-  run: npx claude-code /AgileFlow:impact-analysis BASE=main
+  run: npx claude-code /agileflow:impact-analysis BASE=main
 
 - name: Run affected tests
   run: npm test -- $(cat affected-tests.txt)

package/src/core/commands/metrics.md

@@ -437,9 +437,9 @@ DASHBOARD OUTPUT
 ║                                                                 ║
 ╚════════════════════════════════════════════════════════════════╝
 
-Run `/AgileFlow:velocity` for forecasting
-Run `/AgileFlow:board` for current kanban view
-Run `/AgileFlow:retro` for retrospective insights
+Run `/agileflow:velocity` for forecasting
+Run `/agileflow:board` for current kanban view
+Run `/agileflow:retro` for retrospective insights
 ```
 
 EXPORT FORMATS
@@ -494,35 +494,35 @@ USAGE EXAMPLES
 
 ### View all metrics for last 30 days
 ```bash
-/AgileFlow:metrics
+/agileflow:metrics
 ```
 
 ### Last 90 days, specific epic
 ```bash
-/AgileFlow:metrics TIMEFRAME=90d EPIC=EP-0010
+/agileflow:metrics TIMEFRAME=90d EPIC=EP-0010
 ```
 
 ### Only cycle time, export as JSON
 ```bash
-/AgileFlow:metrics METRIC=cycle-time FORMAT=json
+/agileflow:metrics METRIC=cycle-time FORMAT=json
 ```
 
 ### Agent-specific metrics
 ```bash
-/AgileFlow:metrics OWNER=AG-API TIMEFRAME=7d
+/agileflow:metrics OWNER=AG-API TIMEFRAME=7d
 ```
 
 ### Export to CSV for spreadsheet analysis
 ```bash
-/AgileFlow:metrics FORMAT=csv > metrics.csv
+/agileflow:metrics FORMAT=csv > metrics.csv
 ```
 
 INTEGRATION WITH OTHER COMMANDS
 
-- After `/AgileFlow:velocity`: Run `/AgileFlow:metrics` to see detailed trends
-- After `/AgileFlow:board`: Run `/AgileFlow:metrics` to understand bottlenecks
-- Before `/AgileFlow:retro`: Run `/AgileFlow:metrics` to gather data for retrospective
-- In `/AgileFlow:babysit`: Auto-run `/AgileFlow:metrics` when velocity drops
+- After `/agileflow:velocity`: Run `/agileflow:metrics` to see detailed trends
+- After `/agileflow:board`: Run `/agileflow:metrics` to understand bottlenecks
+- Before `/agileflow:retro`: Run `/agileflow:metrics` to gather data for retrospective
+- In `/agileflow:babysit`: Auto-run `/agileflow:metrics` when velocity drops
 
 RULES
 - Always calculate from raw data (bus/log.jsonl, status.json)

package/src/core/commands/multi-expert.md

@@ -3,7 +3,7 @@ description: Deploy multiple domain experts on the same problem for higher confi
 argument-hint: <question or task>
 ---
 
-# /AgileFlow:multi-expert
+# /agileflow:multi-expert
 
 Deploy multiple Agent Experts on the same problem. Each expert validates independently, then results are synthesized for higher confidence answers.
 

package/src/core/commands/packages.md

@@ -235,7 +235,7 @@ Group updates by SCOPE:
    - Run update commands
    - Run tests (if available)
    - Commit with message: "chore(deps): update dependencies (<scope>)"
-   - Push and create PR using /AgileFlow:pr-template
+   - Push and create PR using /agileflow:pr-template
 
 ### Integration
 - Save report to docs/08-project/dependency-report-<YYYYMMDD>.md
@@ -283,7 +283,7 @@ None
 ## Moderate (3)
 [...]
 
-**Recommendation**: Run /AgileFlow:packages ACTION=update SCOPE=security
+**Recommendation**: Run /agileflow:packages ACTION=update SCOPE=security
 ```
 
 ---
@@ -292,29 +292,29 @@ None
 
 ```bash
 # Show dependency dashboard (default)
-/AgileFlow:packages
-/AgileFlow:packages ACTION=dashboard
+/agileflow:packages
+/agileflow:packages ACTION=dashboard
 
 # Export dashboard as HTML
-/AgileFlow:packages ACTION=dashboard OUTPUT=html
+/agileflow:packages ACTION=dashboard OUTPUT=html
 
 # Export as JSON for tooling
-/AgileFlow:packages ACTION=dashboard OUTPUT=json > deps.json
+/agileflow:packages ACTION=dashboard OUTPUT=json > deps.json
 
 # Security audit only
-/AgileFlow:packages ACTION=audit
+/agileflow:packages ACTION=audit
 
 # Update security vulnerabilities
-/AgileFlow:packages ACTION=update SCOPE=security
+/agileflow:packages ACTION=update SCOPE=security
 
 # Update all minor and patch versions
-/AgileFlow:packages ACTION=update SCOPE=minor
+/agileflow:packages ACTION=update SCOPE=minor
 
 # Update all with auto-PR
-/AgileFlow:packages ACTION=update SCOPE=all AUTO_PR=yes
+/agileflow:packages ACTION=update SCOPE=all AUTO_PR=yes
 
 # Update only production dependencies
-/AgileFlow:packages ACTION=update INCLUDE_DEV=no
+/agileflow:packages ACTION=update INCLUDE_DEV=no
 ```
 
 ---
@@ -330,7 +330,7 @@ Suggest adding automated checks:
   run: npm outdated || true  # Don't fail, just warn
 
 - name: Generate dashboard
-  run: npx claude-code /AgileFlow:packages ACTION=dashboard
+  run: npx claude-code /agileflow:packages ACTION=dashboard
 ```
 
 Suggest Dependabot config (.github/dependabot.yml):

package/src/core/commands/pr.md

@@ -1,5 +1,6 @@
 ---
 description: Generate pull request description from story
+argument-hint: STORY=<US-ID> [TITLE=<text>] [TEST_EVIDENCE=<text>]
 ---
 
 # pr-template