agileflow 2.51.0 → 2.56.0

package/src/core/commands/research.md

@@ -33,19 +33,66 @@ node .agileflow/scripts/obtain-context.js research
 ## Compact Summary
 - **Command**: /agileflow:research-init
 - **Purpose**: Initialize or save research notes with structured analysis
-- **Objective**: Evaluate and organize research findings
-- **TodoList**: Required for tracking 5-step workflow
-- **Key Actions**:
-  1. Ensure docs/10-research/ exists
-  2. Create/update docs/10-research/README.md (index table: Date | Topic | Path | Summary)
-  3. If pasted research content provided: save to docs/10-research/<YYYYMMDD>-<slug>.md
-  4. Add entry to README.md index table (newest first)
-  5. Show preview and wait for YES/NO confirmation
-- **File Format**: <YYYYMMDD>-<slug>.md (e.g., 20251222-session-tracking.md)
+- **Key Actions**: Ensure docs/10-research/ exists → Create/update index → Save research file → Add index entry → Confirm
+
+### Tool Usage Examples
+
+**TodoWrite** (to track research initialization workflow):
+```xml
+<invoke name="TodoWrite">
+<parameter name="content">1. Ensure docs/10-research/ exists
+2. Create/update docs/10-research/README.md (if missing)
+3. If pasted research content provided: save to docs/10-research/<YYYYMMDD>-<slug>.md
+4. Add entry to README.md index table
+5. Show preview and wait for YES/NO confirmation</parameter>
+<parameter name="status">in-progress</parameter>
+<parameter name="activeForm">1</parameter>
+</invoke>
+```
+
+**Write** (to create research file):
+```xml
+<invoke name="Write">
+<parameter name="file_path">/full/path/to/docs/10-research/20251222-session-tracking.md</parameter>
+<parameter name="content"># Session Tracking
+
+**Research Date**: 2025-12-22
+**Topic**: Session tracking implementation
+**Sources**: [source citations]
+
+## Summary
+[2-3 paragraph executive summary]
+
+## Key Findings
+- [Main point 1]
+- [Main point 2]
+
+## References
+- [Source 1]
+- [Source 2]</parameter>
+</invoke>
+```
+
+**Edit** (to update README.md index):
+```xml
+<invoke name="Edit">
+<parameter name="file_path">/full/path/to/docs/10-research/README.md</parameter>
+<parameter name="old_string">| 2025-12-20 | Old Topic | 20251220-old-topic.md | Summary |</parameter>
+<parameter name="new_string">| 2025-12-22 | Session Tracking | 20251222-session-tracking.md | Research findings about tracking sessions |
+| 2025-12-20 | Old Topic | 20251220-old-topic.md | Summary |</parameter>
+</invoke>
+```
+
+**AskUserQuestion** (for confirmation):
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{"question": "Save this research file?", "header": "Preview", "multiSelect": false, "options": [{"label": "Yes, save to docs/10-research/", "description": "Write the research file and update index"}, {"label": "No, abort", "description": "Cancel without saving"}]}]</parameter>
+</invoke>
+```
+
+- **File Format**: <YYYYMMDD>-<slug>.md
 - **Index Table**: Date | Topic | Path | Summary in README.md
-- **Output**: Research note saved to docs/10-research/ with index entry
 - **Workflow**: Diff-first, then YES/NO confirmation
-- **Related**: docs/10-research/ structure, research organization
 <!-- COMPACT_SUMMARY_END -->
 
 ---

package/src/core/commands/retro.md

@@ -24,70 +24,62 @@ Automated retrospective generator that analyzes patterns and surfaces insights f
 
 ## Compact Summary
 
-**Command Purpose**: Automated retrospective generator that analyzes AgileFlow project data to surface insights, patterns, and actionable improvements using the Start/Stop/Continue format.
+**Command Purpose**: Automated retrospective generator analyzing AgileFlow data to surface insights, patterns, and actionable improvements using Start/Stop/Continue format.
 
 **Role**: Retrospective Facilitator
 
 **Critical Behavioral Rules**:
-- ALWAYS create TodoWrite task list at the start (9 steps: load data, analyze wins, analyze improvements, detect patterns, generate actions, create celebration section, generate report, save file, update index)
+- ALWAYS create TodoWrite task list at start (9 steps)
 - Focus on TEAM-LEVEL patterns, never individual blame
-- Balance positive insights (Continue) with improvements (Start/Stop)
-- Use DATA to drive insights - no subjective opinions without evidence
+- Balance positive (Continue) with improvements (Start/Stop)
+- Use DATA to drive insights (no subjective opinions without evidence)
 - Prioritize action items by impact (HIGH/MEDIUM/LOW)
 - ALWAYS celebrate wins, even small ones
-- End with forward-looking predictions for next sprint
 - Save automatically to docs/08-project/retrospectives/ unless SAVE=false
 
 **Key Data Sources**:
 1. docs/09-agents/bus/log.jsonl - Event patterns, status transitions, blocking events
-2. docs/09-agents/status.json - Current state snapshot, WIP levels, owner distribution
+2. docs/09-agents/status.json - Current state, WIP levels, owner distribution
 3. docs/06-stories/**/US-*.md - Story completion, estimates vs actuals, AC rates
-4. Velocity data - Points completed, throughput trends from bus analysis
+4. Velocity data - Points completed, throughput trends
+
+**TodoWrite Task List** (create at start):
+```
+TodoWrite tool usage:
+- content: "1. Load data sources\n2. Analyze what went well\n3. Analyze improvements\n4. Detect patterns\n5. Generate action items\n6. Create celebration section\n7. Generate report\n8. Save file\n9. Update index"
+- status: "in-progress"
+- activeForm: true
+```
 
 **Workflow Steps**:
-1. Load and analyze data sources (bus logs, status, stories, velocity)
-2. Identify "What Went Well" patterns (high velocity, fast cycle times, epic completions, good estimation, balanced workload)
-3. Identify "What Needs Improvement" patterns (velocity drops, long cycles, high WIP, frequent blocking, poor estimation, bottlenecks)
-4. Detect advanced patterns (recurring blockers, day-of-week trends, handoff patterns, story size correlations)
-5. Generate prioritized action items (HIGH: immediate problems, MEDIUM: process improvements, LOW: long-term)
-6. Create celebration moments section (epic completions, velocity milestones, zero bugs, fast deliveries)
-7. Generate comprehensive ASCII report with sprint summary, insights, actions, team contributions, predictions
-8. Save to docs/08-project/retrospectives/retro-YYYYMMDD.md
-9. Update retrospectives/README.md index
-
-**Output Format Requirements**:
-- DEFAULT: ASCII box format with Unicode characters (╔═╗║╚╝)
-- Sections: Sprint Summary → What Went Well → What Needs Improvement → Action Items → Team Contributions → Predictions
-- Use icons: ✅ (Continue), ⚠️ (Improvement), 🛑 (Stop), ▶️ (Start), 🎯 (Actions), 📊 (Summary), 🔮 (Predictions), 🎉 (Celebrate)
-- Action items as checkboxes [ ] for tracking
-- Include velocity trends, cycle times, completion rates, blocking events
-- Show team contributions as horizontal bar charts
-- End with "Next Steps" recommendations
-
-**Pattern Analysis Examples**:
-- CONTINUE: Velocity increased, fast cycle times (<2d), zero blocked stories, epic completions, good estimation (<20% variance), balanced workload
-- START/STOP: Velocity drops, long cycle times (>5d), high WIP, frequent blocking, long review times, poor estimation (>50% variance), agent bottlenecks, stale stories (>10d in-progress)
-
-**Optional Inputs**:
-- TIMEFRAME: sprint|2weeks|30d|90d (default: 2weeks)
-- EPIC: <EP_ID> (retrospective for specific epic only)
-- FORMAT: ascii|markdown|html (default: ascii)
-- SAVE: true|false (default: true)
-
-**Integration Points**:
-- After /agileflow:metrics to contextualize data
-- Before sprint planning to apply learnings
-- With /agileflow:velocity to use trends
-- In /agileflow:babysit to suggest at sprint boundaries
-
-**Success Criteria**:
-- Comprehensive data analysis from all 4 sources
-- Balanced Continue/Start/Stop sections (not all negative)
-- Specific, actionable items (not vague suggestions)
-- Celebration section highlights wins
-- Predictions based on current velocity and epic progress
-- File saved to retrospectives/ directory with date stamp
-- Index updated with latest retrospective entry
+1. Create TodoWrite task list → Load and analyze data sources
+2. Identify "What Went Well" patterns (velocity, cycles, completions, estimation, workload)
+3. Identify "What Needs Improvement" patterns (velocity drops, cycles, WIP, blocking, bottlenecks)
+4. Detect advanced patterns (recurring blockers, handoffs, story size correlations)
+5. Generate prioritized action items (HIGH/MEDIUM/LOW) → Create celebration section
+6. Generate ASCII report → Save to retrospectives/ → Update index
+
+**Inputs** (optional):
+- `TIMEFRAME`: sprint|2weeks|30d|90d (default: 2weeks)
+- `EPIC`: <EP_ID> (epic-specific retrospective)
+- `FORMAT`: ascii|markdown|html (default: ascii)
+- `SAVE`: true|false (default: true)
+
+**Output Format**:
+- ASCII box with Unicode (╔═╗║╚╝)
+- Sections: Summary → What Went Well → What Needs Improvement → Actions → Team Contributions → Predictions
+- Icons: ✅ ⚠️ 🛑 ▶️ 🎯 📊 🔮 🎉
+
+**Example Usage**:
+```bash
+/agileflow:retro
+/agileflow:retro TIMEFRAME=30d
+/agileflow:retro EPIC=EP-0010 FORMAT=markdown
+```
+
+**Success Criteria**: Comprehensive data analysis, balanced Continue/Start/Stop, specific actionable items, celebration section, predictions, file saved with date stamp
+
+**Integration**: After `/metrics`, before sprint planning, with `/velocity`, in `/babysit`
 
 <!-- COMPACT_SUMMARY_END -->
 

package/src/core/commands/review.md

@@ -21,41 +21,36 @@ AI Code Reviewer that analyzes git diffs for quality, security, performance, and
 - **Provide specific fixes** - Include code snippets, not just descriptions
 
 ### Core Workflow
-1. Get git diff: `git diff <BASE>...<BRANCH>`
+1. Get git diff: `git diff <BASE>...<BRANCH>` (shell command)
 2. Analyze changes across 6 categories: Code Quality, Security, Performance, Best Practices, Testing, Documentation
 3. Generate structured report with issue count by severity (CRITICAL/HIGH/MEDIUM/LOW)
 4. Calculate code quality score (0-100) with breakdown by category
-5. Ask user about actions: auto-fix issues, create follow-up stories, block merge
+5. Optionally ask user to auto-fix issues, create follow-up stories, block merge
 6. Save report to `docs/08-project/code-reviews/<YYYYMMDD>-<BRANCH>.md`
 
-### Key Files
-- **Input**: Git diff between BASE and BRANCH
-- **Custom rules**: `.agileflow/review-rules.md`, `docs/02-practices/code-standards.md`
+### Key Files & Parsing
+- **Input**: Git diff between BASE and BRANCH (parse changed files and hunks)
+- **Custom rules**: `.agileflow/review-rules.md`, `docs/02-practices/code-standards.md` (YAML/markdown parsing)
 - **Output**: `docs/08-project/code-reviews/<YYYYMMDD>-<BRANCH>.md`
 
 ### Optional Arguments
-- `BRANCH=<name>` - Branch to review (default: current)
-- `BASE=<branch>` - Base branch for comparison (default: main/master)
-- `FOCUS=all|security|performance|style|tests` - Review scope (default: all)
-- `SEVERITY=critical|high|medium|low|all` - Filter by severity (default: all)
-
-### Security Checks
-- SQL injection, XSS vulnerabilities
-- Hardcoded secrets/credentials
-- Insecure dependencies, unsafe deserialization
-- Missing input validation, authentication/authorization issues
-
-### Performance Checks
-- N+1 query problems
-- Inefficient algorithms (O(n²) vs O(n))
-- Missing database indexes
-- Memory leaks, large bundle sizes
-
-### Quality Metrics
-- Cyclomatic complexity (threshold: 10)
-- Function length (target: <50 lines)
-- File length (target: <500 lines)
-- Test coverage (aim: >80%)
+- `BRANCH`: <name> (branch to review, default: current)
+- `BASE`: <branch> (base branch for comparison, default: main/master)
+- `FOCUS`: all|security|performance|style|tests (review scope, default: all)
+- `SEVERITY`: critical|high|medium|low|all (filter by severity, default: all)
+
+### Analysis Techniques
+- **Static Analysis**: AST parsing for complexity, duplication detection
+- **Pattern Matching**: Security regex patterns (hardcoded keys, SQL injection, XSS)
+- **Code Metrics**: Cyclomatic complexity (threshold: 10), function length (<50 lines), file length (<500 lines)
+- **Test Coverage**: Parse coverage reports (coverage/lcov.info) to map changed lines to tests
+
+### Example Usage**:
+```bash
+/agileflow:ai-code-review
+/agileflow:ai-code-review BRANCH=feature/auth BASE=main
+/agileflow:ai-code-review FOCUS=security SEVERITY=critical
+```
 
 <!-- COMPACT_SUMMARY_END -->
 

package/src/core/commands/session/end.md

@@ -3,344 +3,100 @@ description: Cleanly end session and record summary
 argument-hint: (no arguments)
 ---
 
-# End Session
+# /agileflow:session:end
 
-You are running the `/agileflow:session:end` command to cleanly close the current AgileFlow session.
+End the current session and optionally clean up the worktree.
 
-## IMMEDIATE ACTIONS
-
-**Execute these steps NOW in order:**
-
-### Step 1: Read session-state.json
-```bash
-cat docs/09-agents/session-state.json
-```
-If `current_session` is null, display "No active session" and stop.
-
-### Step 2: Get end timestamp and calculate duration
-```bash
-date -u +%Y-%m-%dT%H:%M:%SZ
-```
-Calculate duration from `current_session.started_at` to now.
-
-### Step 3: Get git activity since session start
-```bash
-git log --oneline HEAD~20..HEAD 2>/dev/null | head -10
-git diff --stat --shortstat 2>/dev/null | tail -1
-```
-
-### Step 4: Check status.json for completed stories
-Read `docs/09-agents/status.json` and identify stories with `status: "done"` that were completed during this session.
-
-### Step 5: Update session-state.json
-Use the Write tool to update the file:
-- Move `current_session` data to `last_session`
-- Add `ended_at` and `duration_minutes` to `last_session`
-- Add `stories_completed` array with story IDs completed this session
-- Set `current_session` to `null`
-- Append to `session_history` array (daily aggregate)
-
-### Step 6: Display session summary
-Output a formatted summary showing:
-- Session duration
-- Stories completed
-- Commits made
-- What to work on next
-
-## TODO LIST TRACKING
-
-**CRITICAL**: Immediately create a todo list using TodoWrite tool:
-```
-1. Read session-state.json (check for active session)
-2. Calculate session duration
-3. Get git activity
-4. Check completed stories
-5. Update session-state.json (move current to last)
-6. Display session summary
-```
+---
 
-## When to Use
+## Purpose
 
-- End of work day
-- Before stepping away for extended time
-- After completing a major milestone
-- Before switching to a different project
+When you're done with a session, this command:
+- Removes the session's lock file (marks it inactive)
+- Optionally removes the git worktree directory
+- Updates the registry with last active timestamp
 
-## Execution Flow
+## IMMEDIATE ACTIONS
 
-### 1. Check Active Session
+### Step 1: Get Current Session
 
 ```bash
