agileflow 2.94.1 → 2.95.1

package/src/core/commands/choose.md

@@ -343,6 +343,83 @@ Use `/agileflow:choose` for decisions that:
 
 ---
 
+## Expected Output
+
+### Success - Decision Analysis
+
+```
+🤔 Decision Analysis: Database Selection
+══════════════════════════════════════════════════════════════
+
+Context: New microservice needs persistent storage for user data
+
+📊 Options Evaluated:
+
+┌─────────────────────────────────────────────────────────────┐
+│ Option A: PostgreSQL                                        │
+├─────────────────────────────────────────────────────────────┤
+│ ✅ Pros:                                                    │
+│    - ACID compliance                                        │
+│    - Rich query capabilities                                │
+│    - Team expertise exists                                  │
+│ ❌ Cons:                                                    │
+│    - Scaling complexity                                     │
+│    - Higher operational overhead                            │
+│ Score: 8/10                                                 │
+└─────────────────────────────────────────────────────────────┘
+
+┌─────────────────────────────────────────────────────────────┐
+│ Option B: MongoDB                                           │
+├─────────────────────────────────────────────────────────────┤
+│ ✅ Pros:                                                    │
+│    - Flexible schema                                        │
+│    - Horizontal scaling                                     │
+│ ❌ Cons:                                                    │
+│    - No ACID by default                                     │
+│    - Learning curve                                         │
+│ Score: 6/10                                                 │
+└─────────────────────────────────────────────────────────────┘
+
+🎯 Recommendation: PostgreSQL
+
+Rationale: Given team expertise and ACID requirements,
+PostgreSQL provides better fit despite scaling concerns.
+
+Document this decision?
+→ /agileflow:adr TITLE="Database Selection for User Service"
+```
+
+### Success - Quick Choice
+
+```
+🤔 Quick Choice: Testing Framework
+
+Options: Jest vs Vitest vs Mocha
+
+✅ Recommended: Jest
+- Industry standard
+- Great TypeScript support
+- Existing config in project
+
+Accept recommendation? [Y/n]
+```
+
+### Error - Insufficient Context
+
+```
+❌ Error: Cannot make recommendation without context
+
+Please provide:
+- QUESTION: What decision needs to be made?
+- OPTIONS: At least 2 alternatives
+- CONTEXT: Relevant constraints and requirements
+
+Example:
+/agileflow:choose QUESTION="Which CI provider?" OPTIONS="GitHub Actions, CircleCI, Jenkins"
+```
+
+---
+
 ## Related Commands
 
 - `/agileflow:adr` - Create Architecture Decision Records

package/src/core/commands/ci.md

@@ -243,6 +243,83 @@ Diff-first; YES/NO.
 
 ---
 
+## Expected Output
+
+### Success - CI Workflow Created
+
+```
+🔧 CI/CD Setup
+══════════════════════════════════════════════════════════════
+
+Creating workflow configuration...
+
+✓ Created .github/workflows/ci.yml
+  - lint: ESLint + Prettier check
+  - typecheck: TypeScript compilation
+  - test: Jest with coverage
+  - Concurrency: cancel-in-progress enabled
+
+✓ Created CODEOWNERS
+  /src/  @team-lead @senior-dev
+  /docs/03-decisions/  @tech-lead
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ CI/CD Setup Complete
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Next steps:
+1. Push workflow: git add . && git push
+2. Enable branch protection in GitHub settings
+3. Set required checks: lint, typecheck, test
+
+View workflow: .github/workflows/ci.yml
+```
+
+### Success - Workflow Updated
+
+```
+🔧 CI/CD Update
+══════════════════════════════════════════════════════════════
+
+Existing workflow detected. Updating...
+
+Changes:
++ Added code coverage threshold (80%)
++ Added security audit job
+~ Updated Node.js version to 20
+
+✓ Updated .github/workflows/ci.yml
+
+Review changes before committing:
+  git diff .github/workflows/ci.yml
+```
+
+### Error - Missing OWNERS
+
+```
+❌ Error: OWNERS parameter required
+
+Specify code owners for CODEOWNERS file:
+
+/agileflow:ci OWNERS="@username1, @username2"
+
+These users will be required reviewers for PR changes.
+```
+
+### Error - Invalid Workflow
+
+```
+❌ Error: Invalid workflow configuration
+
+.github/workflows/ci.yml has syntax errors:
+  Line 15: Invalid job name 'test!'
+  Line 23: Missing 'runs-on' field
+
+Fix errors or run with FORCE=true to overwrite.
+```
+
+---
+
 ## Related Commands
 
 - `/agileflow:configure` - Manage AgileFlow features and hooks

