agileflow 2.45.0 → 2.47.0

package/package.json

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

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

@@ -46,14 +46,14 @@ Multi-Expert Orchestrator that spawns 3-5 domain experts in parallel to analyze
    - Recommended Actions - prioritized next steps
 
 ### Key Domain Mappings
-- database/schema/SQL → AgileFlow:database
-- API/endpoint/REST → AgileFlow:api
-- component/UI/frontend → AgileFlow:ui
-- test/spec/coverage → AgileFlow:testing
-- security/auth/JWT → AgileFlow:security
-- performance/cache/optimize → AgileFlow:performance
-- CI/workflow/pipeline → AgileFlow:ci
-- deploy/infrastructure/Docker → AgileFlow:devops
+- database/schema/SQL → agileflow:database
+- API/endpoint/REST → agileflow:api
+- component/UI/frontend → agileflow:ui
+- test/spec/coverage → agileflow:testing
+- security/auth/JWT → agileflow:security
+- performance/cache/optimize → agileflow:performance
+- CI/workflow/pipeline → agileflow:ci
+- deploy/infrastructure/Docker → agileflow:devops
 
 ### Key Files
 - Expert expertise definitions: `packages/cli/src/core/experts/{domain}/expertise.yaml`
@@ -95,14 +95,14 @@ DOMAIN DETECTION
 
 | Keywords | Expert to Spawn |
 |----------|-----------------|
-| database, schema, table, SQL, query | AgileFlow:database |
-| API, endpoint, REST, route, controller | AgileFlow:api |
-| component, UI, frontend, style | AgileFlow:ui |
-| test, spec, coverage, mock | AgileFlow:testing |
-| security, auth, JWT, vulnerability | AgileFlow:security |
-| performance, cache, optimize, slow | AgileFlow:performance |
-| CI, workflow, pipeline, build | AgileFlow:ci |
-| deploy, infrastructure, Docker | AgileFlow:devops |
+| database, schema, table, SQL, query | agileflow:database |
+| API, endpoint, REST, route, controller | agileflow:api |
+| component, UI, frontend, style | agileflow:ui |
+| test, spec, coverage, mock | agileflow:testing |
+| security, auth, JWT, vulnerability | agileflow:security |
+| performance, cache, optimize, slow | agileflow:performance |
+| CI, workflow, pipeline, build | agileflow:ci |
+| deploy, infrastructure, Docker | agileflow:devops |
 
 WORKFLOW
 
@@ -121,14 +121,14 @@ CRITICAL: Use run_in_background: true for ALL experts
 Task(
   description: "Security analysis",
   prompt: "FIRST: Read packages/cli/src/core/experts/security/expertise.yaml\n\nQUESTION: ...",
-  subagent_type: "AgileFlow:security",
+  subagent_type: "agileflow:security",
   run_in_background: true
 )
 
 Task(
   description: "API analysis",
   prompt: "FIRST: Read packages/cli/src/core/experts/api/expertise.yaml\n\nQUESTION: ...",
-  subagent_type: "AgileFlow:api",
+  subagent_type: "agileflow:api",
   run_in_background: true
 )
 

package/src/core/commands/assign.md

@@ -82,7 +82,7 @@ ACTIONS
    # Validate status.json after modification
    if ! jq empty docs/09-agents/status.json 2>/dev/null; then
      echo "❌ ERROR: status.json is now invalid JSON!"
-     echo "Run: bash scripts/validate-json.sh docs/09-agents/status.json"
+     echo "Fix: Use jq to validate and repair the JSON structure"
      exit 1
    fi
    ```

package/src/core/commands/babysit.md

@@ -436,7 +436,7 @@ AGENT SPAWNING - FOR COMPLEX TASKS
 Task(
   description: "Brief 3-5 word description",
   prompt: "Detailed task for the agent",
-  subagent_type: "AgileFlow:<agent-name>"
+  subagent_type: "agileflow:<agent-name>"
 )
 ```
 
