AgileFlow

/configure

PreviousNext

Configure AgileFlow features with hierarchical menus, profiles, and hooks

/configure

Manage AgileFlow features with preset profiles, enable/disable individual options, and configure project infrastructure with interactive hierarchical menus.

Quick Start

/agileflow:configure

This opens an interactive configuration menu with 5 main categories: Profiles, Features, Sessions, Infrastructure, and Maintenance.

You can also run with specific options:

/agileflow:configure --profile=full
/agileflow:configure --enable=sessionstart,precompact
/agileflow:configure --detect

Workflow

The configure command follows this workflow:

  1. Detect - Check current configuration status and any issues
  2. Handle Issues - If format problems detected, offer migration
  3. Main Menu - Choose from 5 categories (max 4 options per menu)
  4. Sub-Menu - Select specific feature or configuration
  5. Apply - Changes are applied and tracked

Parameters

ParameterDescription
--detectCheck current configuration status (run this first)
--profile=<name>Apply preset profile: full, basic, minimal, experimental, or none
--enable=<features>Comma-separated features to enable
--disable=<features>Comma-separated features to disable
--migrateFix format issues in existing configuration
--upgradeUpdate scripts to latest AgileFlow version
--repairRestore accidentally deleted scripts
--list-profilesList all saved custom profiles
--save-profile=<name>Save current settings as reusable profile
--archival-days=<N>Days before archiving completed stories (default: 7)

Configuration Profiles

Choose a preset profile or create custom ones:

ProfileSessionStartPreCompactRalphLoopSelfImproveArchivalStatusLineFull Injection
full
basic
minimal
experimental⚠️ YES
none

Experimental Profile: Enables all features like full, but injects entire command files during context compaction (~2000-5000 tokens) instead of compact summaries (~200-500 tokens). Use when commands aren't being followed well after compaction, or if you have plenty of context budget.

Available Features

Hooks (Event-Driven Automation)

  • SessionStart: Display project info and context on session start
  • PreCompact: Preserve important context when conversation compacts
  • RalphLoop: Stop hook - run tests automatically, loop until epic complete
  • SelfImprove: Stop hook - auto-update agent expertise from your work

Other Features

  • Archival: Auto-archive completed stories older than threshold (default: 7 days)
  • StatusLine: Custom Claude Code status bar showing current story and progress
  • AskUserQuestion: End all commands with guided options instead of text questions
  • Tmux Auto-Spawn: Auto-start Claude in tmux session with af / agileflow commands
  • Shell Aliases: Add af and agileflow commands to ~/.bashrc and ~/.zshrc
  • Auto-Update: Automatically update AgileFlow when new version available
  • CLAUDE.md Rules: Add /babysit context preservation rules to CLAUDE.md

Preset Profiles

Quick Setup

Apply a preset profile with one command:

# Full - all features enabled (Recommended)
/agileflow:configure --profile=full
 
# Basic - core hooks + archival
/agileflow:configure --profile=basic
 
# Minimal - just welcome message and archival
/agileflow:configure --profile=minimal
 
# Experimental - all features + full command file injection
/agileflow:configure --profile=experimental
 
# None - disable all features
/agileflow:configure --profile=none

Custom Profiles

Save your current settings as a reusable profile:

# Save current setup
/agileflow:configure --save-profile=my-backend-setup --description="Backend dev setup"
 
# Apply custom profile
/agileflow:configure --profile=my-backend-setup
 
# List all custom profiles
/agileflow:configure --list-profiles --verbose
 
# Export profile to share
/agileflow:configure --export-profile=my-backend-setup --output=profile.json
 
# Import profile from file
/agileflow:configure --import-profile=profile.json

Interactive Menu System

Run without parameters to open the interactive menu:

/agileflow:configure