-if [ ! -f "docs/09-agents/session-state.json" ]; then
-  echo "⚠️  No active session to end"
-  echo ""
-  echo "Run /agileflow:session:resume to start a session first"
-  exit 0
-fi
-
-CURRENT_SESSION=$(jq -r '.current_session.id' docs/09-agents/session-state.json)
-
-if [ "$CURRENT_SESSION" == "null" ]; then
-  echo "⚠️  No active session"
-  exit 0
-fi
+node .agileflow/scripts/session-manager.js status
 ```
 
-### 2. Gather Session Metrics
+If no current session is registered, display message and exit.
 
-```bash
-# Session timing
-STARTED_AT=$(jq -r '.current_session.started_at' docs/09-agents/session-state.json)
-ENDED_AT=$(date -u +%Y-%m-%dT%H:%M:%SZ)
-DURATION=$(calculate_duration "$STARTED_AT" "$ENDED_AT")
+### Step 2: Present Options with AskUserQuestion
 
-# Git activity
-BASELINE_COMMIT=$(jq -r '.current_session.baseline_commit // "HEAD~50"' docs/09-agents/session-state.json)
-COMMITS=$(git rev-list --oneline $BASELINE_COMMIT..HEAD 2>/dev/null | head -20)
-COMMIT_COUNT=$(echo "$COMMITS" | grep -c . || echo "0")
-
-# Files changed
-FILES_CHANGED=$(git diff --stat $BASELINE_COMMIT..HEAD 2>/dev/null | tail -1)
 ```
-
-### 3. Identify Completed Stories
-
-Check `docs/09-agents/status.json` for stories that changed to `completed` or `in-review` during this session:
-
-```bash
-# Compare to session start snapshot
-# Identify stories that moved to completed/in-review
+AskUserQuestion:
+  question: "End Session {id}?"
+  header: "End session"
+  multiSelect: false
+  options:
+    - label: "Yes, end session"
+      description: "Mark session inactive (keep worktree for later)"
+    - label: "End and delete worktree"
+      description: "Remove session and its directory completely"
+    - label: "Cancel"
+      description: "Keep session active"
 ```
 
-### 4. Run Final Test Check (Optional)
+Note: Don't show "delete worktree" option for main session (is_main: true).
 
-```
-Run final test verification before ending session? [Y/n]: _
-```
-
-If yes:
-```
-🧪 Running final tests...
-✅ All passing (42/42)
+### Step 3a: If "End session" Selected
 
