agileflow 2.50.0 → 2.55.0

package/src/core/commands/baseline.md

@@ -85,6 +85,26 @@ git checkout agileflow-baseline-20251222-143000
 - Use descriptive messages for future reference
 - Compare current state to baseline with `/agileflow:verify`
 
+**Tools Used**:
+- TodoWrite: Track 8-step baseline creation workflow
+
+**TodoWrite Example**:
+```xml
+<invoke name="TodoWrite">
+<parameter name="content">
+1. Run pre-flight checks (session harness, tests, git status, story tests)
+2. Show baseline summary (what will be included)
+3. Get baseline message (from user or use default)
+4. Create git tag with timestamp
+5. Update docs/00-meta/environment.json (baseline_commit)
+6. Update docs/09-agents/session-state.json (baseline history)
+7. Update story frontmatter (verified_at_baseline)
+8. Display final report
+</parameter>
+<parameter name="status">in-progress</parameter>
+</invoke>
+```
+
 <!-- COMPACT_SUMMARY_END -->
 
 ## Prompt

package/src/core/commands/blockers.md

@@ -30,63 +30,48 @@ This gathers git status, stories/epics, session state, and registers for PreComp
 - Display recently resolved blockers (optional)
 
 **Arguments** (all optional):
-- `AGENT=<id>` - Filter by specific agent (e.g., AG-UI, AG-API)
-- `SHOW_RESOLVED=true` - Include recently resolved blockers (last 7 days)
-- `DETAILED=true` - Show extended details (dependencies, research links, ADRs)
-
-**Data Sources**:
-1. `status.json` - Current story statuses and blockers
-2. `bus/log.jsonl` - Recent unblock/blocked messages
-3. Story files (`US-*.md`) - Detailed story information
-4. ADRs (`adr-*.md`) - Architecture decisions for context
-5. Research notes (`10-research/*.md`) - Background research
-6. Epic files - Epic context for blocked stories
+- `AGENT`: <id> (filter by specific agent: AG-UI, AG-API, etc.)
+- `SHOW_RESOLVED`: true (include recently resolved blockers, last 7 days)
+- `DETAILED`: true (show extended details: dependencies, research links, ADRs)
 
-**Blocker Types Detected**:
-1. **Direct Blockers** - Stories with status="blocked"
-2. **Dependency Blockers** - Stories waiting on incomplete dependencies
-3. **WIP Capacity Blockers** - Agents at WIP limit (2 in-progress stories)
-4. **Stale Blockers** - Blocked >14 days (critical priority)
+**Data Sources** (parsing required):
+1. `status.json` - Current story statuses and blockers (JSON parsing)
+2. `bus/log.jsonl` - Recent unblock/blocked messages (JSON parsing + timestamp filtering)
+3. Story files (`US-*.md`) - Detailed story information (YAML frontmatter parsing)
+4. ADRs (`adr-*.md`) - Architecture decisions (keyword matching)
+5. Research notes (`10-research/*.md`) - Background research (keyword matching)
 
-**Output Sections**:
-- **Summary Stats** - Count by type, critical count, cross-agent coordination
-- **Critical Blockers** - Stale blockers (>14 days) needing immediate attention
-- **Active Blockers** - Grouped by category with resolution suggestions
-- **AG-API Unblocking Status** - v2.7.0 coordination tracking
-- **Capacity Analysis** - Agents at WIP limit with waiting stories
-- **Recently Resolved** - Last 7 days of unblock activity (if requested)
-- **Prioritized Actions** - Ranked next steps with suggested commands
-
-**Resolution Suggestions Include**:
-- Estimated completion time for blocking dependencies
-- Interim workarounds (mock data, feature flags)
-- Linked ADRs and research for context
-- Specific questions for clarification blockers
-- Escalation paths for external blockers
-- Redistribution options for capacity blockers
+**Blocker Types Detected**:
+1. **Direct** - Stories with status="blocked" (extract from status.json)
+2. **Dependency** - Stories waiting on incomplete dependencies (parse frontmatter deps_on)
+3. **WIP Capacity** - Agents at WIP limit (count in-progress stories per agent)
+4. **Stale** - Blocked >14 days (timestamp comparison)
+
+**Workflow**:
+1. Extract all blockers from status.json → Parse bus/log.jsonl for recent activity
+2. Categorize by type (Technical/Coordination/Clarification/External/Capacity/Research)
+3. For each blocker: Match to ADRs/research via keyword search
+4. Generate resolution suggestions (estimated unblock time, workarounds, escalation)
+5. If SHOW_RESOLVED=true: Extract unblock messages from last 7 days
+6. Prioritize actions and display dashboard
 
 **Example Usage**:
 ```bash
-# All blockers
 /agileflow:blockers
-
-# AG-UI blockers only
 /agileflow:blockers AGENT=AG-UI
-
-# Include resolved blockers
-/agileflow:blockers SHOW_RESOLVED=true
-
-# Full detailed output
-/agileflow:blockers DETAILED=true
+/agileflow:blockers SHOW_RESOLVED=true DETAILED=true
 ```
 