package/src/core/commands/compress.md

@@ -251,7 +251,9 @@ bash .agileflow/scripts/compress-status.sh
 - `/agileflow:status` - View current story statuses
 - `/agileflow:validate` - Validate AgileFlow system health
 
-## Example Output
+## Expected Output
+
+### Success - Compression Complete
 
 ```
 🗜️  AgileFlow Status Compression
@@ -298,6 +300,30 @@ bash .agileflow/scripts/compress-status.sh
 💾 To restore original: cp docs/09-agents/status.json.backup docs/09-agents/status.json
 ```
 
+### Error - File Not Found
+
+```
+❌ Error: status.json not found
+
+Expected location: docs/09-agents/status.json
+
+Run /agileflow:setup to initialize AgileFlow structure.
+```
+
+### Error - Invalid JSON
+
+```
+❌ Error: Invalid JSON in status.json
+
+Parse error at line 42: Unexpected token
+
+Fix the JSON syntax error and try again.
+Backup your current file first:
+  cp docs/09-agents/status.json docs/09-agents/status.json.broken
+```
+
+---
+
 ## Technical Notes
 
 **Token Estimation**:

package/src/core/commands/configure.md

@@ -177,18 +177,43 @@ After handling issues (or if none), present the main category menu:
     {"label": "Full (Recommended)", "description": "All features: hooks, archival, status line, AskUserQuestion, TmuxAutoSpawn"},
     {"label": "Basic", "description": "SessionStart + PreCompact + Archival + AskUserQuestion + TmuxAutoSpawn"},
     {"label": "Minimal", "description": "SessionStart + Archival only"},
-    {"label": "None", "description": "Disable all AgileFlow features"}
+    {"label": "Experimental ⚠️", "description": "All features + full file injection during compact (CONTEXT HEAVY)"}
   ]
 }]</parameter>
 </invoke>
 ```
 
+**Note:** If user needs "None" (disable all), show as second page or via "Other" option.
+
 Then run:
 - "Full" → `node .agileflow/scripts/agileflow-configure.js --profile=full`
 - "Basic" → `node .agileflow/scripts/agileflow-configure.js --profile=basic`
 - "Minimal" → `node .agileflow/scripts/agileflow-configure.js --profile=minimal`
+- "Experimental" → `node .agileflow/scripts/agileflow-configure.js --profile=experimental`
 - "None" → `node .agileflow/scripts/agileflow-configure.js --profile=none`
 
+### Experimental Profile Details
+
+The **Experimental** profile enables all features like "Full", but changes how context is preserved during conversation compaction:
+
+| Aspect | Full Profile | Experimental Profile |
+|--------|--------------|---------------------|
+| Features | All enabled | All enabled |
+| PreCompact behavior | Extracts `COMPACT_SUMMARY` sections | Injects **entire command files** |
+| Context usage | ~200-500 tokens per command | ~2000-5000 tokens per command |
+| Reliability | Good for most cases | May improve instruction adherence |
+
+**When to use Experimental:**
+- Commands aren't being followed well after compaction
+- You have plenty of context budget
+- Working on long sessions with complex commands (babysit, mentor)
+
+**Trade-offs:**
+- ⚠️ Uses significantly more context tokens
+- ⚠️ May hit context limits faster
+- ✅ Full command instructions preserved
+- ✅ No loss of nuance from summarization
+
 #### If "Apply custom profile" selected
 
 First, check if custom profiles exist:
@@ -305,20 +330,37 @@ First, ask about hooks:
 </invoke>
 ```
 