-Final test status recorded.
+```bash
+node .agileflow/scripts/session-manager.js unregister {session_id}
 ```
 
-### 5. Update Session State
-
-Update `docs/09-agents/session-state.json`:
-
-```json
-{
-  "current_session": null,
-  "last_session": {
-    "id": "sess-20251216-140000",
-    "started_at": "2025-12-16T14:00:00Z",
-    "ended_at": "2025-12-16T18:30:00Z",
-    "duration_minutes": 270,
-    "stories_completed": ["US-0043"],
-    "stories_progressed": ["US-0044"],
-    "final_test_status": "passing",
-    "commits": ["abc123", "def456", "ghi789"],
-    "files_changed": 12,
-    "lines_added": 450,
-    "lines_removed": 120
-  },
-  "session_history": [
-    {
-      "date": "2025-12-16",
-      "sessions": 1,
-      "total_duration_minutes": 270,
-      "stories_completed": 1,
-      "commits": 3,
-      "test_regressions": 0
-    },
-    // ... previous days
-  ]
-}
+Display:
 ```
+✓ Session {id} ended
 
-### 6. Display Session Summary
+  Branch: {branch}
+  Story:  {story_id} (status unchanged)
+  Worktree kept at: {path}
 
+To resume later: cd {path} && claude
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-✅ Session Ended
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Session: sess-20251216-140000
-Duration: 4 hours 30 minutes
-Date: December 16, 2025
 
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📊 Accomplishments
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+### Step 3b: If "End and delete worktree" Selected
 