-**Related Commands**:
-- `/agileflow:status` - Update blocker status
-- `/story-new` - Create unblocking stories
-- `/handoff` - Reassign capacity-blocked stories
-- `/adr-new` - Document architectural decisions
-- `/agileflow:board` - Visualize current state
-- `/agileflow:validate-system` - Check for inconsistencies
+**Output Sections**:
+- Summary Stats (count by type, critical count)
+- Critical Blockers (stale >14 days)
+- Active Blockers (grouped by category with solutions)
+- AG-API Unblocking Status (v2.7.0 coordination)
+- Capacity Analysis (agents at WIP limit)
+- Recently Resolved (last 7 days if requested)
+- Prioritized Actions (ranked next steps)
+
+**Integration**: With `/status`, `/story-new`, `/handoff`, `/adr-new`, `/board`, `/validate-system`
 <!-- COMPACT_SUMMARY_END -->
 
 Comprehensive blocker tracking, resolution suggestions, and cross-agent coordination (leverages v2.7.0 AG-API unblocking capabilities).

package/src/core/commands/board.md

@@ -89,6 +89,25 @@ This gathers git status, stories/epics, session state, and registers for PreComp
 - Export board snapshots to track velocity over time
 - Use GROUP_BY=owner to balance workload
 
+**Tool Usage Examples**:
+
+AskUserQuestion (for actions after displaying board):
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "What would you like to do?",
+  "header": "Board Actions",
+  "multiSelect": false,
+  "options": [
+    {"label": "Update a story status", "description": "Change story status on board"},
+    {"label": "Export board", "description": "Save board snapshot to file"},
+    {"label": "View story details", "description": "See full story information"},
+    {"label": "Filter board", "description": "Filter by epic/owner"}
+  ]
+}]</parameter>
+</invoke>
+```
+
 <!-- COMPACT_SUMMARY_END -->
 
 ## Prompt

package/src/core/commands/changelog.md

@@ -78,6 +78,26 @@ Automatically generate changelog from PR titles, commits, and tags.
 - Crash when user is null (#124)
 - Memory leak in WebSocket handler (#139)
 ```
+
+**Tool Usage Example**:
+When commits need manual categorization:
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{
+  "question": "How should this commit be categorized?",
+  "header": "Categorize Commit",
+  "multiSelect": false,
+  "options": [
+    {"label": "Added", "description": "New feature or capability (feat:)"},
+    {"label": "Changed", "description": "Modification or enhancement (refactor:, perf:)"},
+    {"label": "Fixed", "description": "Bug fix (fix:)"},
+    {"label": "Security", "description": "Security fix (security:)"},
+    {"label": "Skip", "description": "Don't include in changelog"}
+  ]
+}]</parameter>
+</invoke>
+```
+
 <!-- COMPACT_SUMMARY_END -->
 
 ## Prompt

package/src/core/commands/ci.md

@@ -52,6 +52,23 @@ Bootstrap minimal CI workflow and CODEOWNERS.
 /docs/03-decisions/ @owners
 ```
 
+**Tools Used**:
+- TodoWrite: Track 5-step setup workflow
+
+**TodoWrite Example**:
+```xml
+<invoke name="TodoWrite">
+<parameter name="content">
+1. Parse input (OWNERS)
+2. Create .github/workflows/ci.yml with lint/typecheck/test jobs
+3. Create CODEOWNERS file with owner mappings
+4. Show preview and wait for YES/NO confirmation
+5. Print notes for enabling required checks
+</parameter>
+<parameter name="status">in-progress</parameter>
+</invoke>
+```
+
 **Workflow**:
 1. Parse OWNERS input
 2. Generate CI workflow with generic job placeholders

