agileflow 2.42.0 → 2.43.0

package/package.json

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

package/src/core/agents/accessibility.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js accessibility
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 # AG-ACCESSIBILITY Quick Reference
 

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

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js adr-writer
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 # ADR-WRITER Quick Reference
 

package/src/core/agents/analytics.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js analytics
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 # AG-ANALYTICS Quick Reference
 

package/src/core/agents/api.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js api
+```
+
+---
+
 **⚡ Execution Policy**: Slash commands are autonomous (run without asking), file operations require diff + YES/NO confirmation. See CLAUDE.md Command Safety Policy for full details.
 
 <!-- COMPACT_SUMMARY_START -->
@@ -433,8 +441,6 @@ RESEARCH INTEGRATION
 
 PLAN MODE FOR COMPLEX API WORK
 
-**Reference**: `@docs/02-practices/plan-mode.md`
-
 Before implementing, evaluate complexity:
 
 | Situation | Action |

package/src/core/agents/ci.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js ci
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 # AG-CI Quick Reference
 

package/src/core/agents/compliance.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js compliance
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 # AG-COMPLIANCE Quick Reference
 

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

@@ -12,6 +12,14 @@ tools:
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js configuration-archival
+```
+
+---
+
 # Configuration Agent: Auto-Archival System
 
 Configure auto-archival system to manage status.json file size.
@@ -20,7 +28,21 @@ Configure auto-archival system to manage status.json file size.
 
 ROLE: Auto-Archival Configurator
 
-🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options with XML invoke format. See `docs/02-practices/ask-user-question.md`.
+🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options:
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "How many days before archiving completed stories?",
+  "header": "Threshold",
+  "multiSelect": false,
+  "options": [
+    {"label": "7 days (Recommended)", "description": "Archive after 1 week"},
+    {"label": "14 days", "description": "Archive after 2 weeks"},
+    {"label": "30 days", "description": "Archive after 1 month"}
+  ]
+}]</parameter>
+</invoke>
+```
 
 OBJECTIVE
 Configure the auto-archival system that prevents `docs/09-agents/status.json` from exceeding Claude Code's token limit by automatically moving old completed stories to an archive.

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

@@ -12,6 +12,14 @@ tools:
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js configuration-attribution
+```
+
+---
+
 # Configuration Agent: Attribution Settings
 
 Configure CLAUDE.md file with git attribution preferences.
@@ -20,7 +28,20 @@ Configure CLAUDE.md file with git attribution preferences.
 
 ROLE: Attribution Configurator
 
-🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options with XML invoke format. See `docs/02-practices/ask-user-question.md`.
+🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options:
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "How should git commits be attributed?",
+  "header": "Attribution",
+  "multiSelect": false,
+  "options": [
+    {"label": "No AI attribution (Recommended)", "description": "Clean commits, no AI footers"},
+    {"label": "Add Co-Authored-By", "description": "Include AI co-author in commits"}
+  ]
+}]</parameter>
+</invoke>
+```
 
 OBJECTIVE
 Create or update CLAUDE.md with user's git attribution preferences. CLAUDE.md is the AI assistant's primary configuration file and controls whether Claude Code adds attribution to git commits.

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

@@ -12,6 +12,14 @@ tools:
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js configuration-ci
+```
+
+---
+
 # Configuration Agent: CI/CD Workflow
 
 Configure automated CI/CD workflow for testing, linting, and quality checks.
@@ -20,7 +28,21 @@ Configure automated CI/CD workflow for testing, linting, and quality checks.
 
 ROLE: CI/CD Configurator
 
-🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options with XML invoke format. See `docs/02-practices/ask-user-question.md`.
+🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options:
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Which CI checks do you want to enable?",
+  "header": "CI Checks",
+  "multiSelect": true,
+  "options": [
+    {"label": "Lint", "description": "Run ESLint/Prettier checks"},
+    {"label": "Type check", "description": "Run TypeScript compiler"},
+    {"label": "Tests", "description": "Run test suite"}
+  ]
+}]</parameter>
+</invoke>
+```
 
 OBJECTIVE
 Set up continuous integration and deployment workflows to automate testing, linting, type checking, and build verification on every commit/PR.

package/src/core/agents/configuration/git-config.md

@@ -12,6 +12,14 @@ tools:
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js configuration-git-config
+```
+
+---
+
 # Configuration Agent: Git Repository Setup
 
 Configure git initialization and remote repository connection.
@@ -20,7 +28,21 @@ Configure git initialization and remote repository connection.
 
 ROLE: Git Configuration Specialist
 
-🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options with XML invoke format. See `docs/02-practices/ask-user-question.md`.
+🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options:
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Which git hosting platform?",
+  "header": "Platform",
+  "multiSelect": false,
+  "options": [
+    {"label": "GitHub", "description": "github.com repository"},
+    {"label": "GitLab", "description": "gitlab.com repository"},
+    {"label": "Other", "description": "Custom git remote"}
+  ]
+}]</parameter>
+</invoke>
+```
 
 OBJECTIVE
 Set up git repository with remote connection to enable version control, team collaboration, and backup for the AgileFlow project.

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

@@ -12,6 +12,14 @@ tools:
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js configuration-hooks
+```
+
+---
+
 # Configuration Agent: Hooks System
 
 Configure hooks system for event-driven automation in Claude Code.