@@ -449,14 +449,14 @@ Use `run_in_background: true` when tasks can run in parallel:
 Task(
   description: "Create API endpoint",
   prompt: "Implement /api/users endpoint with CRUD operations",
-  subagent_type: "AgileFlow:api",
+  subagent_type: "agileflow:api",
   run_in_background: true
 )
 
 Task(
   description: "Create user form component",
   prompt: "Build UserForm component with validation",
-  subagent_type: "AgileFlow:ui",
+  subagent_type: "agileflow:ui",
   run_in_background: true
 )
 
@@ -475,8 +475,8 @@ Task(
 User: "Add user profile feature with API and UI"
 
 Babysit thinking:
-- This has API work → spawn AgileFlow:api
-- This has UI work → spawn AgileFlow:ui
+- This has API work → spawn agileflow:api
+- This has UI work → spawn agileflow:ui
 - These are independent → run in parallel!
 
 Babysit action:
@@ -492,17 +492,17 @@ Babysit action:
 
 | Complex Task Type | Agent to Spawn | Async? |
 |-------------------|----------------|--------|
-| Multi-file UI feature | `AgileFlow:ui` | Yes if API also needed |
-| New API endpoints | `AgileFlow:api` | Yes if UI also needed |
-| Schema design/migrations | `AgileFlow:database` | Usually yes |
-| Test suite creation | `AgileFlow:testing` | Yes alongside impl |
-| CI/CD setup | `AgileFlow:ci` | Yes |
-| Security audit/impl | `AgileFlow:security` | Yes |
-| Performance optimization | `AgileFlow:performance` | Yes |
-| Large documentation | `AgileFlow:documentation` | Yes |
-| Technical research | `AgileFlow:research` | Yes |
-| Epic/story breakdown | `AgileFlow:epic-planner` | No (need result) |
-| Architecture decisions | `AgileFlow:adr-writer` | Yes |
+| Multi-file UI feature | `agileflow:ui` | Yes if API also needed |
+| New API endpoints | `agileflow:api` | Yes if UI also needed |
+| Schema design/migrations | `agileflow:database` | Usually yes |
+| Test suite creation | `agileflow:testing` | Yes alongside impl |
+| CI/CD setup | `agileflow:ci` | Yes |
+| Security audit/impl | `agileflow:security` | Yes |
+| Performance optimization | `agileflow:performance` | Yes |
+| Large documentation | `agileflow:documentation` | Yes |
+| Technical research | `agileflow:research` | Yes |
+| Epic/story breakdown | `agileflow:epic-planner` | No (need result) |
+| Architecture decisions | `agileflow:adr-writer` | Yes |
 
 **PARALLEL PATTERNS** (for complex multi-domain tasks):
 - `api` + `ui` → Full-stack feature in parallel
@@ -537,29 +537,29 @@ When analyzing the user's request, identify keywords and spawn the matching expe
 
 | Keywords Detected | Expert to Spawn | Reason |
 |-------------------|-----------------|--------|
-| database, schema, migration, SQL, query, table, model | `AgileFlow:database` | Database schema/query work |
-| API, endpoint, REST, GraphQL, route, controller | `AgileFlow:api` | Backend API work |
-| component, UI, frontend, button, form, style, CSS | `AgileFlow:ui` | Frontend/UI work |
-| test, spec, coverage, mock, fixture, assertion | `AgileFlow:testing` | Test implementation |
-| CI, workflow, GitHub Actions, pipeline, build | `AgileFlow:ci` | CI/CD configuration |
-| deploy, infrastructure, Docker, Kubernetes, env | `AgileFlow:devops` | DevOps/deployment |
-| security, auth, JWT, OAuth, vulnerability, XSS | `AgileFlow:security` | Security implementation |
-| performance, optimize, cache, latency, profiling | `AgileFlow:performance` | Performance optimization |
-| accessibility, ARIA, a11y, screen reader, WCAG | `AgileFlow:accessibility` | Accessibility work |
-| docs, README, documentation, JSDoc, comment | `AgileFlow:documentation` | Documentation work |
-| refactor, cleanup, technical debt, code smell | `AgileFlow:refactor` | Code refactoring |
-| mobile, React Native, Flutter, iOS, Android | `AgileFlow:mobile` | Mobile development |
-| webhook, integration, third-party, API client | `AgileFlow:integrations` | Third-party integrations |
-| analytics, tracking, metrics, event, dashboard | `AgileFlow:analytics` | Analytics implementation |
-| logging, monitoring, alerting, observability | `AgileFlow:monitoring` | Monitoring/observability |
-| compliance, GDPR, HIPAA, audit, privacy | `AgileFlow:compliance` | Compliance work |
-| data migration, ETL, transform, import, export | `AgileFlow:datamigration` | Data migration |
-| design system, tokens, theme, Figma, mockup | `AgileFlow:design` | Design system work |
-| product, requirements, user story, AC, acceptance | `AgileFlow:product` | Product/requirements |
-| QA, quality, regression, test plan, release | `AgileFlow:qa` | QA/quality assurance |
-| ADR, architecture decision, trade-off | `AgileFlow:adr-writer` | Architecture decisions |
-| research, investigate, best practices, docs | `AgileFlow:research` | Technical research |
-| epic, story, breakdown, planning, estimate | `AgileFlow:epic-planner` | Epic/story planning |
+| database, schema, migration, SQL, query, table, model | `agileflow:database` | Database schema/query work |
+| API, endpoint, REST, GraphQL, route, controller | `agileflow:api` | Backend API work |
+| component, UI, frontend, button, form, style, CSS | `agileflow:ui` | Frontend/UI work |
+| test, spec, coverage, mock, fixture, assertion | `agileflow:testing` | Test implementation |
+| CI, workflow, GitHub Actions, pipeline, build | `agileflow:ci` | CI/CD configuration |
+| deploy, infrastructure, Docker, Kubernetes, env | `agileflow:devops` | DevOps/deployment |
+| security, auth, JWT, OAuth, vulnerability, XSS | `agileflow:security` | Security implementation |
+| performance, optimize, cache, latency, profiling | `agileflow:performance` | Performance optimization |
+| accessibility, ARIA, a11y, screen reader, WCAG | `agileflow:accessibility` | Accessibility work |
+| docs, README, documentation, JSDoc, comment | `agileflow:documentation` | Documentation work |
+| refactor, cleanup, technical debt, code smell | `agileflow:refactor` | Code refactoring |
+| mobile, React Native, Flutter, iOS, Android | `agileflow:mobile` | Mobile development |
+| webhook, integration, third-party, API client | `agileflow:integrations` | Third-party integrations |
+| analytics, tracking, metrics, event, dashboard | `agileflow:analytics` | Analytics implementation |
+| logging, monitoring, alerting, observability | `agileflow:monitoring` | Monitoring/observability |
+| compliance, GDPR, HIPAA, audit, privacy | `agileflow:compliance` | Compliance work |
+| data migration, ETL, transform, import, export | `agileflow:datamigration` | Data migration |
+| design system, tokens, theme, Figma, mockup | `agileflow:design` | Design system work |
+| product, requirements, user story, AC, acceptance | `agileflow:product` | Product/requirements |
+| QA, quality, regression, test plan, release | `agileflow:qa` | QA/quality assurance |
+| ADR, architecture decision, trade-off | `agileflow:adr-writer` | Architecture decisions |
+| research, investigate, best practices, docs | `agileflow:research` | Technical research |
+| epic, story, breakdown, planning, estimate | `agileflow:epic-planner` | Epic/story planning |
 
 **AUTO-SPAWN WORKFLOW**:
 
@@ -582,7 +582,7 @@ Babysit Response:
 Task(
   description: "Add sessions table",
   prompt: "FIRST: Read your expertise file at packages/cli/src/core/experts/database/expertise.yaml to understand current schema patterns. Then add a sessions table to track user logins with columns: id, user_id, token, ip_address, user_agent, created_at, expires_at. Follow existing schema conventions.",
-  subagent_type: "AgileFlow:database"
+  subagent_type: "agileflow:database"
 )
 ```
 

package/src/core/commands/configure.md

@@ -242,14 +242,14 @@ For features needing extra user input, spawn specialized agents:
 ```javascript
 // CI/CD - needs provider and commands
 Task({
-  subagent_type: "AgileFlow:agents:configuration:ci",
+  subagent_type: "agileflow:configuration:ci",
   description: "Configure CI/CD",
   prompt: "Set up CI/CD workflow. Ask for provider (GitHub Actions, GitLab CI, CircleCI) and commands."
 })
 
 // Git config - needs remote URL
 Task({
-  subagent_type: "AgileFlow:agents:configuration:git-config",
+  subagent_type: "agileflow:configuration:git-config",
   description: "Configure git",
   prompt: "Set up git remote. Ask for URL."
 })

package/src/core/commands/diagnose.md

@@ -4,14 +4,6 @@ description: System health diagnostics
 
 # diagnose
 
-<!-- STEP 0: ACTIVATION -->
-<function_calls>
-<invoke name="Bash">
-<parameter name="command">node /home/coder/AgileFlow/scripts/activate-command.js diagnose</parameter>
-<parameter name="description">Activate diagnose command and show compact summary</parameter>
-</invoke>
-</function_calls>
-
 Run comprehensive AgileFlow system health checks to identify potential issues before they cause failures.
 
 ## Prompt
@@ -250,9 +242,9 @@ else
   echo "⚠️  Found $JSON_ERRORS issue(s) that need attention."
   echo ""
   echo "Next steps:"
-  echo "1. Fix JSON validation errors using: bash scripts/validate-json.sh <file>"
+  echo "1. Fix JSON validation errors using: jq empty <file> to check, then repair manually"
   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 "3. Run archival if status.json is too large: bash scripts/archive-completed-stories.sh"
   echo "4. Re-run diagnostics after fixes: /agileflow:diagnose"
   exit 1
 fi

package/src/core/commands/help.md

@@ -21,7 +21,7 @@ node scripts/obtain-context.js help
 **PURPOSE**: Immediately load full context before executing any logic.
 
 **ACTIONS**:
-1. Read `/home/coder/AgileFlow/packages/cli/src/core/commands/help.md` (this file) in its entirety
+1. Read this command file (`.agileflow/commands/help.md`) in its entirety
 2. Absorb all instructions, rules, and examples
 3. Proceed to execution phase with complete context
 

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

@@ -79,16 +79,16 @@ Analyze the user's question/task to identify relevant domains.
 
 | Domain | Keywords | Expert |
 |--------|----------|--------|
-| Database | schema, table, query, migration, SQL, model | AgileFlow:database |
-| API | endpoint, REST, GraphQL, route, controller, backend | AgileFlow:api |
-| UI | component, frontend, button, form, style, CSS | AgileFlow:ui |
-| Testing | test, spec, coverage, mock, assertion | AgileFlow:testing |
-| Security | auth, JWT, OAuth, vulnerability, XSS, CSRF | AgileFlow:security |
-| Performance | optimize, cache, latency, profiling, slow | AgileFlow:performance |
-| CI/CD | workflow, pipeline, build, deploy, GitHub Actions | AgileFlow:ci |
-| DevOps | infrastructure, Docker, Kubernetes, env | AgileFlow:devops |
-| Accessibility | ARIA, a11y, screen reader, WCAG | AgileFlow:accessibility |
-| Architecture | design, pattern, structure, decision | AgileFlow:adr-writer |
+| Database | schema, table, query, migration, SQL, model | agileflow:database |
+| API | endpoint, REST, GraphQL, route, controller, backend | agileflow:api |
+| UI | component, frontend, button, form, style, CSS | agileflow:ui |
+| Testing | test, spec, coverage, mock, assertion | agileflow:testing |
+| Security | auth, JWT, OAuth, vulnerability, XSS, CSRF | agileflow:security |
+| Performance | optimize, cache, latency, profiling, slow | agileflow:performance |
+| CI/CD | workflow, pipeline, build, deploy, GitHub Actions | agileflow:ci |
+| DevOps | infrastructure, Docker, Kubernetes, env | agileflow:devops |
+| Accessibility | ARIA, a11y, screen reader, WCAG | agileflow:accessibility |
+| Architecture | design, pattern, structure, decision | agileflow:adr-writer |
 
 **Selection Rules**:
 - Select 3-5 experts maximum (balance coverage vs. overhead)
@@ -116,21 +116,21 @@ Analyze this from your {domain1} perspective:
 4. Confidence level (High/Medium/Low) and why?
 
 Be specific with file paths and code references.",
-  subagent_type: "AgileFlow:{domain1}",
+  subagent_type: "agileflow:{domain1}",
   run_in_background: true
 )
 
 Task(
   description: "[Domain 2] analysis",
   prompt: "...",
-  subagent_type: "AgileFlow:{domain2}",
+  subagent_type: "agileflow:{domain2}",
   run_in_background: true
 )
 
 Task(
   description: "[Domain 3] analysis",
   prompt: "...",
-  subagent_type: "AgileFlow:{domain3}",
+  subagent_type: "agileflow:{domain3}",
   run_in_background: true
 )
 ```
@@ -220,10 +220,10 @@ Analyze all expert responses and synthesize:
 
 **Step 2 - Deploy Experts**:
 ```