package/src/core/commands/context.md

@@ -20,50 +20,53 @@ Web AI Context Manager - Generates/exports/manages project context briefs for we
 - **Import is one-step**: Process CONTENT immediately and create research file
 - **Link research files**: Always reference research from ADRs/Epics/Stories that use it
 
+### Tool Usage Examples
+
+**TodoWrite** (for all modes requiring multi-step tracking):
+```xml
+<invoke name="TodoWrite">
+<parameter name="content">1. Read existing docs/context.md
+2. Gather sources (status.json, bus/log.jsonl, epics)
+3. Extract key information
+4. Generate managed sections
+5. Show diff for review
+6. Apply changes after YES</parameter>
+<parameter name="status">in-progress</parameter>
+<parameter name="activeForm">1</parameter>
+</invoke>
+```
+
+**Edit** (when writing context or research files):
+```xml
+<invoke name="Edit">
+<parameter name="file_path">/full/path/to/docs/context.md</parameter>
+<parameter name="old_string"><!-- MANAGED_SECTION -->\n[old content]\n<!-- END_MANAGED --></parameter>
+<parameter name="new_string"><!-- MANAGED_SECTION -->\n[new content]\n<!-- END_MANAGED --></parameter>
+</invoke>
+```
+
+**AskUserQuestion** (when needing confirmation):
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{"question": "Apply these changes?", "header": "Diff Preview", "multiSelect": false, "options": [{"label": "Yes, update", "description": "Write changes"}, {"label": "No, abort", "description": "Cancel"}]}]</parameter>
+</invoke>
+```
+
 ### Core Workflow
 
-**MODE=full (default)**
-1. Create todo list tracking: read existing, gather sources, extract info, generate sections, preserve user content, show diff, apply after YES
-2. Read docs/context.md (if exists)
-3. Gather sources: status.json, bus/log.jsonl, epics, stories, ADRs, practices, architecture, roadmap, research, manifests, CI, CHANGELOG
-4. Generate comprehensive context with: what we're building, current focus, feature map, tech/tooling, decisions, architecture, testing, recent progress, risks, next steps
-5. Show diff, wait for YES confirmation
-6. Update only managed sections
-
-**MODE=export**
-1. Read docs/context.md
-2. Output concise excerpt (≤300 lines): last updated, what we're building, current focus, tech/tooling, key decisions, feature map, next steps
-3. End with "Paste this excerpt into your web AI tool..."
-4. NO file writes
-
-**MODE=note**
-1. Append timestamped note under "Notes" section
-2. Create section if missing
-3. Show diff, wait for YES confirmation
-
-**MODE=research**
-1. Create todo list tracking: generate prompt, wait for results, format research, save to docs/10-research/, update index, ask about ADR/Epic/Story, link research
-2. STEP 1: Generate single code block prompt for web AI requesting TL;DR, step-by-step plan, code snippets, config, tests, security checklist, ADR draft, story breakdown, rollback plan, risks, PR template, sourcing rules
-3. Tell user to paste prompt into ChatGPT/Perplexity and return with results
-4. STEP 2: When user returns with results, format into structured markdown with sections: Summary, Key Findings, Implementation, Code Snippets, Security, Testing, Risks, ADR Recommendation, Story Breakdown, References
-5. Save to docs/10-research/YYYYMMDD-topic-slug.md
-6. Update docs/10-research/README.md index
-7. Ask if user wants ADR/Epic/Story created from research
-8. Add research reference to created ADR/Epic/Story
-
-**MODE=import**
-1. Create todo list tracking: validate inputs, process content, extract key points, extract code, generate actions, suggest stories, format research file, save, update index
-2. Validate TOPIC and CONTENT are provided
-3. Process raw content (transcript, article, etc.) by: summarizing key points, extracting code snippets, generating action items, suggesting user stories
-4. Format into structured research file with all extracted sections
-5. Save to docs/10-research/YYYYMMDD-topic-slug.md
-6. Update docs/10-research/README.md index
-7. Ask if user wants ADR/Epic/Story created from imported content
-8. Add research reference to created ADR/Epic/Story
+**MODE=full**: Create todo list → Read docs/context.md → Gather sources → Generate sections → Show diff → Apply after YES
+
+**MODE=export**: Read docs/context.md → Output ≤300 line excerpt → No file writes
+
+**MODE=note**: Create todo list → Append timestamped note → Show diff → Apply after YES
+
+**MODE=research**: Create todo list → STEP 1: Generate prompt → STEP 2: Format & save to docs/10-research/
+
+**MODE=import**: Create todo list → Validate inputs → Process content → Save to docs/10-research/
 
 ### Key Files
-- docs/context.md - Main context brief (managed sections + user content)
-- docs/10-research/YYYYMMDD-topic-slug.md - Research results storage
+- docs/context.md - Main context brief
+- docs/10-research/YYYYMMDD-topic-slug.md - Research storage
 - docs/10-research/README.md - Research index
 - status.json - Current work tracking
 - bus/log.jsonl - Recent progress messages

package/src/core/commands/debt.md

@@ -16,63 +16,54 @@ Track and visualize technical debt across the codebase.
 <!-- COMPACT_SUMMARY_START -->
 ## Compact Summary
 
-**Purpose**: Identify, categorize, and prioritize technical debt for refactoring
+**Command**: `tech-debt` - Identify, categorize, and prioritize technical debt for refactoring
 
 **Quick Usage**:
 ```
 /agileflow:tech-debt SCAN=quick OUTPUT=report THRESHOLD=medium
 ```
 
-**What It Does**:
-1. Scans codebase for debt indicators (TODO, complexity, duplication)
-2. Searches stories tagged with `tech-debt: true`
-3. Analyzes ADRs for deprecated decisions
-4. Reviews git history for high-churn files
-5. Categorizes debt by type (Architecture, Code Quality, Testing, etc.)
-6. Scores each item by Severity × Scope × Pain
-7. Generates prioritized debt report
-8. Optionally creates stories for critical debt
-
-**Required Inputs**:
-- None (all optional with smart defaults)
+**What It Does**: Scan codebase → Categorize debt → Score by Severity/Scope/Pain → Generate report → Optional stories
 
 **Optional Inputs**:
-- `SCAN=full|quick` - Scan depth (default: quick)
-- `OUTPUT=report|stories|both` - Output type (default: report)
-- `THRESHOLD=high|medium|low` - Minimum severity (default: medium)
-
-**Output Files**:
-- Debt report: `docs/08-project/tech-debt-<YYYYMMDD>.md`
-- Optional: Stories for top debt items
-- Optional: Dashboard at `docs/08-project/debt-dashboard.md`
-
-**Debt Categories**:
-- Architecture: Wrong abstractions, tight coupling
-- Code Quality: Duplication, complexity, style issues
-- Documentation: Missing, outdated, incomplete
-- Testing: Low coverage, flaky tests, missing E2E
-- Security: Outdated deps, exposed secrets, weak auth
-- Performance: N+1 queries, memory leaks, slow ops
-- Dependencies: Outdated packages, unmaintained libs
+- `SCAN=full|quick` (default: quick)
+- `OUTPUT=report|stories|both` (default: report)
+- `THRESHOLD=high|medium|low` (default: medium)
+
+### Tool Usage Examples
+
+**Bash** (to scan codebase for TODOs, complexity, etc.):
+```xml
+<invoke name="Bash">
+<parameter name="command">grep -r "TODO\|FIXME\|HACK" src/ --include="*.ts" --include="*.js" | head -20</parameter>
+<parameter name="description">Find TODO comments in codebase</parameter>
+</invoke>
+```
 
-**Scoring Formula**:
+**Glob** (to find high-churn files):
+```xml
+<invoke name="Glob">
+<parameter name="pattern">src/**/*.{ts,js}</parameter>
+</invoke>
 ```
-Score = (Severity × Scope × Pain) / 10
-- Severity: 1-10 (impact level)
-- Scope: 1-10 (files affected)
-- Pain: 1-10 (developer frustration)
+
+**Read** (to analyze git history and ADRs):
+```xml
+<invoke name="Read">
+<parameter name="file_path">/full/path/to/docs/03-decisions/adr-0015-deprecated.md</parameter>
+</invoke>
 ```
 
-**Workflow**:
-1. Scan for debt indicators across codebase
-2. Categorize and score each item
-3. Generate prioritized report
-4. Ask: "Generate stories for critical debt? (YES/NO)"
-5. Ask: "Save report to docs/08-project/? (YES/NO)"
-6. Suggest adding debt review to roadmap
+**Write** (to save debt report):
+```xml
+<invoke name="Write">
+<parameter name="file_path">/full/path/to/docs/08-project/tech-debt-20251222.md</parameter>
+<parameter name="content"># Technical Debt Report
+
+**Generated**: 2025-12-22
+**Total Debt Items**: 42
+**Critical**: 3 | **High**: 12 | **Medium**: 18 | **Low**: 9
 