The menu has 5 main categories with hierarchical sub-menus (max 4 options per level):

  1. Profiles - Apply preset, apply custom, save current, manage
  2. Features - Enable/disable hooks and other features
  3. Sessions - Configure default startup mode for new sessions
  4. Infrastructure - Set up Visual E2E, Damage Control, CI/CD, quality gates
  5. Maintenance - Fix format issues, upgrade scripts, repair missing files

Maintenance Commands

Check Status (Always Run First)

/agileflow:configure --detect

Shows current configuration, installed version, and any issues (format problems, outdated scripts).

Fix Format Issues

/agileflow:configure --migrate

Automatically converts old configuration formats to new Claude Code format. Creates backup at .claude/settings.json.backup.

Update Scripts

/agileflow:configure --upgrade

Re-deploy all enabled features with latest AgileFlow version scripts.

Repair Missing Scripts

/agileflow:configure --repair

Restore accidentally deleted scripts. Use after accidental deletions or corrupted installations.

List Installed Scripts

/agileflow:configure --list-scripts

Shows all scripts with status: present, modified, or missing.

Examples

Enable Specific Features

/agileflow:configure --enable=sessionstart,precompact,archival

Disable Feature

/agileflow:configure --disable=statusline

Custom Archival Threshold

/agileflow:configure --enable=archival --archival-days=14

Archive completed stories after 14 days instead of the default 7 days.

Add Shell Aliases

/agileflow:configure --enable=shellaliases

Adds af and agileflow commands to ~/.bashrc and ~/.zshrc for faster access.

Troubleshoot Configuration

# 1. Check current status
/agileflow:configure --detect
 
# 2. If issues found, migrate
/agileflow:configure --migrate
 
# 3. List all scripts
/agileflow:configure --list-scripts
 
# 4. Repair if needed
/agileflow:configure --repair
 
# 5. Open menu for manual config
/agileflow:configure

Hooks System

Each hook automates specific events in your development workflow:

HookTriggerWhat It Does
SessionStartSession beginsDisplay project status, recent commits, active stories
PreCompactConversation compactsPreserve important context, rules, current state
RalphLoopClaude stops (Stop hook)Run tests → if pass, mark story done & load next; if fail, show errors
SelfImproveClaude stops (Stop hook)Analyze git changes, detect domain, update agent expertise

Storage Locations

Configuration is tracked in two files:

  1. .claude/settings.json - Hooks and features in Claude Code format

    • SessionStart hook
    • PreCompact hook
    • Other feature configuration
  2. docs/00-meta/agileflow-metadata.json - Project-level metadata

    • Feature versions and timestamps
    • Archival settings (enabled, threshold_days)
    • Custom profiles
    • Quality gate configuration

Output After Configuration

✅ Configuration Complete!
 
Enabled:
  ✅ sessionstart (v2.94.1)
  ✅ precompact (v2.94.1)
  ✅ archival (v2.94.1)
 
Disabled:
  ❌ statusline
 
═══════════════════════════════════════════════════════
🔴 RESTART CLAUDE CODE NOW!
   Quit completely, wait 5 seconds, restart
═══════════════════════════════════════════════════════

Important: You must completely quit and restart Claude Code for changes to take effect.

Troubleshooting

Format Issues Detected

If you see ⚠️ INVALID FORMAT warnings:

/agileflow:configure --migrate

Automatically fixes format issues and creates backup at .claude/settings.json.backup.

Outdated Scripts

If you see 🔄 OUTDATED warnings:

/agileflow:configure --upgrade

Re-deploys all enabled features with latest versions.

Missing Scripts

If scripts are accidentally deleted:

/agileflow:configure --repair

Restores all missing scripts. Use --repair=<feature> to repair specific feature only.

Best Practices

  1. Always run --detect first - See current state before making changes
  2. Use profiles for team setup - Save and share custom profiles with teammates
  3. Enable incrementally - Start with basic profile, add features as needed
  4. Backup before major changes - Migration automatically creates backups
  5. Restart after changes - Don't skip the restart step, it's critical