-Stories Completed (1):
-  ✅ US-0043: Add user profile settings page
-
-Stories Progressed (1):
-  🔄 US-0044: Implement password reset flow
-     Progress: 2/4 acceptance criteria
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📁 Code Changes
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Commits: 3
-  abc123 - feat: add profile form component
-  def456 - test: add profile validation tests
-  ghi789 - fix: profile image upload
-
-Files changed: 12
-Lines: +450 / -120
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🧪 Test Status
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Final: ✅ All Passing (42/42)
-No regressions introduced ✅
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📈 Session Stats
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-This session:
-  • Duration: 4h 30m
-  • Stories completed: 1
-  • Commits: 3
-  • Productivity: 0.22 stories/hour
-
-Today (all sessions):
-  • Total time: 4h 30m
-  • Stories completed: 1
-  • Sessions: 1
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📋 For Next Session
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Continue with:
-  🔄 US-0044: Implement password reset flow
-     Remaining: Email template, Token validation
-
-Ready to pick up:
-  • US-0045: Add email verification
-  • US-0046: Create admin dashboard
-
-Run /agileflow:session:resume to start next session
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+```bash
+node .agileflow/scripts/session-manager.js delete {session_id} --remove-worktree
 ```
 
-## Output Variations
-
-### Session With Uncommitted Changes
+Display:
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-⚠️  Uncommitted Changes Detected
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+✓ Session {id} ended and removed
 
