agileflow 2.36.1 → 2.37.0

package/README.md

@@ -58,13 +58,13 @@ npx agileflow uninstall   # Remove from project
 
 **Initialize the system:**
 ```
-/AgileFlow:setup
+/agileflow:setup
 ```
 Scaffolds docs structure, templates, and optional CI configuration.
 
 **Get help:**
 ```
-/AgileFlow:help
+/agileflow:help
 ```
 View system overview and available commands.
 
@@ -78,7 +78,7 @@ Interactive mentor guides you through epic/story creation, implementation, and P
 
 | IDE | Status | Config Location |
 |-----|--------|-----------------|
-| Claude Code | ✅ Supported | `.claude/commands/AgileFlow/` |
+| Claude Code | ✅ Supported | `.claude/commands/agileflow/` |
 | Cursor | ✅ Supported | `.cursor/rules/agileflow/` |
 | Windsurf | ✅ Supported | `.windsurf/workflows/agileflow/` |
 
@@ -99,7 +99,7 @@ AgileFlow combines three proven methodologies:
 <details>
 <summary><strong>📁 Folder Structure</strong> (click to expand)</summary>
 
-After running `/AgileFlow:setup`:
+After running `/agileflow:setup`:
 
 ```
 docs/
@@ -126,58 +126,58 @@ docs/
 <summary><strong>📚 Commands</strong> (41 total - click to expand)</summary>
 
 ### Core Workflow
-- `/AgileFlow:setup` - Bootstrap the entire system
-- `/AgileFlow:help` - Display system overview
-- `/AgileFlow:babysit` - Interactive mentor for end-to-end implementation
+- `/agileflow:setup` - Bootstrap the entire system
+- `/agileflow:help` - Display system overview
+- `/agileflow:babysit` - Interactive mentor for end-to-end implementation
 
 ### Planning & Structure
-- `/AgileFlow:epic` - Create a new epic
-- `/AgileFlow:story` - Create a user story with acceptance criteria
-- `/AgileFlow:story-validate` - Validate story completeness before development
-- `/AgileFlow:sprint` - Data-driven sprint planning with velocity forecasting
-- `/AgileFlow:adr` - Create an Architecture Decision Record
-- `/AgileFlow:agent` - Onboard a new agent
+- `/agileflow:epic` - Create a new epic
+- `/agileflow:story` - Create a user story with acceptance criteria
+- `/agileflow:story-validate` - Validate story completeness before development
+- `/agileflow:sprint` - Data-driven sprint planning with velocity forecasting
+- `/agileflow:adr` - Create an Architecture Decision Record
+- `/agileflow:agent` - Onboard a new agent
 
 ### Task Management
-- `/AgileFlow:assign` - Assign/reassign a story
-- `/AgileFlow:status` - Update story status
-- `/AgileFlow:handoff` - Document handoff between agents
+- `/agileflow:assign` - Assign/reassign a story
+- `/agileflow:status` - Update story status
+- `/agileflow:handoff` - Document handoff between agents
 
 ### Quality & CI
-- `/AgileFlow:pr` - Generate PR description
-- `/AgileFlow:ci` - Bootstrap CI workflow
-- `/AgileFlow:readme-sync` - Sync folder READMEs
-- `/AgileFlow:tests` - Automated testing infrastructure setup
-- `/AgileFlow:review` - AI-powered code review
-- `/AgileFlow:verify` - Run tests and update story test status (Session Harness)
-- `/AgileFlow:session-init` - Initialize session harness with test verification (Phase 2)
-- `/AgileFlow:resume` - Resume session with environment verification and context (Phase 2)
-- `/AgileFlow:baseline` - Mark current state as verified baseline (Phase 2)
-- `/AgileFlow:compress` - Compress status.json (fixes token limit issues)
+- `/agileflow:pr` - Generate PR description
+- `/agileflow:ci` - Bootstrap CI workflow
+- `/agileflow:readme-sync` - Sync folder READMEs
+- `/agileflow:tests` - Automated testing infrastructure setup
+- `/agileflow:review` - AI-powered code review
+- `/agileflow:verify` - Run tests and update story test status (Session Harness)
+- `/agileflow:session-init` - Initialize session harness with test verification (Phase 2)
+- `/agileflow:resume` - Resume session with environment verification and context (Phase 2)
+- `/agileflow:baseline` - Mark current state as verified baseline (Phase 2)
+- `/agileflow:compress` - Compress status.json (fixes token limit issues)
 
 ### Automation & DevOps
-- `/AgileFlow:packages` - Manage dependencies (dashboard, updates, security audits)
-- `/AgileFlow:docs` - Synchronize docs with code changes
-- `/AgileFlow:impact` - Analyze change impact on codebase
-- `/AgileFlow:debt` - Track and prioritize technical debt
-- `/AgileFlow:deploy` - Automated deployment pipeline setup
-- `/AgileFlow:changelog` - Auto-generate changelog from commits
-- `/AgileFlow:auto` - Generate stories from PRDs/mockups/specs
-- `/AgileFlow:template` - Create and manage custom templates
-- `/AgileFlow:feedback` - Collect feedback for continuous improvement
-- `/AgileFlow:update` - Generate stakeholder reports
+- `/agileflow:packages` - Manage dependencies (dashboard, updates, security audits)
+- `/agileflow:docs` - Synchronize docs with code changes
+- `/agileflow:impact` - Analyze change impact on codebase
+- `/agileflow:debt` - Track and prioritize technical debt
+- `/agileflow:deploy` - Automated deployment pipeline setup
+- `/agileflow:changelog` - Auto-generate changelog from commits
+- `/agileflow:auto` - Generate stories from PRDs/mockups/specs
+- `/agileflow:template` - Create and manage custom templates
+- `/agileflow:feedback` - Collect feedback for continuous improvement
+- `/agileflow:update` - Generate stakeholder reports
 
 ### Visualization & Analytics
-- `/AgileFlow:board` - Visual kanban board with WIP limits
-- `/AgileFlow:blockers` - Comprehensive blocker tracking with resolution suggestions
-- `/AgileFlow:velocity` - Velocity tracking and forecasting
-- `/AgileFlow:metrics` - Analytics dashboard (cycle time, lead time, throughput, flow efficiency)
-- `/AgileFlow:retro` - Automated retrospective generator with insights
-- `/AgileFlow:deps` - Dependency graph visualization with critical path detection
+- `/agileflow:board` - Visual kanban board with WIP limits
+- `/agileflow:blockers` - Comprehensive blocker tracking with resolution suggestions
+- `/agileflow:velocity` - Velocity tracking and forecasting
+- `/agileflow:metrics` - Analytics dashboard (cycle time, lead time, throughput, flow efficiency)
+- `/agileflow:retro` - Automated retrospective generator with insights
+- `/agileflow:deps` - Dependency graph visualization with critical path detection
 
 ### Web AI Integration
-- `/AgileFlow:context` - Generate/export/manage context for web AI tools (ChatGPT, Perplexity, Gemini, Claude, etc.)
-- `/AgileFlow:research` - Save research notes
+- `/agileflow:context` - Generate/export/manage context for web AI tools (ChatGPT, Perplexity, Gemini, Claude, etc.)
+- `/agileflow:research` - Save research notes
 
 </details>
 
@@ -331,7 +331,7 @@ Hooks are automatic triggers that execute commands in response to events:
        "SessionStart": [{
          "hooks": [{
            "type": "command",
-           "command": "echo '🚀 AgileFlow loaded - Type /AgileFlow:help'"
+           "command": "echo '🚀 AgileFlow loaded - Type /agileflow:help'"
          }]
        }]
      }
@@ -380,8 +380,8 @@ Hooks are automatic triggers that execute commands in response to events:
 1. **Pick a story** - Use `mentor` or check `docs/09-agents/status.json`
 2. **Implement to AC** - Follow acceptance criteria
 3. **Write tests** - Reference `docs/07-testing/test-cases/<STORY_ID>.md`
-4. **Update status** - Use `/AgileFlow:status`
-5. **Create PR** - Use `/AgileFlow:pr`
+4. **Update status** - Use `/agileflow:status`
+5. **Create PR** - Use `/agileflow:pr`
 6. **Mark done** - Update status after merge
 
 ### Multi-Agent Collaboration
@@ -389,7 +389,7 @@ Hooks are automatic triggers that execute commands in response to events:
 AgileFlow uses a message bus (`docs/09-agents/bus/log.jsonl`) for coordination:
 - Agents update `docs/09-agents/status.json` with current work
 - Messages logged to bus for async communication
-- Use `/AgileFlow:handoff` to transfer work between agents
+- Use `/agileflow:handoff` to transfer work between agents
 - WIP limit: max 2 stories per agent
 
 ### Git Worktrees for Context Preservation
@@ -404,12 +404,12 @@ For advanced users handling urgent hotfixes during feature work:
 
 **Quick Start:**
 ```bash