-**Example Report Section**:
-```markdown
 ## Critical Debt (Score >80)
 
 ### 1. Auth service tightly coupled to database
@@ -85,8 +76,48 @@ Score = (Severity × Scope × Pain) / 10
 **Type**: Testing | **Score**: 85
 **Impact**: High regression risk, blocking production
 **Files**: src/api/payments/*.ts (12 files, 0% coverage)
-**Estimate**: 2-3 days
+**Estimate**: 2-3 days</parameter>
+</invoke>
 ```
+
+**Write** (to create debt stories):
+```xml
+<invoke name="Write">
+<parameter name="file_path">/full/path/to/docs/06-stories/EP-XXXX/US-XXXX-refactor-auth.md</parameter>
+<parameter name="content">---
+story_id: US-XXXX
+type: tech-debt
+debt_score: 87
+estimate: 3d
+---
+
+# US-XXXX: Refactor auth service to separate concerns
+
+## Current State (Before)
+Auth service tightly coupled to database layer...
+
+## Desired State (After)
+Clear separation: AuthService, AuthRepository, AuthController...</parameter>
+</invoke>
+```
+
+**AskUserQuestion** (for approval):
+```xml
+<invoke name="AskUserQuestion">
+<parameter name="questions">[{"question": "Generate stories for critical debt?", "header": "Action", "multiSelect": false, "options": [{"label": "Yes, create stories", "description": "Generate stories for top 5 critical items"}, {"label": "No, report only", "description": "Save report without creating stories"}]}]</parameter>
+</invoke>
+```
+
+**Debt Categories**:
+- Architecture: Wrong abstractions, tight coupling
+- Code Quality: Duplication, complexity, style issues
+- Documentation: Missing, outdated, incomplete
+- Testing: Low coverage, flaky tests, missing E2E
+- Security: Outdated deps, exposed secrets, weak auth
+- Performance: N+1 queries, memory leaks, slow ops
+- Dependencies: Outdated packages, unmaintained libs
+
+**Output Files**: `docs/08-project/tech-debt-<YYYYMMDD>.md` | Optional stories | Optional dashboard
 <!-- COMPACT_SUMMARY_END -->
 
 ## Prompt

