Back to Planning With Files

Troubleshooting

docs/troubleshooting.md

3.12.06.4 KB
Original Source

Troubleshooting

Common issues and their solutions.


Templates not found in cache (after update)

Issue: After updating to a new version, /planning-with-files fails with "template files not found in cache" or similar errors.

Why this happens: Claude Code caches plugin files, and the cache may not refresh properly after an update.

Solutions:

bash
/plugin uninstall planning-with-files@planning-with-files
/plugin marketplace add OthmanAdi/planning-with-files
/plugin install planning-with-files@planning-with-files

Solution 2: Inspect the installed plugin

Use claude plugin list and claude plugin details to inspect the installed version and components. Claude Code manages installed files under ~/.claude/plugins/cache/; do not edit the cached copy in place.

Restart Claude Code completely after reinstalling.

Note: This was fixed in v2.1.2 by adding templates at the repo root level.


Planning files created in wrong directory

Issue: When using /planning-with-files, the files (task_plan.md, findings.md, progress.md) are created in the skill installation directory instead of your project.

Why this happens: When the skill runs as a subagent, it may not inherit your terminal's current working directory.

Solutions:

Solution 1: Specify your project path when invoking

/planning-with-files - I'm working in /path/to/my-project/, create all files there

Solution 2: Add context before invoking

I'm working on the project at /path/to/my-project/

Then run /planning-with-files.

Solution 3: Create a CLAUDE.md in your project root

markdown
# Project Context

All planning files (task_plan.md, findings.md, progress.md)
should be created in this directory.

Solution 4: Use the skill directly without subagent

Help me plan this task using the planning-with-files approach.
Create task_plan.md, findings.md, and progress.md here.

Note: This was fixed in v2.0.1. The skill instructions now explicitly specify that planning files should be created in your project directory, not the skill installation folder.


Files not persisting between sessions

Issue: Planning files seem to disappear or aren't found when resuming work.

Solution: Make sure the files are in your project root, not in a temporary location.

Check with:

bash
ls -la task_plan.md findings.md progress.md

If files are missing, they may have been created in:

  • The skill installation folder (~/.claude/skills/planning-with-files/)
  • A temporary directory
  • A different working directory

Hooks not triggering

Issue: The PreToolUse hook (which reads task_plan.md before actions) doesn't seem to run.

Solution:

  1. Use the current stable Claude Code release:

    bash
    claude --version
    

    Full lifecycle support is tested against current stable Claude Code. This project does not claim an older minimum without a compatibility receipt.

  2. Verify the installation route:

    bash
    claude plugin list
    

    For a standalone skill install:

    bash
    ls ~/.claude/skills/planning-with-files/
    
  3. Check that an active plan exists: The hooks resolve .planning/.active_plan first and fall back to legacy task_plan.md. If no plan exists, they stay silent by design.

  4. Inspect hook ownership: Plugin installs register hooks/hooks.json at startup. Standalone skill hooks register only after /planning-with-files is invoked for that session. Use /hooks and Claude debug logs to confirm that only the intended route is active.

  5. Check for configuration errors: Run Claude Code with debug mode:

    bash
    claude --debug
    

    Look for skill loading errors.


SessionStart hook appears silent

Issue: No planning-with-files message appears when starting Claude Code.

Solution:

  1. Silence is correct when no active plan exists.
  2. SessionStart is a plugin-route feature; standalone skill installs do not register it.
  3. With an active plan, inspect /hooks and the debug log to confirm the plugin descriptor was trusted and loaded from the installed cache.
  4. If the session was already open before installation or update, start a new Claude Code session.

PostToolUse hook not running

Issue: The reminder message after Write/Edit doesn't appear.

Solution:

  1. Confirm the plugin descriptor is trusted in /hooks, or invoke the standalone skill first.
  2. The hook fires only after a matched successful tool operation.
  3. Confirm only one installation route owns the hooks to avoid duplicate reminders.

Skill not auto-detecting complex tasks

Issue: Claude doesn't automatically use the planning pattern for complex tasks.

Solution:

  1. Manually invoke:

    /planning-with-files
    
  2. Trigger words: The skill auto-activates based on its description. Try phrases like:

    • "complex multi-step task"
    • "research project"
    • "task requiring many steps"
  3. Be explicit:

    This is a complex task that will require >5 tool calls.
    Please use the planning-with-files pattern.
    

Stop hook blocking completion

Issue: Claude won't stop because the Stop hook says phases aren't complete.

Solution:

  1. Check task_plan.md: All phases should have **Status:** complete

  2. Manual override: If you need to stop anyway:

    Override the completion check - I want to stop now.
    
  3. Fix the status: Update incomplete phases to complete if they're actually done.


YAML frontmatter errors

Issue: Skill won't load due to YAML errors.

Solution:

  1. Check indentation: YAML requires spaces, not tabs
  2. Check the first line: Must be exactly --- with no blank lines before it
  3. Validate YAML: Use an online YAML validator

Common mistakes:

yaml
# WRONG - tabs
hooks:
	PreToolUse:

# CORRECT - spaces
hooks:
  PreToolUse:

Windows-specific issues

See docs/windows.md for Windows-specific troubleshooting.


Cursor-specific issues

See docs/cursor.md for Cursor IDE troubleshooting.


Still stuck?

Open an issue at github.com/OthmanAdi/planning-with-files/issues with:

  • Your Claude Code version (claude --version)
  • Your operating system
  • The command you ran
  • What happened vs what you expected
  • Any error messages