-# Use helper script (created by /AgileFlow:setup)
+# Use helper script (created by /agileflow:setup)
 ./docs/00-meta/scripts/worktree-create.sh auth-hotfix
 
 # Open in new window
 code ../myapp-auth-hotfix
-/AgileFlow:babysit
+/agileflow:babysit
 ```
 
 See `docs/00-meta/guides/worktrees.md` for comprehensive guide.
@@ -418,11 +418,11 @@ See `docs/00-meta/guides/worktrees.md` for comprehensive guide.
 
 Share context with web AI tools (ChatGPT, Perplexity, Gemini, Claude, etc.):
 
-1. Run `/AgileFlow:context` to generate/refresh context
-2. Use `/AgileFlow:context MODE=export` for concise excerpt
+1. Run `/agileflow:context` to generate/refresh context
+2. Use `/agileflow:context MODE=export` for concise excerpt
 3. Paste into web AI tool for research/ideation
-4. Use `/AgileFlow:context MODE=research TOPIC="..."` for structured prompts
-5. Save results with `/AgileFlow:research`
+4. Use `/agileflow:context MODE=research TOPIC="..."` for structured prompts
+5. Save results with `/agileflow:research`
 
 ### Session Harness System (v2.24.0+)
 
@@ -441,22 +441,22 @@ Session Harness System tracks test status, verifies baselines, and maintains ses
 **Quick Start:**
 ```bash
 # First time setup (interactive)