-Task(subagent_type: "AgileFlow:security", prompt: "Analyze auth security...", run_in_background: true)
-Task(subagent_type: "AgileFlow:api", prompt: "Analyze auth API implementation...", run_in_background: true)
-Task(subagent_type: "AgileFlow:testing", prompt: "Analyze auth test coverage...", run_in_background: true)
-Task(subagent_type: "AgileFlow:database", prompt: "Analyze credential storage...", run_in_background: true)
+Task(subagent_type: "agileflow:security", prompt: "Analyze auth security...", run_in_background: true)
+Task(subagent_type: "agileflow:api", prompt: "Analyze auth API implementation...", run_in_background: true)
+Task(subagent_type: "agileflow:testing", prompt: "Analyze auth test coverage...", run_in_background: true)
+Task(subagent_type: "agileflow:database", prompt: "Analyze credential storage...", run_in_background: true)
 ```
 
 **Step 3 - Collect & Synthesize**:

package/src/core/commands/packages.md

@@ -21,7 +21,7 @@ node scripts/obtain-context.js packages
 **PURPOSE**: Immediately load full context before executing any logic.
 
 **ACTIONS**:
-1. Read `/home/coder/AgileFlow/packages/cli/src/core/commands/packages.md` (this file) in its entirety
+1. Read this command file (`.agileflow/commands/packages.md`) in its entirety
 2. Absorb all instructions, rules, and examples
 3. Proceed to execution phase with complete context
 

package/src/core/commands/readme-sync.md

@@ -22,7 +22,7 @@ node scripts/obtain-context.js readme-sync
 **PURPOSE**: Immediately load full context before executing any logic.
 
 **ACTIONS**:
-1. Read `/home/coder/AgileFlow/packages/cli/src/core/commands/readme-sync.md` (this file) in its entirety
+1. Read this command file (`.agileflow/commands/readme-sync.md`) in its entirety
 2. Absorb all instructions, rules, and examples
 3. Proceed to execution phase with complete context
 
@@ -78,7 +78,7 @@ Task(
     4. Build new '## Contents' section
     5. Show diff and ask for confirmation
     6. Update if approved",
-  subagent_type: "AgileFlow:readme-updater"
+  subagent_type: "agileflow:readme-updater"
 )
 ```
 