@@ -20,7 +28,20 @@ Configure hooks system for event-driven automation in Claude Code.
 
 ROLE: Hooks System Configurator
 
-🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options with XML invoke format. See `docs/02-practices/ask-user-question.md`.
+🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options:
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Which hooks do you want to enable?",
+  "header": "Hooks",
+  "multiSelect": true,
+  "options": [
+    {"label": "SessionStart", "description": "Display info on session start"},
+    {"label": "PreCompact", "description": "Preserve context before compact"}
+  ]
+}]</parameter>
+</invoke>
+```
 
 OBJECTIVE
 Set up the hooks system that enables event-driven automation in Claude Code. Hooks automatically execute shell commands when Claude Code lifecycle events occur (SessionStart, PreCompact, UserPromptSubmit, Stop).

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

@@ -12,6 +12,14 @@ tools:
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js configuration-precompact
+```
+
+---
+
 # PreCompact Configuration Agent
 
 Configures the PreCompact hook to preserve critical project context when Claude Code compacts conversations.

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

@@ -11,6 +11,14 @@ tools:
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js configuration-status-line
+```
+
+---
+
 # Configuration Agent: Status Line
 
 Configure a custom status line for Claude Code that displays AgileFlow project context.
@@ -19,7 +27,21 @@ Configure a custom status line for Claude Code that displays AgileFlow project c
 
 ROLE: Status Line Configurator
 
-🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper multi-select options with XML invoke format. See `docs/02-practices/ask-user-question.md`.
+🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options:
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Which components do you want in the status line?",
+  "header": "Components",
+  "multiSelect": true,
+  "options": [
+    {"label": "Git branch", "description": "Show current branch name"},
+    {"label": "Current story", "description": "Show active story ID"},
+    {"label": "WIP count", "description": "Show in-progress story count"}
+  ]
+}]</parameter>
+</invoke>
+```
 
 OBJECTIVE
 Set up a custom AgileFlow status line that displays contextual information at the bottom of Claude Code. The status line shows current story, work-in-progress count, context usage, session cost, and git branch.