package/src/core/commands/deploy.md

@@ -56,6 +56,26 @@ Automatically set up deployment pipeline for the project.
 - Mobile (Expo) → EAS
 - Serverless → AWS Lambda, Vercel Functions
 
+**Tools Used**:
+- TodoWrite: Track 8-step deployment setup workflow
+
+**TodoWrite Example**:
+```xml
+<invoke name="TodoWrite">
+<parameter name="content">
+1. Detect project type (static, full-stack, mobile, containers, serverless)
+2. Recommend platform based on project type
+3. Generate deployment configuration files
+4. Create CI/CD workflow file
+5. Create .env.example and secrets management docs
+6. Show configuration preview
+7. Create files after YES/NO confirmation
+8. Display next steps (add secrets, connect repo, test deploy)
+</parameter>
+<parameter name="status">in-progress</parameter>
+</invoke>
+```
+
 **Workflow**:
 1. Detect project type from package.json, Dockerfile, etc.
 2. Recommend deployment platform

package/src/core/commands/deps.md

@@ -26,63 +26,57 @@ This gathers git status, stories/epics, session state, and registers for PreComp
 **Purpose**: Visualize and analyze story/epic dependency graphs with critical path detection, circular dependency checking, and blocking story impact analysis.
 
 **Input Parameters** (all optional):