-You have 3 uncommitted files:
-  M src/components/ProfileForm.tsx
-  M src/api/user.ts
-  ? src/utils/validation.ts
+  Branch: {branch}
+  Worktree removed: {path}
 
-Options:
-  1. Commit changes now
-  2. End session anyway (changes preserved)
-  3. Cancel and continue working
-
-Choice [1/2/3]: _
+💡 The branch still exists. To delete it:
+   git branch -d {branch}
 ```
 
-### Short Session Warning
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-📊 Session Summary
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+### Step 3c: If "Cancel" Selected
 
-Session Duration: 15 minutes
-
-ℹ️  Short session - minimal changes recorded.
-
-Commits: 0
-Stories completed: 0
-
-End this session? [y/N]: _
 ```
-
-### Session With Failing Tests
+Session remains active.
 ```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-⚠️  Tests Failing
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Current test status: ❌ FAILING (40/42)
 
-Failed tests:
-  ❌ auth.test.ts:42
-  ❌ auth.test.ts:67
+## Main Session Warning
 
-Ending session with failing tests will:
-  • Record "failing" as final test status
-  • Flag potential regression for next session
+If current session is the main project (is_main: true):
 
-Options:
-  1. Fix tests first (recommended)
-  2. End session with failing tests
-  3. Cancel
-
-Choice [1/2/3]: _
 ```