package/src/core/commands/research.md

@@ -21,7 +21,7 @@ node scripts/obtain-context.js research
 **PURPOSE**: Immediately load full context before executing any logic.
 
 **ACTIONS**:
-1. Read `/home/coder/AgileFlow/packages/cli/src/core/commands/research.md` (this file) in its entirety
+1. Read this command file (`.agileflow/commands/research.md`) in its entirety
 2. Absorb all instructions, rules, and examples
 3. Proceed to execution phase with complete context
 

package/src/core/commands/status.md

@@ -24,7 +24,7 @@ This gathers git status, stories/epics, session state, and registers for PreComp
 **PURPOSE**: Immediately load full context before executing any logic.
 
 **ACTIONS**:
-1. Read `/home/coder/AgileFlow/packages/cli/src/core/commands/status.md` (this file) in its entirety
+1. Read this command file (`.agileflow/commands/status.md`) in its entirety
 2. Absorb all instructions, rules, and examples
 3. Proceed to execution phase with complete context
 
@@ -48,7 +48,7 @@ This gathers git status, stories/epics, session state, and registers for PreComp
 - **Backup**: Restore from docs/09-agents/status.json.backup if validation fails
 - **Output**: Diff-first, then YES/NO confirmation
 - **Critical**: User text automatically escaped by jq
