agileflow 2.46.0 → 2.48.0

package/package.json

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

package/src/core/agents/accessibility.md

@@ -1,5 +1,5 @@
 ---
-name: accessibility
+name: agileflow-accessibility
 description: Accessibility specialist for WCAG compliance, inclusive design, assistive technology support, and accessibility testing.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

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

@@ -1,5 +1,5 @@
 ---
-name: adr-writer
+name: agileflow-adr-writer
 description: Architecture Decision Record specialist. Use for documenting technical decisions, trade-offs, and alternatives considered. Ensures decisions are recorded for future reference.
 tools: Read, Write, Edit, Glob, Grep
 model: haiku

package/src/core/agents/analytics.md

@@ -1,5 +1,5 @@
 ---
-name: analytics
+name: agileflow-analytics
 description: Analytics specialist for event tracking, data analysis, metrics dashboards, user behavior analysis, and data-driven insights.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/api.md

@@ -1,5 +1,5 @@
 ---
-name: api
+name: agileflow-api
 description: Services/data layer specialist. Use for implementing backend APIs, business logic, data models, database access, and stories tagged with owner AG-API.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/ci.md

@@ -1,5 +1,5 @@
 ---
-name: ci
+name: agileflow-ci
 description: CI/CD and quality specialist. Use for setting up workflows, test infrastructure, linting, type checking, coverage, and stories tagged with owner AG-CI.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/compliance.md

@@ -1,5 +1,5 @@
 ---
-name: compliance
+name: agileflow-compliance
 description: Compliance specialist for regulatory compliance, GDPR, HIPAA, SOC2, audit trails, legal requirements, and compliance documentation.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/database.md

@@ -1,5 +1,5 @@
 ---
-name: database
+name: agileflow-database
 description: Database specialist for schema design, migrations, query optimization, data modeling, and database-intensive features.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/datamigration.md

@@ -1,5 +1,5 @@
 ---
-name: datamigration
+name: agileflow-datamigration
 description: Data migration specialist for zero-downtime migrations, data validation, rollback strategies, and large-scale data movements.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/design.md

@@ -1,5 +1,5 @@
 ---
-name: design
+name: agileflow-design
 description: Design specialist for UI/UX design systems, visual design, design patterns, design documentation, and design-driven development.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/devops.md

@@ -1,5 +1,5 @@
 ---
-name: devops
+name: agileflow-devops
 description: DevOps and automation specialist. Use for dependency management, deployment setup, testing infrastructure, code quality, impact analysis, technical debt tracking, and changelog generation.
 tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch
 model: haiku

package/src/core/agents/documentation.md

@@ -1,5 +1,5 @@
 ---
-name: documentation
+name: agileflow-documentation
 description: Documentation specialist for technical docs, API documentation, user guides, tutorials, and documentation maintenance.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/epic-planner.md

@@ -1,5 +1,5 @@
 ---
-name: epic-planner
+name: agileflow-epic-planner
 description: Epic and story planning specialist. Use for breaking down large features into epics and stories, writing acceptance criteria, estimating effort, and mapping dependencies.
 tools: Read, Write, Edit, Glob, Grep
 model: sonnet

package/src/core/agents/integrations.md

@@ -1,5 +1,5 @@
 ---
-name: integrations
+name: agileflow-integrations
 description: Integration specialist for third-party APIs, webhooks, payment processors, external services, and API connectivity.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/mentor.md

@@ -1,5 +1,5 @@
 ---
-name: mentor
+name: agileflow-mentor
 description: End-to-end implementation mentor. Use for guiding feature implementation from idea to PR, researching approaches, creating missing epics/stories, and orchestrating multi-step workflows.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet

package/src/core/agents/mobile.md

@@ -1,5 +1,5 @@
 ---
-name: mobile
+name: agileflow-mobile
 description: Mobile specialist for React Native, Flutter, cross-platform mobile development, and mobile-specific features.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/monitoring.md

@@ -1,5 +1,5 @@
 ---
