spacehub

surshar / claude-code

Claude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.

Built by Anthropic · github.com/anthropics

Add plan-auto-show plugin to display plan after updatesBrowse files
When in plan mode, users couldn't see the plan without typing /plan,
but they also couldn't type /plan while being asked follow-up questions.

This plugin adds a SessionStart hook that instructs Claude to
automatically display the plan content after updating the plan file,
showing it before any follow-up questions.

Fixes the UX issue where users need to answer questions about a plan
they can't see.
Claude authored on Dec 15, 2025 parent eb87245 · commit 4ffa4f07ffe4
3 changed files+75 -0compared with eb87245
Aplugins/plan-auto-show/README.md
Aplugins/plan-auto-show/hooks/session-start.sh
Aplugins/plan-auto-show/settings.json
@@ -1,0 +1,45 @@
1+# Plan Auto-Show Plugin
2+
3+Automatically displays the plan content when it's updated in plan mode, eliminating the need to type `/plan` to preview changes.
4+
5+## Problem
6+
7+When in plan mode, Claude updates the plan file and may ask follow-up questions. Users can't see the plan without typing `/plan`, but they also can't type `/plan` while being asked questions - they need to respond to the questions first.
8+
9+## Solution
10+
11+This plugin instructs Claude to automatically display the plan content in its response whenever it updates the plan file. The plan is shown before any follow-up questions, giving users the context they need to answer.
12+
13+## Installation
14+
15+1. Enable the plugin in your Claude Code settings
16+2. The SessionStart hook will automatically add instructions for plan auto-display
17+
18+## How It Works
19+
20+The plugin adds a SessionStart hook that provides additional context to Claude:
21+- After updating the plan file, Claude will display the full plan content
22+- The plan is shown in a markdown code block
23+- The plan appears before any follow-up questions
24+
25+## Example
26+
27+Before this plugin:
28+```
29+Claude: I've updated the plan file. Would you prefer approach A or B?
30+User: (Can't see the plan without typing /plan, but needs to answer the question)
31+```
32+
33+After this plugin:
34+```
35+Claude: I've updated the plan file:
36+
37+## Current Plan
38+1. Implement feature X
39+2. Add tests
40+3. Deploy
41+
42+Would you prefer approach A or B?
43+
44+User: (Can see the plan and answer the question)
45+```
@@ -1,0 +1,15 @@
1+#!/usr/bin/env bash
2+
3+# Auto-show plan content after updates in plan mode
4+# This hook adds instructions to automatically display the plan when updated
5+
6+cat << 'EOF'
7+{
8+ "hookSpecificOutput": {
9+ "hookEventName": "SessionStart",
10+ "additionalContext": "## Plan Mode Auto-Display\n\nWhen you are in plan mode and you update the plan file:\n\n1. After writing or editing the plan file, ALWAYS display the full plan content in a markdown code block in your response\n2. Use the format:\n ```markdown\n ## Current Plan\n [full plan content here]\n ```\n3. This ensures the user can see the plan without needing to run `/plan`, which is especially important when you're asking follow-up questions\n4. Show the plan BEFORE asking any clarifying questions, so the user has context for their answers\n\nThis improves the user experience by making the plan visible immediately after updates, without requiring separate commands."
11+ }
12+}
13+EOF
14+
15+exit 0
@@ -1,0 +1,15 @@
1+{
2+ "hooks": {
3+ "SessionStart": [
4+ {
5+ "matcher": "*",
6+ "hooks": [
7+ {
8+ "type": "command",
9+ "command": "bash ${CLAUDE_PLUGIN_ROOT}/hooks/session-start.sh"
10+ }
11+ ]
12+ }
13+ ]
14+ }
15+}