-- SCOPE=story|epic|all (default: all)
-- EPIC=<EP_ID> (show dependencies within specific epic)
-- STORY=<US_ID> (show dependencies for specific story)
-- FORMAT=ascii|mermaid|graphviz|json (default: ascii)
-- ANALYSIS=critical-path|circular|blocking|all (default: all)
+- `SCOPE`: story|epic|all (default: all)
+- `EPIC`: <EP_ID> (dependencies within specific epic)
+- `STORY`: <US_ID> (dependencies for specific story)
+- `FORMAT`: ascii|mermaid|graphviz|json (default: ascii)
+- `ANALYSIS`: critical-path|circular|blocking|all (default: all)
 
 **Dependency Sources**:
-1. Story frontmatter (depends_on, blocks fields)
-2. Bus log (implicit dependencies from blocked events)
-3. Epic hierarchy (parent-child relationships)
+1. Story frontmatter - depends_on, blocks fields (YAML parsing):
+   ```yaml
+   depends_on:
+     - US-0030
+     - US-0031
+   blocks:
+     - US-0033
+   ```
+2. Bus log - implicit dependencies from blocked events (JSON parsing)
+3. Epic hierarchy - parent-child relationships
 
 **Core Analysis Types**:
-1. **Critical Path Detection**: Longest path from root to leaf story (delays here affect entire project)
-2. **Circular Dependency Detection**: Identify impossible-to-complete dependency cycles
-3. **Blocking Story Impact**: Find stories that block multiple others (high-priority bottlenecks)
-4. **Parallel Work Opportunities**: Identify stories that can be started now (no blockers)
-
-**Output Format** (ASCII default):
+1. **Critical Path**: Longest path from root to leaf (delays affect entire project)
+2. **Circular Dependency Detection**: Impossible-to-complete cycles (flag as errors)
+3. **Blocking Story Impact**: Stories that block multiple others (bottlenecks)
+4. **Parallel Work Opportunities**: Stories ready to start (no blockers)
+
+**Parsing Algorithm**:
+1. Read all story frontmatter files → Extract depends_on, blocks
+2. Query bus/log.jsonl for implicit dependencies
+3. Build adjacency list graph structure
+4. Run DFS for critical path (longest path from roots to leaves)
+5. Run cycle detection algorithm (DFS with visited tracking)
+6. Calculate impact scores for each blocking story
+7. Render in requested format
+
+**Example Usage**:
+```bash
+/agileflow:dependencies
+/agileflow:dependencies EPIC=EP-0010
+/agileflow:dependencies STORY=US-0032 ANALYSIS=critical-path
+/agileflow:dependencies FORMAT=mermaid
 ```
-Story Dependency Graph
-━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-
-Legend:
-  ✅ Done    🟢 Ready    🟡 In Progress    🔵 In Review    ⚪ Blocked
-
-[Visual tree showing dependencies]
-
-Critical Path:
-  US-0030 → US-0031 → US-0032 → US-0033  (11 days total)
 
-Blocking Stories:
-  US-0040 blocks: US-0041, US-0042  (⚠️ High impact)
-
-Circular Dependencies: None detected ✅
-```
+**Output**: ASCII tree with legend, critical path, blocking stories, circular dependency check, actionable recommendations
 
 **Critical Rules**:
 - Parse frontmatter first (authoritative source)
-- Flag circular dependencies as errors (cannot be completed)
-- Highlight critical path stories (delays affect entire project)
+- Flag circular dependencies as errors (cannot complete)
+- Highlight critical path stories (delays affect project)
 - Show actionable recommendations
-- Use consistent color coding across all formats
+- Use consistent color coding across formats
 
-**Common Usage**:
-```bash
-/agileflow:dependencies                    # Show all dependencies
-/agileflow:dependencies EPIC=EP-0010       # Specific epic
-/agileflow:dependencies STORY=US-0032      # Specific story
-/agileflow:dependencies ANALYSIS=critical-path  # Only critical path
-/agileflow:dependencies FORMAT=mermaid     # Export as Mermaid
-```
-
-**Integration Points**:
-- Before `/board`: Understand blockers before planning
-- After `/story-new`: Visualize impact of new story
-- In `/babysit`: Check dependencies before starting work
-- With `/metrics`: Correlate cycle time with dependency depth
+**Integration**: Before `/board`, after `/story-new`, in `/babysit`, with `/metrics`
 
 <!-- COMPACT_SUMMARY_END -->