-Then ask about other features:
+Then ask about other features (page 1):
 
 ```xml
 <invoke name="AskUserQuestion">
 <parameter name="questions">[{
-  "question": "Which other features?",
+  "question": "Which other features? (Page 1/2)",
   "header": "Features",
   "multiSelect": true,
   "options": [
     {"label": "Archival", "description": "Auto-archive completed stories older than threshold"},
     {"label": "Status Line", "description": "Custom status bar showing story/epic info"},
     {"label": "Auto-Update", "description": "Automatically update AgileFlow on session start"},
+    {"label": "More options...", "description": "View additional features"}
+  ]
+}]</parameter>
+</invoke>
+```
+
+If "More options..." selected, show page 2:
+
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "Which other features? (Page 2/2)",
+  "header": "Features",
+  "multiSelect": true,
+  "options": [
     {"label": "AskUserQuestion Mode", "description": "End responses with guided options"},
-    {"label": "Tmux Auto-Spawn", "description": "Auto-start Claude in tmux session when using af/agileflow wrapper"}
+    {"label": "Tmux Auto-Spawn", "description": "Auto-start Claude in tmux session when using af/agileflow"},
+    {"label": "Shell Aliases", "description": "Add af/agileflow commands to ~/.bashrc and ~/.zshrc"},
+    {"label": "CLAUDE.md Rules", "description": "Add /babysit context preservation rules to CLAUDE.md"}
   ]
 }]</parameter>
 </invoke>
@@ -334,6 +376,8 @@ Map selections to commands:
 - Auto-Update → `autoupdate`
 - AskUserQuestion Mode → `askuserquestion`
 - Tmux Auto-Spawn → `tmuxautospawn`
+- Shell Aliases → `shellaliases`
+- CLAUDE.md Rules → `claudemdreinforcement`
 
 Then run:
 ```bash
@@ -490,12 +534,20 @@ If no new options: "✅ All configuration options are up to date!"
 
 ## Profile Details
 
-| Profile | SessionStart | PreCompact | RalphLoop | SelfImprove | Archival | StatusLine | AskUserQuestion |
-|---------|-------------|------------|-----------|-------------|----------|------------|-----------------|
-| `full` | ✅ | ✅ | ✅ | ✅ | ✅ 30 days | ✅ | ✅ |
-| `basic` | ✅ | ✅ | ❌ | ❌ | ✅ 30 days | ❌ | ✅ |
-| `minimal` | ✅ | ❌ | ❌ | ❌ | ✅ 30 days | ❌ | ❌ |
-| `none` | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |
+| Profile | SessionStart | PreCompact | RalphLoop | SelfImprove | Archival | StatusLine | AskUserQuestion | Full File Injection |
+|---------|-------------|------------|-----------|-------------|----------|------------|-----------------|---------------------|
+| `full` | ✅ | ✅ | ✅ | ✅ | ✅ 30 days | ✅ | ✅ | ❌ |
+| `basic` | ✅ | ✅ | ❌ | ❌ | ✅ 30 days | ❌ | ✅ | ❌ |
+| `minimal` | ✅ | ❌ | ❌ | ❌ | ✅ 30 days | ❌ | ❌ | ❌ |
+| `experimental` | ✅ | ✅ | ✅ | ✅ | ✅ 30 days | ✅ | ✅ | ⚠️ **YES** |
+| `none` | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ | ❌ |
+
+**⚠️ Experimental Profile Warning:**
+The `experimental` profile enables **Full File Injection** during context compaction. Instead of injecting compact summaries (~200-500 tokens), it injects the **entire command file** (~2000-5000+ tokens per command). This is very context-heavy but may improve instruction adherence for complex commands like `/babysit`.
+
+**Note:** Shell Aliases and CLAUDE.md Rules are **not** included in any profile. These are per-user preferences that must be explicitly enabled:
+- `--enable=shellaliases` - Adds `af` and `agileflow` commands to ~/.bashrc and ~/.zshrc
+- `--enable=claudemdreinforcement` - Adds /babysit context preservation rules to CLAUDE.md
 
 ## CLI Commands Reference
 
@@ -504,6 +556,7 @@ If no new options: "✅ All configuration options are up to date!"
 node .agileflow/scripts/agileflow-configure.js --profile=full
 node .agileflow/scripts/agileflow-configure.js --profile=basic
 node .agileflow/scripts/agileflow-configure.js --profile=minimal
+node .agileflow/scripts/agileflow-configure.js --profile=experimental
 node .agileflow/scripts/agileflow-configure.js --profile=none
 
 # Custom Profiles
@@ -521,6 +574,8 @@ node .agileflow/scripts/agileflow-configure.js --import-profile=my-setup.json
 node .agileflow/scripts/agileflow-configure.js --enable=sessionstart,precompact
 node .agileflow/scripts/agileflow-configure.js --disable=statusline
 node .agileflow/scripts/agileflow-configure.js --enable=archival --archival-days=14
+node .agileflow/scripts/agileflow-configure.js --enable=shellaliases
+node .agileflow/scripts/agileflow-configure.js --enable=claudemdreinforcement
 
 # Maintenance
 node .agileflow/scripts/agileflow-configure.js --detect
@@ -897,6 +952,67 @@ Repaired: 1, Errors: 0, Skipped: 18
 
 ---
 
+## Expected Output
+
+### Success - Feature Enabled
+
+```
+🔧 AgileFlow Configuration
+══════════════════════════════════════════════════════════════
+
+Enabling feature: damage-control
+
+✓ Created .claude/hooks/PreToolUse/damage-control-bash.js
+✓ Created .claude/hooks/PreToolUse/damage-control-edit.js
+✓ Created .claude/hooks/patterns.yaml
+✓ Updated settings.json
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ damage-control enabled
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+31 protection patterns active.
+Test: Try running a blocked command to verify.
+```
+
+### Success - List Features
+
+```
+🔧 AgileFlow Configuration
+══════════════════════════════════════════════════════════════
+
+Installed Features:
+✅ damage-control (v2.94.1) - 31 patterns
+✅ precompact (v2.94.1) - context preservation
+✅ status-line (v2.94.1) - story tracking
+⚪ visual-e2e (not installed)
+⚪ hooks (not installed)
+
+Scripts:
+✅ obtain-context.js (v2.94.1)
+✅ archive-completed-stories.sh (v2.94.1)
+
+Run /agileflow:configure FEATURE=<name> to install features.
+```
+
+### Error - Unknown Feature
+
+```
+❌ Error: Unknown feature: super-ai
+
+Available features:
+- damage-control: Protect against destructive commands
+- precompact: Context preservation during compaction
+- status-line: Story status in Claude Code UI
+- visual-e2e: Screenshot-based testing
+- hooks: Event-driven automation
+- ci: CI/CD workflow setup
+
+Usage: /agileflow:configure FEATURE=damage-control
+```
+
+---
+
 ## Related Commands
 
 - `/agileflow:ci` - Bootstrap CI/CD workflow

package/src/core/commands/council.md

@@ -515,3 +515,77 @@ Final: Synthesized recommendation with confidence
 ```
 
 The council evaluates from three angles to provide balanced guidance.