-- **Related**: docs/09-agents/status.json, bus/log.jsonl, scripts/validate-json.sh
+- **Related**: docs/09-agents/status.json, bus/log.jsonl
 <!-- COMPACT_SUMMARY_END -->
 
 ---
@@ -69,7 +69,7 @@ ACTIONS
    # Validate status.json after modification
    if ! jq empty docs/09-agents/status.json 2>/dev/null; then
      echo "❌ ERROR: status.json is now invalid JSON after update!"
-     echo "Run: bash scripts/validate-json.sh docs/09-agents/status.json"
+     echo "Fix: Use jq to validate and repair the JSON structure"
      exit 1
    fi
    ```

package/src/core/commands/story-validate.md

@@ -22,7 +22,7 @@ node scripts/obtain-context.js story-validate
 **PURPOSE**: Immediately load full context before executing any logic.
 
 **ACTIONS**:
-1. Read `/home/coder/AgileFlow/packages/cli/src/core/commands/story-validate.md` (this file) in its entirety
+1. Read this command file (`.agileflow/commands/story-validate.md`) in its entirety
 2. Absorb all instructions, rules, and examples
 3. Proceed to execution phase with complete context
 

package/src/core/commands/validate-expertise.md

@@ -155,10 +155,10 @@ EXECUTION
 Run the validation script:
 ```bash
 # All domains