-/AgileFlow:session-init
+/agileflow:session-init
 
 # Start each session (or auto-run via hook)
-/AgileFlow:resume
+/agileflow:resume
 
 # Run tests and update test status
-/AgileFlow:verify
+/agileflow:verify
 
 # Create verified checkpoint
-/AgileFlow:baseline "Sprint 12 complete"
+/agileflow:baseline "Sprint 12 complete"
 ```
 
 **How It Works:**
 1. **Test Tracking**: Every story has `test_status` field (passing/failing/not_run)
 2. **Pre-Implementation**: Agents check test_status before starting work
-3. **Post-Implementation**: Agents run `/AgileFlow:verify` before marking complete
+3. **Post-Implementation**: Agents run `/agileflow:verify` before marking complete
 4. **Session Resume**: Loads context and detects regressions
 5. **Baselines**: Git tags mark known-good states for reset points
 
@@ -483,7 +483,7 @@ Prevent "file too large" errors:
 
 ```bash
 # Compress status.json (removes verbose fields)
-/AgileFlow:compress
+/agileflow:compress
 
 # Typical result: 80-90% size reduction
 ```
@@ -496,19 +496,19 @@ Full story content remains in `docs/06-stories/` markdown files (no data loss).
 
 ### Creating an Epic with Stories
 ```
-/AgileFlow:epic EPIC=EP-0001 TITLE="User Authentication" OWNER=AG-API GOAL="Secure user login and registration" STORIES="US-0001|Login form|AG-UI,US-0002|Auth API|AG-API"
+/agileflow:epic EPIC=EP-0001 TITLE="User Authentication" OWNER=AG-API GOAL="Secure user login and registration" STORIES="US-0001|Login form|AG-UI,US-0002|Auth API|AG-API"
 ```
 
 ### Working on a Story
 ```
-/AgileFlow:assign STORY=US-0001 NEW_OWNER=AG-UI NEW_STATUS=in-progress NOTE="Starting implementation"
+/agileflow:assign STORY=US-0001 NEW_OWNER=AG-UI NEW_STATUS=in-progress NOTE="Starting implementation"
 # ... do the work ...
-/AgileFlow:status STORY=US-0001 STATUS=in-review SUMMARY="Login form complete with tests" PR=https://github.com/...
+/agileflow:status STORY=US-0001 STATUS=in-review SUMMARY="Login form complete with tests" PR=https://github.com/...
 ```
 
 ### Recording a Decision
 ```