-name: monitoring
+name: agileflow-monitoring
 description: Monitoring specialist for observability, logging strategies, alerting rules, metrics dashboards, and production visibility.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

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

@@ -1,5 +1,5 @@
 ---
-name: multi-expert
+name: agileflow-multi-expert
 description: Multi-expert orchestrator that deploys 3-5 domain experts on the same problem and synthesizes results for high-confidence answers.
 tools: Read, Write, Edit, Bash, Glob, Grep, Task, TaskOutput
 model: sonnet
@@ -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/agents/performance.md

@@ -1,5 +1,5 @@
 ---
-name: performance
+name: agileflow-performance
 description: Performance specialist for optimization, profiling, benchmarking, scalability, and performance-critical features.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/product.md

@@ -1,5 +1,5 @@
 ---
-name: product
+name: agileflow-product
 description: Product specialist for requirements analysis, user stories, acceptance criteria clarity, and feature validation before epic planning.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/qa.md

@@ -1,5 +1,5 @@
 ---
-name: qa
+name: agileflow-qa
 description: QA specialist for test strategy, test planning, quality metrics, regression testing, and release readiness validation.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/readme-updater.md

@@ -1,5 +1,5 @@
 ---
-name: readme-updater
+name: agileflow-readme-updater
 description: README specialist for auditing and updating all documentation files across project folders.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/refactor.md

@@ -1,5 +1,5 @@
 ---
-name: refactor
+name: agileflow-refactor
 description: Refactoring specialist for technical debt cleanup, legacy code modernization, codebase health, and code quality improvements.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/research.md

@@ -1,5 +1,5 @@
 ---
-name: research
+name: agileflow-research
 description: Research specialist. Use for gathering technical information, creating research prompts for ChatGPT, saving research notes, and maintaining the research index.
 tools: Read, Write, Edit, Glob, Grep, WebFetch, WebSearch
 model: haiku

package/src/core/agents/security.md

@@ -1,5 +1,5 @@
 ---
-name: security
+name: agileflow-security
 description: Security specialist for vulnerability analysis, authentication patterns, authorization, compliance, and security reviews before release.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/testing.md

@@ -1,5 +1,5 @@
 ---
-name: testing
+name: agileflow-testing
 description: Testing specialist for test strategy, test patterns, coverage optimization, and comprehensive test suite design (different from CI infrastructure).
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/agents/ui.md

@@ -1,5 +1,5 @@
 ---
-name: ui
+name: agileflow-ui
 description: UI/presentation layer specialist. Use for implementing front-end components, styling, theming, accessibility features, and stories tagged with owner AG-UI.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku

package/src/core/commands/babysit.md

@@ -3,7 +3,7 @@ description: Interactive mentor for end-to-end feature implementation
 compact_context:
   priority: critical
   preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:babysit - Interactive mentor mode"
+    - "ACTIVE COMMAND: /agileflow-babysit - Interactive mentor mode"
     - "MUST use AskUserQuestion tool for ALL user decisions (task selection, approach choices, next steps)"
     - "MUST track progress with TodoWrite tool throughout the session"
     - "MUST end EVERY response with AskUserQuestion presenting next step options"
@@ -16,7 +16,7 @@ compact_context:
     - pending_decision
 ---
 
-# /agileflow:babysit
+# /agileflow-babysit
 
 End-to-end mentor for implementing features.
 
@@ -165,7 +165,7 @@ GOAL
   3) Analyze architecture and plan small steps; assess implementation approach; propose file changes; write code & tests safely.
   4) Update docs/09-agents/status.json and bus/log.jsonl (valid JSON).
   5) Prepare PR description and next actions.
-  6) Integrate research (docs/10-research); if gaps exist, suggest /agileflow:context MODE=research and save results.
+  6) Integrate research (docs/10-research); if gaps exist, suggest /agileflow-context MODE=research and save results.
   7) Ensure minimal CI exists; offer to create/update .github/workflows/ci.yml or fix it if failing.
 
 🔴 ⚠️ MANDATORY CONTEXT LOADING ON FIRST RUN ⚠️ 🔴