+⚠️ This is the main project session.
 
-### Productive Session
-```
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🎉 Great Session!
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Duration: 6 hours
-Stories completed: 3
-Commits: 12
-Tests: ✅ All passing
-
-Above average productivity! 🚀
-
-Completed:
-  ✅ US-0043: Add user profile settings page
-  ✅ US-0044: Implement password reset flow
-  ✅ US-0045: Add email verification
-
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+You can only end this session (mark inactive), not delete the directory.
+The main project is not a worktree and cannot be removed.
 ```
 
 ## Related Commands
 
-| Command | Purpose |
-|---------|---------|
-| `/agileflow:session:init` | One-time setup of session harness |
-| `/agileflow:session:resume` | Start session with verification |
-| `/agileflow:session:status` | Quick view of current session |
-| `/agileflow:session:history` | View past sessions and analytics |
-
-## Integration Points
-
-### Reads
-- `docs/09-agents/session-state.json` - Current session
-- `docs/09-agents/status.json` - Story status
-- Git log - Commits during session
-
-### Updates
-- `docs/09-agents/session-state.json` - Moves current to last, updates history
-
-### Optionally Runs
-- `/agileflow:verify` - Final test check
-
-## Implementation Notes
-
-1. **Safe**: Never loses work - only records metadata
-2. **Summarizing**: Provides clear recap of accomplishments
-3. **Forward-Looking**: Suggests what to work on next
-4. **Flexible**: Can end with failing tests or uncommitted changes
-5. **Analytics-Ready**: Updates history for tracking over time
+- `/agileflow:session:new` - Create new session
+- `/agileflow:session:resume` - Switch sessions
+- `/agileflow:session:status` - View all sessions