-/AgileFlow:adr NUMBER=0001 TITLE="Use JWT for authentication" CONTEXT="Need stateless auth for API" DECISION="JWT with 15min access + refresh tokens" CONSEQUENCES="Simpler scaling but requires token refresh flow"
+/agileflow:adr NUMBER=0001 TITLE="Use JWT for authentication" CONTEXT="Need stateless auth for API" DECISION="JWT with 15min access + refresh tokens" CONSEQUENCES="Simpler scaling but requires token refresh flow"
 ```
 
 ## Templates

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agileflow",
-  "version": "2.36.1",
+  "version": "2.37.0",
   "description": "AI-driven agile development system for Claude Code, Cursor, Windsurf, and more",
   "keywords": [
     "agile",

package/src/core/agents/accessibility.md

@@ -59,17 +59,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
 
@@ -78,7 +78,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
@@ -89,12 +89,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
 
@@ -130,7 +130,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
 
@@ -150,18 +150,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
@@ -364,10 +364,10 @@ COORDINATION WITH OTHER AGENTS
 
 SLASH COMMANDS
 
-- `/AgileFlow:context MODE=research TOPIC=...` → Research accessibility best practices
-- `/AgileFlow:ai-code-review` → Review code for accessibility issues
-- `/AgileFlow:adr-new` → Document accessibility decisions
-- `/AgileFlow:status STORY=... STATUS=...` → Update status
+- `/agileflow:context MODE=research TOPIC=...` → Research accessibility best practices
+- `/agileflow:ai-code-review` → Review code for accessibility issues
+- `/agileflow:adr-new` → Document accessibility decisions
+- `/agileflow:status STORY=... STATUS=...` → Update status
 
 WORKFLOW
 

package/src/core/agents/adr-writer.md

@@ -69,13 +69,13 @@ Create an ADR when deciding:
 SLASH COMMANDS (Proactive Use)
 
 **Research**:
-- `/AgileFlow:context MODE=research TOPIC=...` → Generate research for alternatives before writing ADR
+- `/agileflow:context MODE=research TOPIC=...` → Generate research for alternatives before writing ADR
 
 RESEARCH INTEGRATION
 
 **Before Writing ADR**:
 1. Check docs/10-research/ for existing research on the decision topic
-2. If research is missing or stale, invoke `/AgileFlow:context MODE=research TOPIC=...`
+2. If research is missing or stale, invoke `/agileflow:context MODE=research TOPIC=...`
 3. Research should cover all alternatives with pros/cons, benchmarks, trade-offs
 
 **After User Provides Research**:
@@ -85,7 +85,7 @@ RESEARCH INTEGRATION
 
 WORKFLOW
 1. **[KNOWLEDGE LOADING]** Before writing:
-   - Check docs/10-research/ for relevant research (or invoke `/AgileFlow:context MODE=research`)
+   - Check docs/10-research/ for relevant research (or invoke `/agileflow:context MODE=research`)
    - Check existing ADRs in docs/03-decisions/ for related decisions
    - Check CLAUDE.md for current architecture context
 2. Ask for decision context (what's being decided and why now?)
@@ -202,7 +202,7 @@ This contains your mental model of:
 **Then Output**:
 1. ADR context: "Next ADR: ADR-<NUMBER>, recent decisions: <list of last 3 ADRs>"
 2. If research exists: "Found research: <topic> (docs/10-research/<file>)"
-3. If no research: "No research found. I can invoke `/AgileFlow:context MODE=research` to gather alternatives."
+3. If no research: "No research found. I can invoke `/agileflow:context MODE=research` to gather alternatives."
 4. Ask: "What technical decision would you like to document?"
 5. Clarify: "I'll document context, alternatives considered, decision, and consequences."
 
@@ -222,7 +222,7 @@ This updates your expertise with what you learned, so you're faster next time.
 
 **After User Describes Decision**:
 1. Clarify context (why now? what forces?)
-2. Check docs/10-research/ for supporting research (or invoke `/AgileFlow:context MODE=research`)
+2. Check docs/10-research/ for supporting research (or invoke `/agileflow:context MODE=research`)
 3. Identify 2-5 alternatives with pros/cons
 4. Propose ADR structure (show preview)
 5. Get approval (YES/NO)

package/src/core/agents/analytics.md

@@ -59,17 +59,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
 
@@ -78,7 +78,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
@@ -89,12 +89,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
 
@@ -130,7 +130,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
 
@@ -150,18 +150,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
@@ -435,10 +435,10 @@ COORDINATION WITH OTHER AGENTS
 
 SLASH COMMANDS
 
-- `/AgileFlow:context MODE=research TOPIC=...` → Research analytics best practices
-- `/AgileFlow:ai-code-review` → Review analytics implementation for data quality
-- `/AgileFlow:adr-new` → Document analytics decisions
-- `/AgileFlow:status STORY=... STATUS=...` → Update status
+- `/agileflow:context MODE=research TOPIC=...` → Research analytics best practices
+- `/agileflow:ai-code-review` → Review analytics implementation for data quality
+- `/agileflow:adr-new` → Document analytics decisions
+- `/agileflow:status STORY=... STATUS=...` → Update status
 
 WORKFLOW
 

package/src/core/agents/api.md

@@ -103,17 +103,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
 
@@ -122,7 +122,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
@@ -133,12 +133,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
 
@@ -177,7 +177,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
 
@@ -197,18 +197,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
@@ -294,20 +294,20 @@ SLASH COMMANDS (Proactive Use)
 AG-API can directly invoke AgileFlow commands to streamline workflows:
 
 **Research & Planning**:
-- `/AgileFlow:context MODE=research TOPIC=...` → Research API patterns, database strategies, integration approaches
+- `/agileflow:context MODE=research TOPIC=...` → Research API patterns, database strategies, integration approaches
 
 **Quality & Review**:
-- `/AgileFlow:ai-code-review` → Review API code before marking in-review
-- `/AgileFlow:impact-analysis` → Analyze impact of schema changes, API breaking changes
+- `/agileflow:ai-code-review` → Review API code before marking in-review
+- `/agileflow:impact-analysis` → Analyze impact of schema changes, API breaking changes
 
 **Documentation**:
-- `/AgileFlow:adr-new` → Document API architecture decisions (REST vs GraphQL, ORM choice, auth strategy)
-- `/AgileFlow:tech-debt` → Document API debt (missing validation, N+1 queries, security gaps)
+- `/agileflow:adr-new` → Document API architecture decisions (REST vs GraphQL, ORM choice, auth strategy)
+- `/agileflow:tech-debt` → Document API debt (missing validation, N+1 queries, security gaps)
 
 **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.
 
@@ -327,12 +327,12 @@ AGENT COORDINATION
   - API tests failing → Check if test infrastructure issue or API bug
 
 - **AG-DEVOPS** (Dependencies/deployment):
-  - Need external service SDK → Request dependency via bus or `/AgileFlow:packages ACTION=update`
+  - Need external service SDK → Request dependency via bus or `/agileflow:packages ACTION=update`
   - Database migrations → Coordinate on deployment strategy (blue-green, migration timing)
   - Performance issues → Request impact analysis
 
 - **RESEARCH** (Technical research):
-  - Unfamiliar pattern → Request research via `/AgileFlow:context MODE=research`
+  - Unfamiliar pattern → Request research via `/agileflow:context MODE=research`
   - Check docs/10-research/ for existing API/database research before starting
 
 - **MENTOR** (Guidance):
@@ -349,7 +349,7 @@ RESEARCH INTEGRATION
 **Before Starting Implementation**:
 1. Check docs/10-research/ for relevant API/database/integration research
 2. Search for topics: API patterns, database design, ORM usage, authentication, external integrations
-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
@@ -389,7 +389,7 @@ WORKFLOW
 12. Update status.json: status → in-review
 13. Append bus message: `{"ts":"<ISO>","from":"AG-API","type":"status","story":"<US_ID>","text":"API implementation complete, ready for review"}`
 14. **If AG-UI was blocked**: Append unblock message: `{"ts":"<ISO>","from":"AG-API","type":"unblock","story":"<US_ID>","text":"API ready, unblocking <AG-UI-STORY-ID>"}`
-15. Use `/AgileFlow:pr-template` command to generate PR description
+15. Use `/agileflow:pr-template` command to generate PR description
 16. After merge: update status.json: status → done
 
 QUALITY CHECKLIST