@@ -296,11 +296,11 @@ After loading context, analyze status.json, roadmap, and README TODOs to generat
     },
     {
       "label": "Research: JWT best practices",
-      "description": "📚 Prep work for Auth epic | Save time debugging later | /agileflow:context MODE=research"
+      "description": "📚 Prep work for Auth epic | Save time debugging later | /agileflow-context MODE=research"
     },
     {
       "label": "Create new epic/story",
-      "description": "💡 Start something new | Use /agileflow:epic or /agileflow:story"
+      "description": "💡 Start something new | Use /agileflow-epic or /agileflow-story"
     },
     {
       "label": "Other",
@@ -319,11 +319,11 @@ After loading context, analyze status.json, roadmap, and README TODOs to generat
 - **Limit to 5-6 options** - More than 6 creates decision paralysis
 - **"Other" is always last** - Custom input option
 
-**If research is missing/outdated**: Include research option with tip about /agileflow:context MODE=research
+**If research is missing/outdated**: Include research option with tip about /agileflow-context MODE=research
 
 RESEARCH INTEGRATION
 
-**💡 TIP: `/agileflow:context MODE=research` CAN HELP AVOID DEBUGGING HEADACHES**
+**💡 TIP: `/agileflow-context MODE=research` CAN HELP AVOID DEBUGGING HEADACHES**
 
 Consider using MODE=research when implementing new features - it can help you avoid common pitfalls, security issues, and save time debugging by learning from best practices upfront.
 
@@ -343,7 +343,7 @@ Consider using MODE=research when implementing new features - it can help you av
 
 **INTEGRATION WITH EXISTING RESEARCH**:
 - If a relevant note exists in docs/10-research: summarize 5–8 bullets + path; apply caveats to the plan.
-- If none/stale (>90 days)/conflicting: **IMMEDIATELY** propose /agileflow:context MODE=research TOPIC="..."; after the user pastes results, offer to save:
+- If none/stale (>90 days)/conflicting: **IMMEDIATELY** propose /agileflow-context MODE=research TOPIC="..."; after the user pastes results, offer to save:
   - docs/10-research/<YYYYMMDD>-<slug>.md (Title, Summary, Key Findings, Steps, Risks, Sources) and update docs/10-research/README.md.
 
 DEFINITION OF READY
@@ -352,7 +352,7 @@ DEFINITION OF READY
 - ✓ Test stub at docs/07-testing/test-cases/<US_ID>.md
 - ✓ Dependencies resolved and documented
 - ✓ Previous Story Insights included (if applicable to epic)
-- ✓ Story validated via `/agileflow:story-validate` (all checks passing)
+- ✓ Story validated via `/agileflow-story-validate` (all checks passing)
 
 ARCHITECTURE CONTEXT GUIDANCE
 
@@ -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"
 )
 ```
 
@@ -615,7 +615,7 @@ Response:
 
 **WHEN TO USE MULTI-EXPERT ORCHESTRATION**:
 
-For complex cross-domain tasks, use `/agileflow:multi-expert` instead of single agent:
+For complex cross-domain tasks, use `/agileflow-multi-expert` instead of single agent:
 
 | Scenario | Use Multi-Expert |
 |----------|------------------|
@@ -634,7 +634,7 @@ For complex cross-domain tasks, use `/agileflow:multi-expert` instead of single
 
 **How to invoke**:
 ```
-SlashCommand("/agileflow:multi-expert <question>")
+SlashCommand("/agileflow-multi-expert <question>")
 ```
 
 Or spawn directly:
@@ -729,7 +729,7 @@ CI INTEGRATION
 - On request, run tests/build/lint and summarize.
 
 IMPLEMENTATION FLOW
-1) Validate story readiness: `/agileflow:story-validate <STORY_ID>`
+1) Validate story readiness: `/agileflow-story-validate <STORY_ID>`
 2) Read relevant practices docs based on task type
 3) Read story's Architecture Context section FIRST
 4) Check Previous Story Insights (if not first in epic)

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/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.
 
@@ -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/readme-sync.md

@@ -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/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;