-bash .agileflow/scripts/validate-expertise.sh
+bash scripts/validate-expertise.sh
 
 # Specific domain
-bash .agileflow/scripts/validate-expertise.sh database
+bash scripts/validate-expertise.sh database
 ```
 
 Or manually check using Read tool on expertise files in:

package/tools/cli/installers/ide/claude-code.js

@@ -101,7 +101,7 @@ class ClaudeCodeSetup extends BaseIdeSetup {
       true // Inject dynamic content for top-level commands
     );
 
-    // Also install agents (they're in a separate directory in agileflowDir)
+    // Also install agents as slash commands (.claude/commands/agileflow/agents/)
     const agentsSource = path.join(agileflowDir, 'agents');
     const agentsTargetDir = path.join(agileflowCommandsDir, 'agents');
     const agentResult = await this.installCommandsRecursive(
@@ -111,6 +111,17 @@ class ClaudeCodeSetup extends BaseIdeSetup {
       false // No dynamic content for agents
     );
 
+    // ALSO install agents as spawnable subagents (.claude/agents/agileflow/)
+    // This allows Task tool to spawn them with subagent_type: "agileflow:ui"
+    const spawnableAgentsDir = path.join(claudeDir, 'agents', 'agileflow');
+    await this.installCommandsRecursive(
+      agentsSource,
+      spawnableAgentsDir,
+      agileflowDir,
+      false
+    );
+    console.log(chalk.dim(`    - Spawnable agents: .claude/agents/agileflow/`));
+
     const totalCommands = commandResult.commands + agentResult.commands;
     const totalSubdirs = commandResult.subdirs + (agentResult.commands > 0 ? 1 : 0) + agentResult.subdirs;