+
+---
+
+## Expected Output
+
+### Success - Council Decision
+
+```
+🏛️ AI Council Convened
+══════════════════════════════════════════════════════════════
+Question: Should we migrate to microservices?
+Mode: standard (3 perspectives)
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+🌟 OPTIMIST PERSPECTIVE
+Microservices offer significant benefits:
+- Independent scaling per service
+- Technology flexibility
+- Team autonomy and faster releases
+Recommendation: Proceed with migration
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+😈 ADVOCATE PERSPECTIVE
+Critical concerns to address:
+- Distributed systems complexity
+- Network latency overhead
+- Operational burden (monitoring, debugging)
+- Team may lack experience
+Recommendation: Caution - validate team readiness
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+⚖️ ANALYST SYNTHESIS
+Balanced assessment:
+- Current monolith pain points are real
+- Full migration is high-risk
+- Incremental approach reduces risk
+
+Recommendation: Start with one bounded context
+Confidence: 75%
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+🎯 COUNCIL VERDICT: Proceed with caution
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Document decision? /agileflow:adr TITLE="Microservices Migration"
+```
+
+### Success - Debate Mode
+
+```
+🏛️ AI Council Debate (Round 2 of 2)
+══════════════════════════════════════════════════════════════
+
+[Optimist responds to Advocate's concerns...]
+[Advocate counters with specific risks...]
+[Analyst synthesizes final position...]
+
+Final Verdict: GraphQL for internal APIs, REST for public
+Confidence: 85%
+```
+
+### Error - Question Too Vague
+
+```
+❌ Error: Question too vague for meaningful analysis
+
+"Should we do it?" - What is "it"?
+
+Please provide specific context:
+/agileflow:council "Should we use Redis or Memcached for session caching given our 10k DAU scale?"
+```

package/src/core/commands/debt.md

@@ -400,6 +400,78 @@ OUTPUT
 
 ---
 