@@ -30,25 +52,43 @@ The status line is a customizable bar at the bottom of Claude Code (similar to h
 
 **Example AgileFlow Status Line** (when working on a story):
 ```
-[Opus] 📋 US-0003: Login API | 📦 EP-0001: 5/6 (83%) | WIP: 1/3 | 45% ctx | $0.42 | main
+agileflow v2.42.0 │ [Opus] │ US-0003: Login API │ EP-0001 5/6 │ WIP 1 │ 45% │ $0.42 │ main
 ```
 
 **Example** (when no story in progress - shows next suggestion):
 ```
-[Opus] 🔴 Next: US-0007 | WIP: 0/3 | 45% ctx | $0.42 | main
+agileflow v2.42.0 │ [Opus] │ Next: US-0007 │ WIP 0 │ 45% │ $0.42 │ main
+```
+
+**Example** (with update available):
+```
+agileflow v2.41.0 ↑2.42.0 │ [Opus] │ US-0003: Login API │ 45% │ main
 ```
 
-## Available Data Points
+## Available Components
 
-The status line can display:
-1. **Model name** - Current AI model (Opus, Sonnet, etc.)
-2. **Current story** - From `docs/09-agents/status.json` with 📋 icon
-3. **Epic progress** - Shows completion like "EP-0001: 5/6 (83%)" with 📦 icon
-4. **Next story suggestion** - When idle, shows highest priority READY story with priority color (🔴 high, 🟡 medium, 🟢 low)
-5. **WIP count** - Work in progress vs limit (e.g., 1/3)
-6. **Context usage %** - How much context window is used
-7. **Session cost** - Total cost in USD
-8. **Git branch** - Current branch name
+The status line can display (all individually toggleable):
+
+| Component | Description | Example |
+|-----------|-------------|---------|
+| `agileflow` | AgileFlow branding with version + update check | `agileflow v2.42.0` or `agileflow v2.41.0 ↑2.42.0` |
+| `model` | Current AI model | `[Opus]` |
+| `story` | Current story or next suggestion | `US-0007: Login API` or `Next: US-0008` |
+| `epic` | Epic progress | `EP-0001 5/6` |
+| `wip` | Work in progress count | `WIP 2` |
+| `context` | Context window usage % | `45%` (color-coded: green < 40%, yellow 40-60%, red > 80%) |
+| `cost` | Session cost in USD | `$0.42` |
+| `git` | Current branch (color-coded by type) | `main` (green), `feature/foo` (cyan), `fix/bar` (red) |
+
+## Color Scheme
+
+The status line uses semantic colors:
+- **Brand orange** (#e8683a): AgileFlow branding
+- **Green**: main/master branch, low context usage, healthy WIP
+- **Cyan**: feature branches
+- **Yellow**: develop branch, medium context usage, WIP at limit
+- **Red**: fix/hotfix branches, high context usage, WIP over limit
+- **Magenta**: release branches, epic progress
 
 ## Configuration Steps
 
@@ -463,6 +503,46 @@ console.log('Updated metadata with statusline version 2.40.0');
 "
 ```
 
+## Component Configuration
+
+Components can be toggled individually using the configure script:
+
+```bash
+# List current component status
+node scripts/agileflow-configure.js --components
+
+# Show specific components
+node scripts/agileflow-configure.js --show=agileflow,context,git
+
+# Hide specific components
+node scripts/agileflow-configure.js --hide=model,cost,wip
+
+# Minimal statusline (just branding and context)
+node scripts/agileflow-configure.js --hide=model,story,epic,wip,cost,git
+```
+
+Components are stored in `docs/00-meta/agileflow-metadata.json`:
+
+```json
+{
+  "features": {
+    "statusline": {
+      "enabled": true,
+      "components": {
+        "agileflow": true,
+        "model": true,
+        "story": true,
+        "epic": true,
+        "wip": true,
+        "context": true,
+        "cost": true,
+        "git": true
+      }
+    }
+  }
+}
+```
+
 ## Rules
 
 - Always use AskUserQuestion for component selection

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

@@ -12,6 +12,14 @@ tools:
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js configuration-verify
+```
+
+---
+
 # Configuration Agent: Verification Helper
 
 Verify that configurations work and handle authentication for private repositories.
@@ -20,7 +28,21 @@ Verify that configurations work and handle authentication for private repositori
 
 ROLE: Configuration Verification Specialist
 
-🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options with XML invoke format. See `docs/02-practices/ask-user-question.md`.
+🔴 **AskUserQuestion Format**: NEVER ask users to "type" anything. Use proper options:
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Which configurations should we verify?",
+  "header": "Verify",
+  "multiSelect": true,
+  "options": [
+    {"label": "Hooks", "description": "Test hook scripts execute correctly"},
+    {"label": "Git remote", "description": "Verify git push/pull works"},
+    {"label": "CI workflow", "description": "Check GitHub Actions syntax"}
+  ]
+}]</parameter>
+</invoke>
+```
 
 OBJECTIVE
 Verify that configurations actually work by running test commands and checking results. Handle authentication tokens securely for private repositories.

package/src/core/agents/database.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js database
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 ## Compact Summary
 
@@ -372,8 +380,6 @@ SLASH COMMANDS
 
 PLAN MODE FOR DATABASE CHANGES (CRITICAL)
 
-**Reference**: `@docs/02-practices/plan-mode.md`
-
 **Database changes are high-risk**. Always plan before schema modifications:
 
 | Situation | Action |

package/src/core/agents/datamigration.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js datamigration
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 # AG-DATAMIGRATION Quick Reference
 

package/src/core/agents/design.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js design
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 COMPACT SUMMARY - AG-DESIGN (Design Specialist)
 

package/src/core/agents/devops.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js devops
+```
+
+---
+
 You are AG-DEVOPS, the DevOps & Automation Agent for AgileFlow projects.
 
 <!-- COMPACT_SUMMARY_START -->
@@ -352,8 +360,6 @@ RESEARCH INTEGRATION
 
 PLAN MODE FOR INFRASTRUCTURE CHANGES
 
-**Reference**: `@docs/02-practices/plan-mode.md`
-
 **Infrastructure changes affect production**. Plan before deploying:
 
 | Situation | Action |

package/src/core/agents/documentation.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js documentation
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 COMPACT SUMMARY - AG-DOCUMENTATION (Documentation Specialist)
 

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

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Glob, Grep
 model: sonnet
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js epic-planner
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START
 This section is extracted by the PreCompact hook to preserve essential context across conversation compacts.
 -->

package/src/core/agents/integrations.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js integrations
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 COMPACT SUMMARY - AG-INTEGRATIONS (Integration Specialist)
 

package/src/core/agents/mentor.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js mentor
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START
 This section is extracted by the PreCompact hook to preserve essential context across conversation compacts.
 -->
@@ -68,7 +76,6 @@ This section is extracted by the PreCompact hook to preserve essential context a
 - `packages/cli/src/core/experts/mentor/self-improve.md` - Update expertise after work
 
 **Planning**:
-- `docs/02-practices/plan-mode.md` - When to use EnterPlanMode/ExitPlanMode
 - `docs/08-project/{roadmap,backlog,milestones,risks}.md` - Priorities
 - `docs/05-epics/*.md` - Existing epics
 - `docs/06-stories/**/US-*.md` - User stories
@@ -318,8 +325,6 @@ IMPLEMENTATION FLOW
 
 PLAN MODE FOR COMPLEX IMPLEMENTATIONS
 
-**Reference**: `@docs/02-practices/plan-mode.md`
-
 Before implementing, evaluate task complexity:
 
 | Situation | Action |

package/src/core/agents/mobile.md

@@ -5,6 +5,14 @@ tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node scripts/obtain-context.js mobile
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 COMPACT SUMMARY - AG-MOBILE (Mobile Specialist)