feat: plan-to-goal capture via ExitPlanMode PostToolUse hook

When a plan is approved (ExitPlanMode) and an active goal exists,
the hook parses the plan's numbered steps and nudges Claude to add
them as goal steps, ensuring plan work persists across sessions.

Co-developed-by: Claude Code v2.1.50 (claude-opus-4-6)

Author: robtaylor

.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
       "name": "context-daddy",
       "source": "./",
       "description": "Your codebase's context needs a responsible adult. Fast code exploration, living project narratives, and tribal knowledge that survives across sessions.",
-      "version": "0.14.5",
+      "version": "0.14.6",
       "author": {
         "name": "Robert Taylor"
       },

.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "context-daddy",
-  "version": "0.14.5",
+  "version": "0.14.6",
   "description": "Your codebase's context needs a responsible adult. Fast code exploration, living project narratives, and tribal knowledge that survives across sessions.",
   "author": {
     "name": "Robert Taylor"

CHANGELOG.md

@@ -5,6 +5,11 @@ All notable changes to the context-tools plugin will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.14.6] - 2026-03-02
+
+### Added
+- **Plan-to-goal capture** - PostToolUse hook on ExitPlanMode detects approved plan steps and nudges Claude to add them as goal steps, ensuring plan work persists across sessions
+
 ## [0.14.5] - 2026-03-02
 
 ### Added

hooks/hooks.json

@@ -102,6 +102,15 @@
             "command": "${CLAUDE_PLUGIN_ROOT}/hooks/goals-post-tool.sh"
           }
         ]
+      },
+      {
+        "matcher": "ExitPlanMode",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "${CLAUDE_PLUGIN_ROOT}/hooks/plan-capture.sh"
+          }
+        ]
       }
     ],
     "PreToolUse": [

hooks/plan-capture.sh

@@ -0,0 +1,76 @@
+#!/usr/bin/env bash
+# PostToolUse hook for ExitPlanMode
+# When a plan is approved and an active goal exists, nudges Claude to
+# capture the plan's steps as goal steps so they persist across sessions.
+set -euo pipefail
+
+SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/../scripts" && pwd)"
+PROJECT_ROOT="${PWD}"
+CLAUDE_DIR="${PROJECT_ROOT}/.claude"
+CURRENT_GOAL_FILE="${CLAUDE_DIR}/.current-goal"
+PLANS_DIR="${HOME}/.claude/plans"
+
+# Quick exit if no active goal or no plans directory
+if [[ ! -f "${CURRENT_GOAL_FILE}" ]] || [[ ! -d "${PLANS_DIR}" ]]; then
+    echo '{}'
+    exit 0
+fi
+
+# Find the most recently modified plan file (modified in the last 60 seconds)
+PLAN_FILE=$(find "${PLANS_DIR}" -name '*.md' -not -name '*.backup-*' -mmin -1 -print0 2>/dev/null \
+    | xargs -0 ls -t 2>/dev/null \
+    | head -1)
+
+if [[ -z "${PLAN_FILE}" ]]; then
+    echo '{}'
+    exit 0
+fi
+
+# Extract numbered steps from the plan (### N. Title pattern)
+# Also handles ## Changes / ### N. Title patterns
+export _PC_PLAN_FILE="${PLAN_FILE}"
+STEPS=$(python3 -c '
+import os
+import re
+from pathlib import Path
+
+plan_file = os.environ["_PC_PLAN_FILE"]
+content = Path(plan_file).read_text()
+
+steps = []
+for m in re.finditer(r"^###\s+(\d+)\.\s+(.+)$", content, re.MULTILINE):
+    num = m.group(1)
+    title = m.group(2).strip()
+    # Clean up markdown formatting from title
+    title = re.sub(r"`([^`]+)`", r"\1", title)
+    # Truncate long titles
+    if len(title) > 80:
+        title = title[:77] + "..."
+    steps.append(f"  {num}. {title}")
+
+if steps:
+    print("\n".join(steps))
+' 2>/dev/null || true)
+
+if [[ -z "${STEPS}" ]]; then
+    echo '{}'
+    exit 0
+fi
+
+# Get current goal info for the message
+GOAL_STATUS=$(bash "${SCRIPT_DIR}/goal-context-helper.sh" --status "${PROJECT_ROOT}" 2>/dev/null || true)
+
+# Build the nudge message
+MSG="📋 Plan approved with steps that should be tracked in your active goal.
+
+Plan steps detected:
+${STEPS}
+
+**ACTION**: Use goal_add_step to add these as goal steps (skip any that duplicate existing steps). Use short kebab-case step IDs derived from the titles."
+
+MSG_ESCAPED=$(echo -n "${MSG}" | python3 -c "import sys,json; print(json.dumps(sys.stdin.read()))" | sed 's/^"//;s/"$//')
+cat << EOF
+{
+  "systemMessage": "${MSG_ESCAPED}"
+}
+EOF

scripts/goal-context-helper.sh

@@ -200,7 +200,7 @@ lines.append("   Commands: /context-daddy:goal (manage) | /context-daddy:goal-do
 # Behavioral guidance
 lines.append("")
 lines.append("   **IMPORTANT - Goal-driven workflow:**")
-lines.append("   - When the user asks for a large multi-step task, use the goal system (goal_create + goal_add_step) instead of EnterPlanMode.")
+lines.append("   - When the user asks for a large multi-step task, prefer the goal system (goal_create + goal_add_step) over EnterPlanMode. If you do use EnterPlanMode, the plan steps will be auto-captured as goal steps.")
 lines.append("   - After completing a step, use goal_update_step to mark it done, then CONTINUE to the next step without waiting to be asked.")
 lines.append("   - Only stop between steps if you need user input or clarification.")
 lines.append("   - To reorder or remove steps: edit the goal file directly (rearrange/delete the `- [ ] [step-id]` lines). Step IDs, not positions, identify steps.")