+## Expected Output
+
+### Success - Debt Report
+
+```
+📊 Technical Debt Analysis
+══════════════════════════════════════════════════════════════
+Scan date: 2026-01-29
+Files analyzed: 127
+
+🔴 HIGH PRIORITY (3)
+┌──────────────────────────────────────────────────────────────┐
+│ 1. Legacy auth module (src/auth/legacy.js)                   │
+│    Impact: Security risk, blocks OAuth work                  │
+│    Effort: 3 days                                            │
+│    ROI: High (unblocks US-0053, US-0054)                     │
+├──────────────────────────────────────────────────────────────┤
+│ 2. Untyped API responses                                     │
+│    Impact: Runtime errors, poor DX                           │
+│    Effort: 2 days                                            │
+│    ROI: High (prevents bugs)                                 │
+├──────────────────────────────────────────────────────────────┤
+│ 3. Test coverage gap in /api/orders                          │
+│    Impact: 23% coverage vs 80% target                        │
+│    Effort: 1 day                                             │
+│    ROI: Medium (risk reduction)                              │
+└──────────────────────────────────────────────────────────────┘
+
+🟡 MEDIUM PRIORITY (5)
+- Deprecated dependencies (lodash 3.x)
+- Console.log statements in production
+- Missing error boundaries
+- Hardcoded configuration
+- Duplicate validation logic
+
+📈 Trend: +2 items since last scan (2026-01-22)
+
+Create stories for high-priority items? [Y/n]
+```
+
+### Success - Debt Reduced
+
+```
+📊 Technical Debt Update
+══════════════════════════════════════════════════════════════
+
+✓ Resolved: Legacy auth module
+✓ Resolved: Test coverage gap
+
+Debt Score: 15 → 9 (-40%)
+Sprint Impact: Unblocked 2 stories
+
+🎉 Great progress on debt reduction!
+```
+
+### Error - No Analysis Available
+
+```
+⚠️ No technical debt analysis found
+
+Run initial scan first:
+/agileflow:debt SCAN=true
+
+This will analyze:
+- Code complexity
+- Test coverage
+- Dependency freshness
+- Security vulnerabilities
+```
+
+---
+
 ## Related Commands
 
 - `/agileflow:diagnose` - System health diagnostics

package/src/core/commands/deploy.md

@@ -781,6 +781,79 @@ OUTPUT
 
 ---
 
+## Expected Output
+
+### Success - Deployment Configured
+
+```
+🚀 Deployment Setup
+══════════════════════════════════════════════════════════════
+
+Analyzing project...
+✓ Detected: Next.js application
+✓ Package manager: npm
+✓ Build command: npm run build
+✓ Output: .next/
+
+Platform Recommendation: Vercel (optimal for Next.js)
+
+Creating configuration...
+✓ Created vercel.json
+✓ Created .github/workflows/deploy.yml
+✓ Updated package.json scripts
+
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✅ Deployment Setup Complete
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Next steps:
+1. Connect GitHub repo to Vercel dashboard
+2. Set environment variables in Vercel
+3. Push to trigger first deployment
+
+Environments:
+- Preview: Automatic on PR
+- Production: On merge to main
+
+Rollback: vercel rollback <deployment-id>
+```
+
+### Success - Multi-Environment
+
+```
+🚀 Deployment Setup (Multi-Environment)
+══════════════════════════════════════════════════════════════
+
+Environments configured:
+┌─────────────┬─────────────────────┬──────────────────┐
+│ Environment │ URL                 │ Trigger          │
+├─────────────┼─────────────────────┼──────────────────┤
+│ Development │ dev.example.com     │ Push to dev/*    │
+│ Staging     │ staging.example.com │ Push to staging  │
+│ Production  │ example.com         │ Push to main     │
+└─────────────┴─────────────────────┴──────────────────┘
+
+✓ All environments configured
+```
+
+### Error - Unsupported Project
+
+```
+❌ Error: Could not detect project type
+
+No supported framework found. Supported:
+- Next.js
+- Remix
+- Vite
+- Create React App
+- Node.js API
+
+Specify manually:
+/agileflow:deploy TYPE=nodejs PLATFORM=railway
+```
+
+---
+
 ## Related Commands
 
 - `/agileflow:configure` - Manage AgileFlow features and hooks