agileflow 2.95.0 → 2.95.2

package/CHANGELOG.md

@@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [2.95.2] - 2026-02-01
+
+### Changed
+- Fix damage control hook MODULE_NOT_FOUND error
+
+## [2.95.1] - 2026-01-30
+
+### Fixed
+- Fix stale doc counts and scoped npm audit
+
 ## [2.95.0] - 2026-01-30
 
 ### Added

package/README.md

@@ -3,7 +3,7 @@
 </p>
 
 [![npm version](https://img.shields.io/npm/v/agileflow?color=brightgreen)](https://www.npmjs.com/package/agileflow)
-[![Commands](https://img.shields.io/badge/commands-79-blue)](docs/04-architecture/commands.md)
+[![Commands](https://img.shields.io/badge/commands-81-blue)](docs/04-architecture/commands.md)
 [![Agents/Experts](https://img.shields.io/badge/agents%2Fexperts-34-orange)](docs/04-architecture/subagents.md)
 [![Skills](https://img.shields.io/badge/skills-dynamic-purple)](docs/04-architecture/skills.md)
 
@@ -65,7 +65,7 @@ AgileFlow combines three proven methodologies:
 
 | Component | Count | Description |
 |-----------|-------|-------------|
-| [Commands](docs/04-architecture/commands.md) | 79 | Slash commands for agile workflows |
+| [Commands](docs/04-architecture/commands.md) | 81 | Slash commands for agile workflows |
 | [Agents/Experts](docs/04-architecture/subagents.md) | 34 | Specialized agents with self-improving knowledge bases |
 | [Skills](docs/04-architecture/skills.md) | Dynamic | Generated on-demand with `/agileflow:skill:create` |
 
@@ -76,7 +76,7 @@ AgileFlow combines three proven methodologies:
 Full documentation lives in [`docs/04-architecture/`](docs/04-architecture/):
 
 ### Reference
-- [Commands](docs/04-architecture/commands.md) - All 79 slash commands
+- [Commands](docs/04-architecture/commands.md) - All 81 slash commands
 - [Agents/Experts](docs/04-architecture/subagents.md) - 34 specialized agents with self-improving knowledge
 - [Skills](docs/04-architecture/skills.md) - Dynamic skill generator with MCP integration
 

package/package.json

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

package/scripts/agileflow-welcome.js

@@ -870,7 +870,7 @@ When \`/agileflow:babysit\` is active (check session-state.json), these rules ar
 1. **ALWAYS end responses with the AskUserQuestion tool** - Not text like "What next?" but the ACTUAL TOOL CALL
 2. **Use Plan Mode for non-trivial tasks** - Call \`EnterPlanMode\` before complex implementations
 3. **Delegate complex work to domain experts** - Use \`Task\` tool with appropriate \`subagent_type\`
-4. **Track progress with TodoWrite** - For any task with 3+ steps
+4. **Track progress with TaskCreate/TaskUpdate** - For any task with 3+ steps
 
 These rules persist across conversation compaction. Check \`docs/09-agents/session-state.json\` for active commands.
 ${marker}

package/scripts/babysit-context-restore.js

@@ -66,7 +66,7 @@ function main() {
       '\x1b[36m║\x1b[0m  3. Delegate complex work to domain experts                  \x1b[36m║\x1b[0m'
     );
     console.log(
-      '\x1b[36m║\x1b[0m  4. Track progress with TodoWrite for 3+ step tasks          \x1b[36m║\x1b[0m'
+      '\x1b[36m║\x1b[0m  4. Track progress with TaskCreate/TaskUpdate for 3+ step tasks          \x1b[36m║\x1b[0m'
     );
     console.log(
       '\x1b[36m║\x1b[0m                                                              \x1b[36m║\x1b[0m'

package/scripts/lib/configure-features.js

@@ -1157,7 +1157,7 @@ When \`/agileflow:babysit\` is active (check session-state.json), these rules ar
 1. **ALWAYS end responses with the AskUserQuestion tool** - Not text like "What next?" but the ACTUAL TOOL CALL
 2. **Use Plan Mode for non-trivial tasks** - Call \`EnterPlanMode\` before complex implementations
 3. **Delegate complex work to domain experts** - Use \`Task\` tool with appropriate \`subagent_type\`
-4. **Track progress with TodoWrite** - For any task with 3+ steps
+4. **Track progress with TaskCreate/TaskUpdate** - For any task with 3+ steps
 
 These rules persist across conversation compaction. Check \`docs/09-agents/session-state.json\` for active commands.
 ${CLAUDE_MD_MARKER}

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

@@ -62,7 +62,7 @@ compact_context:
   priority: critical
   preserve_rules:
     - "MUST use AskUserQuestion for all decisions"
-    - "MUST track progress with TodoWrite"
+    - "MUST track progress with TaskCreate/TaskUpdate"
 ---
 ```
 

package/src/core/agents/configuration-visual-e2e.md

@@ -18,7 +18,7 @@ compact_context:
     - "Create screenshots/ directory for visual verification workflow"
     - "Add test:e2e script to package.json"
     - "All screenshots must be visually reviewed and renamed with 'verified-' prefix"
-    - "Use TodoWrite to track all 8 setup steps"
+    - "Use TaskCreate/TaskUpdate to track all 8 setup steps"
     - "Run example test after setup to verify it works"
   state_fields:
     - playwright_installed

package/src/core/commands/adr.md

@@ -205,7 +205,7 @@ Both are important - readers need full trade-off picture.
 ROLE: ADR Writer
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track ADR creation:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track ADR creation:
 ```
 1. Parse inputs (NUMBER, TITLE, CONTEXT, DECISION, CONSEQUENCES, LINKS)
 2. Create docs/03-decisions/adr-<NUMBER>-<slug>.md from template

package/src/core/commands/audit.md

@@ -70,17 +70,15 @@ This gathers git status, stories/epics, session state, and registers for PreComp
 
 **Tool Usage Examples**:
 
-TodoWrite:
+Task Tracking:
 ```xml
-<invoke name="TodoWrite">
-<parameter name="todos">[
-  {"content": "Parse story ID and load story data", "status": "in_progress", "activeForm": "Loading story"},
-  {"content": "Run project tests", "status": "pending", "activeForm": "Running tests"},
-  {"content": "Verify acceptance criteria with user", "status": "pending", "activeForm": "Verifying AC"},
-  {"content": "Capture learnings", "status": "pending", "activeForm": "Capturing learnings"},
-  {"content": "Generate audit verdict and next steps", "status": "pending", "activeForm": "Generating verdict"}
-]</parameter>
+<!-- Create tasks for multi-step workflow -->
+<invoke name="TaskCreate">
+<parameter name="subject">Parse story ID and load story data</parameter>
+<parameter name="description">Load story from status.json and verify it exists</parameter>
+<parameter name="activeForm">Loading story</parameter>
 </invoke>
+<!-- Then use TaskUpdate with taskId to mark in_progress/completed -->
 ```
 
 AskUserQuestion (AC Verification):
@@ -111,8 +109,8 @@ ROLE: Story Auditor
 INPUTS
 STORY=<US-ID>   Required - story to audit
 
-TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool:
+TASK TRACKING
+**CRITICAL**: Immediately create tasks using TaskCreate tool:
 ```
 1. Parse story ID and load story data
 2. Run project tests

package/src/core/commands/auto.md

@@ -5,7 +5,7 @@ compact_context:
   priority: high
   preserve_rules:
     - "ACTIVE COMMAND: /agileflow:auto-story - Auto-generate stories from product artifacts"
-    - "CRITICAL: Use TodoWrite to track 10-step generation process immediately"
+    - "CRITICAL: Use TaskCreate/TaskUpdate to track 10-step generation process immediately"
     - "CRITICAL: Always preview BEFORE creating (AUTO_CREATE=no default)"
     - "MUST generate stories with Given/When/Then Acceptance Criteria format"
     - "MUST estimate using INVEST: 0.5d (simple) | 1d (standard) | 1.5d (complex) | 2d (refactor)"
@@ -46,9 +46,9 @@ node .agileflow/scripts/obtain-context.js auto
 
 ### Tool Usage Examples
 
-**TodoWrite** (to track auto-generation):
+**TaskCreate/TaskUpdate** (to track auto-generation):
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Read source file/URL
 2. Identify document type (PRD, API spec, mockup, etc.)
 3. Extract features and requirements
@@ -121,7 +121,7 @@ As a new user, I want to register with my email...
 ROLE: Story Generator
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track auto-generation:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track auto-generation:
 ```
 1. Read source file/URL
 2. Identify document type (PRD, API spec, mockup, etc.)

package/src/core/commands/babysit.md

@@ -52,7 +52,7 @@ This gathers: git status, stories/epics, session state, docs structure, research
 **Key Rules:**
 1. ALWAYS end responses with `AskUserQuestion` tool (not text questions)
 2. Use `EnterPlanMode` before non-trivial implementation
-3. Use `TodoWrite` to track multi-step tasks
+3. Use `TaskCreate`/`TaskUpdate` to track multi-step tasks
 
 ---
 
@@ -312,9 +312,9 @@ Analysis/Review                   → /agileflow:multi-expert or Task(subagent_t
 
 ---
 
-### 🚨 RULE #4: TRACK PROGRESS WITH TodoWrite
+### 🚨 RULE #4: TRACK PROGRESS WITH Task Tools
 
-Use TodoWrite for any task with 3+ steps. Update status as you complete each step.
+Use TaskCreate for any task with 3+ steps. Use TaskUpdate to mark status as you complete each step.
 
 ---
 
@@ -345,7 +345,7 @@ These rules MUST be followed during implementation:
 1. **ALWAYS end your final response with AskUserQuestion tool** offering next steps
 2. **Use EnterPlanMode** if any NEW non-trivial tasks arise during implementation
 3. **Delegate complex work** to domain experts via Task tool
-4. **Track progress** with TodoWrite for multi-step work
+4. **Track progress** with TaskCreate/TaskUpdate for multi-step work
 
 After implementation completes, you MUST call AskUserQuestion with options like:
 - "Run tests to verify"
@@ -849,7 +849,7 @@ When stuck detection triggers:
    1. ALWAYS end your final response with AskUserQuestion tool
    2. Use EnterPlanMode if new non-trivial tasks arise
    3. Delegate complex work to domain experts
-   4. Track progress with TodoWrite
+   4. Track progress with TaskCreate/TaskUpdate
 
    After implementation, call AskUserQuestion with next step options.
 
@@ -973,18 +973,32 @@ Use AskUserQuestion at natural pause points (task completion, decision needed) b
 </invoke>
 ```
 
-### TodoWrite
+### Task Tools (TaskCreate, TaskUpdate, TaskList, TaskGet)
 
-**USE:** Track all workflow steps. Update as you complete.
+**USE:** Track all workflow steps. Create tasks with TaskCreate, update status with TaskUpdate.
 
 ```xml
-<invoke name="TodoWrite">
-<parameter name="todos">[
-  {"content": "Run context script", "status": "completed", "activeForm": "Running context"},
-  {"content": "Spawn database expert", "status": "in_progress", "activeForm": "Spawning expert"},
-  {"content": "Update status.json", "status": "pending", "activeForm": "Updating status"}
-]</parameter>
+<!-- Create a task -->
+<invoke name="TaskCreate">
+<parameter name="subject">Run context script</parameter>
+<parameter name="description">Gather project context using obtain-context.js</parameter>
+<parameter name="activeForm">Running context script</parameter>
 </invoke>
+
+<!-- Mark task in progress -->
+<invoke name="TaskUpdate">
+<parameter name="taskId">1</parameter>
+<parameter name="status">in_progress</parameter>
+</invoke>
+
+<!-- Mark task completed -->
+<invoke name="TaskUpdate">
+<parameter name="taskId">1</parameter>
+<parameter name="status">completed</parameter>
+</invoke>
+
+<!-- List all tasks -->
+<invoke name="TaskList"></invoke>
 ```
 
 ### Task (Spawn Expert)

package/src/core/commands/baseline.md

@@ -100,11 +100,11 @@ git checkout agileflow-baseline-20251222-143000
 - Compare current state to baseline with `/agileflow:verify`
 
 **Tools Used**:
-- TodoWrite: Track 8-step baseline creation workflow
+- TaskCreate/TaskUpdate: Track 8-step baseline creation workflow
 
-**TodoWrite Example**:
+**TaskCreate/TaskUpdate Example**:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">
 1. Run pre-flight checks (session harness, tests, git status, story tests)
 2. Show baseline summary (what will be included)
@@ -152,7 +152,7 @@ Create a baseline marker (git tag + metadata) when all tests are passing and the
 
 ## TODO LIST TRACKING
 
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track baseline creation:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track baseline creation:
 ```
 1. Run pre-flight checks (session harness, tests, git status, story tests)
 2. Show baseline summary (what will be included)

package/src/core/commands/ci.md

@@ -36,11 +36,11 @@ Bootstrap minimal CI workflow and CODEOWNERS.
 
 ---
 
-### 🚨 RULE #1: ALWAYS USE TodoWrite FOR TRACKING
+### 🚨 RULE #1: ALWAYS USE TaskCreate/TaskUpdate FOR TRACKING
 
 Track all 5 steps explicitly:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">
 1. Parse OWNERS input (required, comma-separated)
 2. Generate .github/workflows/ci.yml with 3 jobs
@@ -139,7 +139,7 @@ Both paths MUST include the parsed OWNERS.
 ✅ Include concurrency with cancel-in-progress
 ✅ Use minimal permissions (contents: read)
 ✅ Include both required path mappings
-✅ Track with TodoWrite for safety
+✅ Track with TaskCreate/TaskUpdate for safety
 
 ---
 
@@ -208,7 +208,7 @@ Next steps:
 - ALWAYS show diff-first before creating files
 - Include lint, typecheck, test jobs
 - Map both /src/ and /docs/03-decisions/ in CODEOWNERS
-- Use TodoWrite to track 5 steps
+- Use TaskCreate/TaskUpdate to track 5 steps
 - Display next steps for GitHub configuration
 
 <!-- COMPACT_SUMMARY_END -->
@@ -218,7 +218,7 @@ Next steps:
 ROLE: CI Bootstrapper
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track CI setup:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track CI setup:
 ```
 1. Parse input (OWNERS)
 2. Create .github/workflows/ci.yml with lint/typecheck/test jobs

package/src/core/commands/context/export.md

@@ -9,7 +9,7 @@ compact_context:
     - "OUTPUT LIMIT: ≤300 lines maximum for easy pasting into web AI tools"
     - "REQUIRED INPUT: docs/context.md must exist (run /agileflow:context:full first if missing)"
     - "EXTRACT ONLY: overview, focus, tech, decisions, features, next steps (skip progress, notes)"
-    - "NO TodoWrite needed - single-step read-only operation"
+    - "NO TaskCreate/TaskUpdate needed - single-step read-only operation"
   state_fields:
     - context_file_exists
     - output_line_count
@@ -285,7 +285,7 @@ Paste this excerpt into your web AI tool (ChatGPT, Perplexity, Gemini, etc.) to
 
 - **LIMIT**: ≤300 lines total output
 - **NO FILE WRITES**: This is read-only
-- **NO TodoWrite needed**: Simple single-step operation
+- **NO TaskCreate/TaskUpdate needed**: Simple single-step operation
 
 ---
 

package/src/core/commands/context/full.md

@@ -5,7 +5,7 @@ compact_context:
   priority: high
   preserve_rules:
     - "ACTIVE COMMAND: /agileflow:context:full - Generates docs/context.md for external AI tools"
-    - "ALWAYS create TodoWrite list for multi-step workflow tracking"
+    - "ALWAYS create TaskCreate/TaskUpdate list for multi-step workflow tracking"
     - "ALWAYS show diff BEFORE ANY file writes - wait for YES/NO confirmation"
     - "PRESERVE user-written content - only update sections between MANAGED_SECTION markers"
     - "REQUIRED SOURCES: status.json, bus/log.jsonl, epics, stories, ADRs, practices, architecture, CI, CHANGELOG"
@@ -56,12 +56,12 @@ node .agileflow/scripts/obtain-context.js context:full
 
 ---
 
-### 🚨 RULE #1: ALWAYS START WITH TodoWrite LIST
+### 🚨 RULE #1: ALWAYS START WITH TaskCreate/TaskUpdate LIST
 
-**Before ANY gathering, create TodoWrite to track workflow:**
+**Before ANY gathering, create TaskCreate/TaskUpdate to track workflow:**
 
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="todos">[
   {"content": "Read existing docs/context.md", "status": "in_progress", "activeForm": "Reading context file"},
   {"content": "Gather sources (status.json, bus, epics, ADRs, practices, architecture, CI, CHANGELOG)", "status": "pending", "activeForm": "Gathering sources"},
@@ -234,7 +234,7 @@ Upon invocation, execute these steps:
 ### Step 1: Create Todo List
 
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="todos">[
   {"content": "Read existing docs/context.md", "status": "in_progress", "activeForm": "Reading context file"},
   {"content": "Gather sources (status.json, bus, epics, ADRs)", "status": "pending", "activeForm": "Gathering sources"},

package/src/core/commands/deploy.md

@@ -121,11 +121,11 @@ Both workflows deploy automatically on push.
 
 ---
 
-### 🚨 RULE #6: USE TodoWrite FOR TRACKING
+### 🚨 RULE #6: USE TaskCreate/TaskUpdate FOR TRACKING
 
 Track all 8 steps explicitly:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">
 1. Detect project type
 2. Recommend platform
@@ -238,7 +238,7 @@ Secrets guide: docs/02-practices/secrets-management.md
 - ALWAYS show preview before creating files
 - Create BOTH staging and production (unless specified)
 - Create .env.example template (never commit actual secrets)
-- Use TodoWrite to track 8 steps
+- Use TaskCreate/TaskUpdate to track 8 steps
 - Display next steps with exact commands
 
 <!-- COMPACT_SUMMARY_END -->
@@ -248,7 +248,7 @@ Secrets guide: docs/02-practices/secrets-management.md
 ROLE: Deployment Pipeline Configurator
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track deployment setup:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track deployment setup:
 ```
 1. Detect project type (static, full-stack, mobile, containers, serverless)
 2. Recommend platform based on project type

package/src/core/commands/docs.md

@@ -191,9 +191,9 @@ Returns JWT token and user profile.
 
 ### TOOL USAGE EXAMPLES
 
-**TodoWrite** (to track sync process):
+**TaskCreate/TaskUpdate** (to track sync process):
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Get git diff between BASE and BRANCH
 2. Categorize changes (API, UI, services, config, DB)
 3. Map to expected documentation locations

package/src/core/commands/epic.md

@@ -5,7 +5,7 @@ compact_context:
   priority: high
   preserve_rules:
     - "ACTIVE COMMAND: /agileflow:epic-new - Epic creator for feature planning"
-    - "{{RULES:todo_tracking}}"
+    - "{{RULES:task_tracking}}"
     - "{{RULES:file_preview}}"
     - "{{RULES:json_operations}}"
     - "{{RULES:user_confirmation}}"
@@ -43,11 +43,11 @@ Create a new epic with optional child stories.
 
 ---
 
-### 🚨 RULE #1: ALWAYS Create TodoWrite Task List FIRST
+### 🚨 RULE #1: ALWAYS Create TaskCreate/TaskUpdate Task List FIRST
 
 Create a 6-step task list IMMEDIATELY:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Parse inputs (EPIC, TITLE, OWNER, GOAL, STORIES)
 2. Create epic file from template
 3. For each story: create docs/06-stories/<EPIC>/<US_ID>-<slug>.md
@@ -183,7 +183,7 @@ RESEARCH=<file>        # Research note filename (optional)
 - ALWAYS parse and validate STORIES input (triplet format)
 - ALWAYS preview before confirming (prevents mistakes)
 - ALWAYS validate JSON after merge (prevents corruption)
-- Use TodoWrite for step tracking (6 steps)
+- Use TaskCreate/TaskUpdate for step tracking (6 steps)
 - Files: epic file, N story files, status.json, bus/log.jsonl
 - **RESEARCH-FIRST**: For complex epics (3+ stories), validate research exists; suggest /agileflow:research:ask if missing
 
@@ -197,7 +197,7 @@ OBJECTIVE
 Analyze feature requirements and create structured epics with associated stories. Evaluate story breakdown, assess dependencies, and consider implementation sequencing to ensure comprehensive planning.
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track epic creation:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track epic creation:
 ```
 1. Parse inputs (EPIC, TITLE, OWNER, GOAL, STORIES)
 2. Create docs/05-epics/<EPIC>.md from template

package/src/core/commands/feedback.md

@@ -180,9 +180,9 @@ Suggested Story: "US-XXXX: Improve story template with AC examples"
 
 ### TOOL USAGE EXAMPLES
 
-**TodoWrite** (to track feedback process):
+**TaskCreate/TaskUpdate** (to track feedback process):
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Determine scope and required inputs
 2. Ask for feedback (optional)
 3. If YES: Show form with pre-filled context

package/src/core/commands/handoff.md

@@ -178,9 +178,9 @@ Fields:
 
 ### TOOL USAGE EXAMPLES
 
-**TodoWrite** (to track handoff creation):
+**TaskCreate/TaskUpdate** (to track handoff creation):
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Parse inputs (STORY, FROM, TO, SUMMARY, BLOCKERS)
 2. Generate handoff note from template
 3. Generate bus log JSON line
@@ -223,7 +223,7 @@ Fields:
 ROLE: Handoff Scribe
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track handoff documentation:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track handoff documentation:
 ```
 1. Parse inputs (STORY, FROM, TO, SUMMARY, BLOCKERS)
 2. Create docs/09-agents/comms/<STORY>-<YYYYMMDD>-handoff.md

package/src/core/commands/packages.md

@@ -5,7 +5,7 @@ compact_context:
   priority: high
   preserve_rules:
     - "Auto-detect package manager (npm, pip, cargo, etc.) from manifest files"
-    - "MUST use TodoWrite to track 8-step workflow (inputs, detect, analyze, generate, preview, confirm, apply, save)"
+    - "MUST use TaskCreate/TaskUpdate to track 8-step workflow (inputs, detect, analyze, generate, preview, confirm, apply, save)"
     - "ALWAYS show diff-first before applying updates (YES/NO confirmation)"
     - "Prioritize security updates - run ACTION=audit first if vulnerabilities suspected"
     - "For major updates: Create stories, don't auto-update (may require code changes)"
@@ -71,11 +71,11 @@ node .agileflow/scripts/obtain-context.js packages
 - **Related**: Security audits, CI integration, Dependabot config
 
 **Tools Used**:
-- TodoWrite: Track 8-step dependency management workflow
+- TaskCreate/TaskUpdate: Track 8-step dependency management workflow
 
-**TodoWrite Example**:
+**TaskCreate/TaskUpdate Example**:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">
 1. Parse inputs (ACTION, SCOPE, OUTPUT, INCLUDE_DEV, SAVE_TO, AUTO_PR)
 2. Detect package manager(s) (npm, pip, cargo, etc.)
@@ -99,7 +99,7 @@ node .agileflow/scripts/obtain-context.js packages
 ROLE: Package Dependency Manager
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track package management:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track package management:
 ```
 1. Parse inputs (ACTION, SCOPE, OUTPUT, INCLUDE_DEV, SAVE_TO, AUTO_PR)
 2. Detect package manager(s) (npm, pip, cargo, etc.)

package/src/core/commands/pr.md

@@ -155,9 +155,9 @@ Suggest a commit message following conventional format:
 
 ### TOOL USAGE EXAMPLES
 
-**TodoWrite** (to track PR generation):
+**TaskCreate/TaskUpdate** (to track PR generation):
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Parse inputs (STORY, TITLE, AC_CHECKED, TEST_EVIDENCE, NOTES)
 2. Read story file from docs/06-stories/
 3. Extract: epic, summary, deps, AC
@@ -206,7 +206,7 @@ Generate a complete PR description from story and test evidence.
 ROLE: PR Author
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track PR description generation:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track PR description generation:
 ```
 1. Parse inputs (STORY, TITLE, AC_CHECKED, TEST_EVIDENCE, NOTES)
 2. Read story file to extract epic/summary/deps

package/src/core/commands/research/analyze.md

@@ -340,7 +340,7 @@ Upon invocation, execute these steps:
 ### Step 1: Create Todo List
 
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="todos">[
   {"content": "Select research note", "status": "in_progress", "activeForm": "Selecting research"},
   {"content": "Assess file and display research summary", "status": "pending", "activeForm": "Showing summary"},

package/src/core/commands/research/ask.md

@@ -396,7 +396,7 @@ Upon invocation, execute these steps:
 ### Step 1: Create Todo List
 
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="todos">[
   {"content": "Gather codebase context", "status": "in_progress", "activeForm": "Gathering context"},
   {"content": "Extract relevant code snippets", "status": "pending", "activeForm": "Extracting code"},

package/src/core/commands/research/import.md

@@ -464,7 +464,7 @@ Upon invocation, execute these steps:
 ### Step 1: Create Todo List
 
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="todos">[
   {"content": "Validate TOPIC and CONTENT", "status": "in_progress", "activeForm": "Validating inputs"},
   {"content": "Analyze and summarize content", "status": "pending", "activeForm": "Analyzing content"},

package/src/core/commands/research/synthesize.md

@@ -310,7 +310,7 @@ Upon invocation, execute these steps:
 ### Step 1: Create Todo List
 
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="todos">[
   {"content": "Validate TOPIC or FILES input", "status": "in_progress", "activeForm": "Validating inputs"},
   {"content": "Search/select research files", "status": "pending", "activeForm": "Selecting files"},

package/src/core/commands/retro.md

@@ -6,7 +6,7 @@ compact_context:
   priority: medium
   preserve_rules:
     - "ACTIVE COMMAND: /agileflow:retro - Retrospective facilitator (read-only analysis)"
-    - "{{RULES:todo_tracking}}"
+    - "{{RULES:task_tracking}}"
     - "MUST focus on TEAM-LEVEL patterns (never individual blame)"
     - "MUST balance positive (Continue) with improvements (Start/Stop)"
     - "MUST use DATA to drive insights (no opinions without evidence)"
@@ -44,11 +44,11 @@ Automated retrospective generator that analyzes patterns and surfaces insights f
 
 ---
 
-### 🚨 RULE #1: ALWAYS Create TodoWrite Task List FIRST
+### 🚨 RULE #1: ALWAYS Create TaskCreate/TaskUpdate Task List FIRST
 
 Create 9-step task list immediately:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Load data sources (bus/log.jsonl, status.json, stories, velocity)
 2. Analyze what went well (velocity, cycles, completions, estimation)
 3. Analyze improvements (velocity drops, cycles, WIP, blockers)
@@ -159,7 +159,7 @@ After displaying retrospective:
 ## REMEMBER AFTER COMPACTION
 
 - Command is read-only (analyzes data, no updates)
-- Creates 9-step TodoWrite task list (tracks progress)
+- Creates 9-step TaskCreate/TaskUpdate task list (tracks progress)
 - Focuses on TEAM-LEVEL patterns (never individual blame)
 - Balances Continue/Start/Stop with data evidence
 - Generates retrospective report with Start/Stop/Continue format
@@ -175,7 +175,7 @@ After displaying retrospective:
 ROLE: Retrospective Facilitator
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track retrospective generation:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track retrospective generation:
 ```
 1. Load data sources (bus/log.jsonl, status.json, story data, velocity data)
 2. Analyze what went well (velocity, cycle time, epic completion, estimation)

package/src/core/commands/review.md

@@ -182,9 +182,9 @@ Include:
 
 ### TOOL USAGE EXAMPLES
 
-**TodoWrite** (to track review progress):
+**TaskCreate/TaskUpdate** (to track review progress):
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Get git diff between BASE and BRANCH
 2. Analyze code for 6 categories
 3. Identify issues and prioritize by severity

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

@@ -62,7 +62,7 @@ At least one of `--count`, `--branches`, or `--from-epic` is required.
 ### Step 2: Create Todo List
 
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="todos">[
   {"content": "Validate arguments", "status": "in_progress", "activeForm": "Validating arguments"},
   {"content": "Create parallel sessions", "status": "pending", "activeForm": "Creating sessions"},

package/src/core/commands/sprint.md

@@ -6,7 +6,7 @@ compact_context:
   priority: critical
   preserve_rules:
     - "ACTIVE COMMAND: /agileflow:sprint-plan - Sprint planner with capacity analysis"
-    - "{{RULES:todo_tracking}}"
+    - "{{RULES:task_tracking}}"
     - "MUST calculate historical velocity from last 30 days (bus/log.jsonl)"
     - "MUST respect WIP limits (max 2 in-progress per agent)"
     - "MUST validate dependencies resolved (only select stories with all deps status=done)"
@@ -29,7 +29,7 @@ This section is extracted by the PreCompact hook to preserve essential context a
 Sprint Planner that creates data-driven sprint commitments based on historical velocity, agent capacity, and dependency validation.
 
 ### Critical Behavioral Rules
-- **ALWAYS create a TodoWrite list** with 8 steps before starting sprint planning
+- **ALWAYS create a TaskCreate/TaskUpdate list** with 8 steps before starting sprint planning
 - **Load knowledge sources silently first** (status.json, bus/log.jsonl, backlog.md, roadmap.md, milestones.md, epics, stories)
 - **Calculate historical velocity** from last 30 days of completed stories in bus/log.jsonl before selecting stories
 - **Respect WIP limits**: Max 2 stories in-progress per agent
@@ -80,9 +80,9 @@ Sprint Planner that creates data-driven sprint commitments based on historical v
 
 **Tool Usage Examples**:
 
-TodoWrite:
+TaskCreate/TaskUpdate:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Load knowledge sources (status.json, bus log, backlog)
 2. Analyze agent capacity and WIP
 3. Calculate historical velocity (last 30 days)
@@ -130,7 +130,7 @@ This gathers git status, stories/epics, session state, and registers for PreComp
 ROLE: Sprint Planner
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track sprint planning:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track sprint planning:
 ```
 1. Load knowledge sources (status.json, bus/log.jsonl, backlog, roadmap, epics, stories)
 2. Analyze current state (agent capacity, backlog health)

package/src/core/commands/story-validate.md

@@ -70,9 +70,9 @@ node .agileflow/scripts/obtain-context.js story-validate
 
 **Tool Usage Examples**:
 
-TodoWrite:
+TaskCreate/TaskUpdate:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Parse story ID from input
 2. Load story file from docs/06-stories/
 3. Parse YAML frontmatter and extract sections
@@ -108,7 +108,7 @@ AskUserQuestion:
 ROLE: Story Validator
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track story validation:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track story validation:
 ```
 1. Parse story ID from input or ask user
 2. Load story file from docs/06-stories/

package/src/core/commands/story.md

@@ -5,7 +5,7 @@ compact_context:
   priority: high
   preserve_rules:
     - "ACTIVE COMMAND: /agileflow:story-new - Story creator with acceptance criteria"
-    - "{{RULES:todo_tracking}}"
+    - "{{RULES:task_tracking}}"
     - "{{RULES:file_preview}}"
     - "{{RULES:json_operations}}"
     - "{{RULES:user_confirmation}}"
@@ -46,11 +46,11 @@ node .agileflow/scripts/obtain-context.js story
 
 ---
 
-### 🚨 RULE #1: ALWAYS Create TodoWrite Task List FIRST
+### 🚨 RULE #1: ALWAYS Create TaskCreate/TaskUpdate Task List FIRST
 
 Create a task list IMMEDIATELY (7 steps if TDD=true, 6 steps otherwise):
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Parse inputs (EPIC, STORY, TITLE, OWNER, ESTIMATE, AC)
 2. Create story file from template
 3. Create test case stub
@@ -246,7 +246,7 @@ TDD=true|false             # TDD mode (smart default: true for code owners, fals
 - ALWAYS create test stub referencing AC
 - ALWAYS preview before confirming (prevents mistakes)
 - ALWAYS validate JSON after merge (prevents corruption)
-- Use TodoWrite for step tracking (6 steps, or 7 if TDD=true)
+- Use TaskCreate/TaskUpdate for step tracking (6 steps, or 7 if TDD=true)
 - Files: story file, test file, status.json, bus/log.jsonl
 - **TDD=true**: Also create framework-specific test code in `__tests__/` with pending tests
 
@@ -272,7 +272,7 @@ ROLE: Story Creator
 ```
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track story creation:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track story creation:
 ```
 1. Parse inputs (EPIC, STORY, TITLE, OWNER, ESTIMATE, DEPENDENCIES, AC)
 2. Create docs/06-stories/<EPIC>/<STORY>-<slug>.md from template

package/src/core/commands/tests.md

@@ -5,7 +5,7 @@ compact_context:
   priority: high
   preserve_rules:
     - "Auto-detect language/runtime and testing framework (Node.js→Jest, Python→pytest, Ruby→RSpec, etc.)"
-    - "MUST use TodoWrite to track all 10 steps (detect, check existing, install, config, examples, structure, scripts, CI, docs, run)"
+    - "MUST use TaskCreate/TaskUpdate to track all 10 steps (detect, check existing, install, config, examples, structure, scripts, CI, docs, run)"
     - "Always show diff-first preview before creating files"
     - "Create working example tests (unit, integration, E2E if requested) - not just config"
     - "Set reasonable coverage thresholds (70%, not 100%)"
@@ -43,11 +43,11 @@ node .agileflow/scripts/obtain-context.js tests
 
 ---
 
-### 🚨 RULE #1: ALWAYS USE TodoWrite FOR 10 STEPS
+### 🚨 RULE #1: ALWAYS USE TaskCreate/TaskUpdate FOR 10 STEPS
 
 Track all steps explicitly:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">
 1. Detect language/runtime and framework
 2. Check existing test setup
@@ -264,7 +264,7 @@ tests/
 - ALWAYS create working example tests (not just config)
 - Set reasonable coverage (70%, not 100%)
 - Run tests after setup to verify they pass
-- Use TodoWrite to track 10 steps
+- Use TaskCreate/TaskUpdate to track 10 steps
 - Integrate with CI immediately
 - Create docs/02-practices/testing.md
 
@@ -290,7 +290,7 @@ ACTIONS
 8) Run tests to verify setup
 
 TODO LIST TRACKING
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track test infrastructure setup:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track test infrastructure setup:
 ```
 1. Detect language/runtime and framework
 2. Check existing test setup

package/src/core/commands/verify.md

@@ -89,9 +89,9 @@ This gathers git status, stories/epics, session state, and registers for PreComp
 
 **Tool Usage Examples**:
 
-TodoWrite:
+TaskCreate/TaskUpdate:
 ```xml
-<invoke name="TodoWrite">
+<invoke name="TaskCreate/TaskUpdate">
 <parameter name="content">1. Run pre-flight checks (session harness initialized)
 2. Load test configuration from environment.json
 3. Execute test command with timeout
@@ -135,7 +135,7 @@ Execute project tests and update `test_status` for stories in `docs/09-agents/st
 
 ## TODO LIST TRACKING
 
-**CRITICAL**: Immediately create a todo list using TodoWrite tool to track test verification:
+**CRITICAL**: Immediately create a todo list using TaskCreate/TaskUpdate tool to track test verification:
 ```
 1. Run pre-flight checks (session harness initialized)
 2. Load configuration from docs/00-meta/environment.json

package/src/core/templates/preserve-rules-common.md

@@ -43,12 +43,12 @@ Rules for using AskUserQuestion tool
 - "Options: YES to confirm, NO to cancel, or specific choices"
 ```
 
-### todo_tracking
-Rules for using TodoWrite tool
+### task_tracking
+Rules for using Task management tools (TaskCreate, TaskUpdate, TaskList, TaskGet)
 
 ```
-- "MUST create TodoWrite task list for 3+ step workflows"
-- "Mark tasks in_progress before starting, completed when done"
+- "MUST use TaskCreate for 3+ step workflows, TaskUpdate to mark progress"
+- "Set status: in_progress when starting, completed when done"
 ```
 
 ### bus_messaging

package/src/core/templates/preserve-rules.json

@@ -11,9 +11,9 @@
     "MUST use AskUserQuestion tool for user decisions (not text prompts)",
     "Options: YES to confirm, NO to cancel, or specific choices"
   ],
-  "todo_tracking": [
-    "MUST create TodoWrite task list for 3+ step workflows",
-    "Mark tasks in_progress before starting, completed when done"
+  "task_tracking": [
+    "MUST use TaskCreate for 3+ step workflows, TaskUpdate to mark progress",
+    "Set status: in_progress when starting, completed when done"
   ],
   "bus_messaging": [
     "MUST append status update to docs/09-agents/bus/log.jsonl",

package/tools/cli/lib/content-injector.js

@@ -721,7 +721,7 @@ function getPlaceholderDocs() {
       '{{RULES:json_operations}}': 'Rules for safe JSON file modifications',
       '{{RULES:file_preview}}': 'Rules for showing previews before writing',
       '{{RULES:user_confirmation}}': 'Rules for using AskUserQuestion tool',
-      '{{RULES:todo_tracking}}': 'Rules for using TodoWrite tool',
+      '{{RULES:task_tracking}}': 'Rules for using TaskCreate/TaskUpdate tool',
       '{{RULES:bus_messaging}}': 'Rules for bus message logging',
       '{{RULES:plan_mode}}': 'Rules for using EnterPlanMode',
       '{{RULES:commit_approval}}': 'Rules about git commits',