fix(mastra): add hooks.json, fix SKILL.md path var, correct docs

Mastra Code reads hooks from .mastracode/hooks.json, not SKILL.md frontmatter. All three hooks (PreToolUse, PostToolUse, Stop) were silently non-functional. Added hooks.json with proper Mastra format including matchers and timeouts. Fixed MASTRACODE_SKILL_ROOT env var (does not exist in Mastra Code). Corrected docs/mastra.md to accurately describe the hooks.json system and fixed personal install instructions to include the hooks file.
fix: stretch Star History chart to full width
2026-02-26 19:43:46 +01:00 · 2026-02-26 19:01:16 +01:00 · 2026-02-26 18:59:05 +01:00 · 2026-02-26 18:45:54 +01:00 · 2026-02-25 23:34:16 +01:00 · 2026-02-25 21:22:31 +01:00
39 changed files with 2249 additions and 292 deletions
@@ -1,6 +1,6 @@
 ---
 name: planning-with-files
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 ---

 # Planning with Files
@@ -1,6 +1,6 @@
 ---
 name: planning-with-files
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 license: MIT
 ---

@@ -1,6 +1,6 @@
 {
  "name": "planning-with-files",
-  "version": "2.11.0",
+  "version": "2.17.0",
  "description": "Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Works with Claude Code, Kiro, Clawd CLI, Gemini CLI, Cursor, Continue, and 11+ AI coding assistants.",
  "author": {
    "name": "OthmanAdi",
@@ -1,17 +1,8 @@
 ---
 name: planning-with-files
-version: "2.10.0"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 user-invocable: true
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - WebFetch
-  - WebSearch
+allowed-tools: "Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch"
 hooks:
  PreToolUse:
    - matcher: "Write|Edit|Bash|Read|Glob|Grep"
@@ -51,6 +42,8 @@ hooks:
            else
              sh "$SCRIPT_DIR/check-complete.sh"
            fi
+metadata:
+  version: "2.16.1"
 ---

 # Planning with Files
@@ -1,17 +1,8 @@
 ---
 name: planning-with-files
-version: "2.10.0"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 user-invocable: true
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - WebFetch
-  - WebSearch
+allowed-tools: "Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch"
 hooks:
  PreToolUse:
    - matcher: "Write|Edit|Bash|Read|Glob|Grep"
@@ -51,6 +42,8 @@ hooks:
            else
              sh "$SCRIPT_DIR/check-complete.sh"
            fi
+metadata:
+  version: "2.16.1"
 ---

 # Planning with Files
@@ -1,7 +1,8 @@
 ---
 name: planning-with-files
-version: "2.10.0"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
+metadata:
+  version: "2.16.1"
 ---

 # Planning with Files
@@ -1,17 +1,8 @@
 ---
 name: planning-with-files
-version: "2.10.0"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 user-invocable: true
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - WebFetch
-  - WebSearch
+allowed-tools: "Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch"
 hooks:
  PreToolUse:
    - matcher: "Write|Edit|Bash|Read|Glob|Grep"
@@ -51,6 +42,8 @@ hooks:
            else
              sh "$SCRIPT_DIR/check-complete.sh"
            fi
+metadata:
+  version: "2.16.1"
 ---

 # Planning with Files
@@ -1,6 +1,6 @@
 ---
 name: planning-with-files
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 ---

 # Planning with Files
@@ -1,6 +1,6 @@
 ---
 name: planning-with-files
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 ---

 # Planning with Files
@@ -4,8 +4,8 @@
 # Always exits 0 — outputs JSON to stdout.

 # Read stdin (required — Copilot pipes JSON to stdin)
-$OutputEncoding = [System.Text.Encoding]::UTF8
-[Console]::OutputEncoding = [System.Text.Encoding]::UTF8
+$OutputEncoding = [System.Text.UTF8Encoding]::new($false)
+[Console]::OutputEncoding = [System.Text.UTF8Encoding]::new($false)
 $InputData = [Console]::In.ReadToEnd()

 $PlanFile = "task_plan.md"
@@ -15,7 +15,7 @@ if (-not (Test-Path $PlanFile)) {
    exit 0
 }

-$content = Get-Content $PlanFile -Raw
+$content = Get-Content $PlanFile -Raw -Encoding UTF8

 # Count total phases
 $TOTAL = ([regex]::Matches($content, "### Phase")).Count
@@ -4,8 +4,8 @@
 # Always exits 0 — outputs JSON to stdout.

 # Read stdin (required — Copilot pipes JSON to stdin)
-$OutputEncoding = [System.Text.Encoding]::UTF8
-[Console]::OutputEncoding = [System.Text.Encoding]::UTF8
+$OutputEncoding = [System.Text.UTF8Encoding]::new($false)
+[Console]::OutputEncoding = [System.Text.UTF8Encoding]::new($false)
 $InputData = [Console]::In.ReadToEnd()

 $PlanFile = "task_plan.md"
@@ -15,7 +15,7 @@ if (-not (Test-Path $PlanFile)) {
    exit 0
 }

-$Context = (Get-Content $PlanFile -TotalCount 30 -ErrorAction SilentlyContinue) -join "`n"
+$Context = (Get-Content $PlanFile -TotalCount 30 -Encoding UTF8 -ErrorAction SilentlyContinue) -join "`n"

 if (-not $Context) {
    Write-Output '{"hookSpecificOutput":{"hookEventName":"PreToolUse","permissionDecision":"allow"}}'
@@ -4,8 +4,8 @@
 # Always exits 0 — outputs JSON to stdout.

 # Read stdin (required — Copilot pipes JSON to stdin)
-$OutputEncoding = [System.Text.Encoding]::UTF8
-[Console]::OutputEncoding = [System.Text.Encoding]::UTF8
+$OutputEncoding = [System.Text.UTF8Encoding]::new($false)
+[Console]::OutputEncoding = [System.Text.UTF8Encoding]::new($false)
 $InputData = [Console]::In.ReadToEnd()

 $PlanFile = "task_plan.md"
@@ -26,12 +26,12 @@ if (Test-Path $PlanFile) {
    if ($Catchup) {
        $Context = $Catchup -join "`n"
    } else {
-        $Context = (Get-Content $PlanFile -TotalCount 5 -ErrorAction SilentlyContinue) -join "`n"
+        $Context = (Get-Content $PlanFile -TotalCount 5 -Encoding UTF8 -ErrorAction SilentlyContinue) -join "`n"
    }
 } else {
    # No plan yet — inject SKILL.md so Copilot knows the planning workflow and templates
    if (Test-Path "$SkillDir/SKILL.md") {
-        $Context = Get-Content "$SkillDir/SKILL.md" -Raw -ErrorAction SilentlyContinue
+        $Context = Get-Content "$SkillDir/SKILL.md" -Raw -Encoding UTF8 -ErrorAction SilentlyContinue
    }
 }

@@ -30,3 +30,5 @@ clawdhub-publish/
 # Keep the skill folder clean
 *.log
 *.tmp
+WIKI_HOME_PAGE.md
+DISCUSSION_2_CONTENT.md
@@ -1,17 +1,8 @@
 ---
 name: planning-with-files
-version: "2.10.0"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 user-invocable: true
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - WebFetch
-  - WebSearch
+allowed-tools: "Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch"
 hooks:
  PreToolUse:
    - matcher: "Write|Edit|Bash|Read|Glob|Grep"
@@ -51,6 +42,8 @@ hooks:
            else
              sh "$SCRIPT_DIR/check-complete.sh"
            fi
+metadata:
+  version: "2.16.1"
 ---

 # Planning with Files
@@ -0,0 +1,27 @@
+{
+  "PreToolUse": [
+    {
+      "type": "command",
+      "command": "cat task_plan.md 2>/dev/null | head -30 || true",
+      "matcher": { "tool_name": "Write|Edit|Bash|Read|Glob|Grep" },
+      "timeout": 5000,
+      "description": "Read plan before tool use to keep goals in active context"
+    }
+  ],
+  "PostToolUse": [
+    {
+      "type": "command",
+      "command": "echo '[planning-with-files] File updated. If this completes a phase, update task_plan.md status.'",
+      "matcher": { "tool_name": "Write|Edit" },
+      "description": "Remind agent to update plan status after file changes"
+    }
+  ],
+  "Stop": [
+    {
+      "type": "command",
+      "command": "sh .mastracode/skills/planning-with-files/scripts/check-complete.sh 2>/dev/null || sh ~/.mastracode/skills/planning-with-files/scripts/check-complete.sh 2>/dev/null || true",
+      "timeout": 10000,
+      "description": "Check all phases are complete before the agent stops"
+    }
+  ]
+}
@@ -0,0 +1,242 @@
+---
+name: planning-with-files
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
+user-invocable: true
+allowed-tools: "Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch"
+hooks:
+  PreToolUse:
+    - matcher: "Write|Edit|Bash|Read|Glob|Grep"
+      hooks:
+        - type: command
+          command: "cat task_plan.md 2>/dev/null | head -30 || true"
+  PostToolUse:
+    - matcher: "Write|Edit"
+      hooks:
+        - type: command
+          command: "echo '[planning-with-files] File updated. If this completes a phase, update task_plan.md status.'"
+  Stop:
+    - hooks:
+        - type: command
+          command: |
+            SCRIPT_DIR="${HOME}/.mastracode/skills/planning-with-files/scripts"
+            [ -f "$SCRIPT_DIR/check-complete.sh" ] || SCRIPT_DIR=".mastracode/skills/planning-with-files/scripts"
+
+            IS_WINDOWS=0
+            if [ "${OS-}" = "Windows_NT" ]; then
+              IS_WINDOWS=1
+            else
+              UNAME_S="$(uname -s 2>/dev/null || echo '')"
+              case "$UNAME_S" in
+                CYGWIN*|MINGW*|MSYS*) IS_WINDOWS=1 ;;
+              esac
+            fi
+
+            if [ "$IS_WINDOWS" -eq 1 ]; then
+              if command -v pwsh >/dev/null 2>&1; then
+                pwsh -ExecutionPolicy Bypass -File "$SCRIPT_DIR/check-complete.ps1" 2>/dev/null ||
+                powershell -ExecutionPolicy Bypass -File "$SCRIPT_DIR/check-complete.ps1" 2>/dev/null ||
+                sh "$SCRIPT_DIR/check-complete.sh"
+              else
+                powershell -ExecutionPolicy Bypass -File "$SCRIPT_DIR/check-complete.ps1" 2>/dev/null ||
+                sh "$SCRIPT_DIR/check-complete.sh"
+              fi
+            else
+              sh "$SCRIPT_DIR/check-complete.sh"
+            fi
+metadata:
+  version: "2.18.1"
+---
+
+# Planning with Files
+
+Work like Manus: Use persistent markdown files as your "working memory on disk."
+
+## FIRST: Check for Previous Session (v2.2.0)
+
+**Before starting work**, check for unsynced context from a previous session:
+
+```bash
+# Linux/macOS
+$(command -v python3 || command -v python) ~/.mastracode/skills/planning-with-files/scripts/session-catchup.py "$(pwd)"
+```
+
+```powershell
+# Windows PowerShell
+& (Get-Command python -ErrorAction SilentlyContinue).Source "$env:USERPROFILE\.mastracode\skills\planning-with-files\scripts\session-catchup.py" (Get-Location)
+```
+
+If catchup report shows unsynced context:
+1. Run `git diff --stat` to see actual code changes
+2. Read current planning files
+3. Update planning files based on catchup + git diff
+4. Then proceed with task
+
+## Important: Where Files Go
+
+- **Templates** are in this skill's `templates/` folder
+- **Your planning files** go in **your project directory**
+
+| Location | What Goes There |
+|----------|-----------------|
+| Skill directory | Templates, scripts, reference docs |
+| Your project directory | `task_plan.md`, `findings.md`, `progress.md` |
+
+## Quick Start
+
+Before ANY complex task:
+
+1. **Create `task_plan.md`** — Use [templates/task_plan.md](templates/task_plan.md) as reference
+2. **Create `findings.md`** — Use [templates/findings.md](templates/findings.md) as reference
+3. **Create `progress.md`** — Use [templates/progress.md](templates/progress.md) as reference
+4. **Re-read plan before decisions** — Refreshes goals in attention window
+5. **Update after each phase** — Mark complete, log errors
+
+> **Note:** Planning files go in your project root, not the skill installation folder.
+
+## The Core Pattern
+
+```
+Context Window = RAM (volatile, limited)
+Filesystem = Disk (persistent, unlimited)
+
+→ Anything important gets written to disk.
+```
+
+## File Purposes
+
+| File | Purpose | When to Update |
+|------|---------|----------------|
+| `task_plan.md` | Phases, progress, decisions | After each phase |
+| `findings.md` | Research, discoveries | After ANY discovery |
+| `progress.md` | Session log, test results | Throughout session |
+
+## Critical Rules
+
+### 1. Create Plan First
+Never start a complex task without `task_plan.md`. Non-negotiable.
+
+### 2. The 2-Action Rule
+> "After every 2 view/browser/search operations, IMMEDIATELY save key findings to text files."
+
+This prevents visual/multimodal information from being lost.
+
+### 3. Read Before Decide
+Before major decisions, read the plan file. This keeps goals in your attention window.
+
+### 4. Update After Act
+After completing any phase:
+- Mark phase status: `in_progress` → `complete`
+- Log any errors encountered
+- Note files created/modified
+
+### 5. Log ALL Errors
+Every error goes in the plan file. This builds knowledge and prevents repetition.
+
+```markdown
+## Errors Encountered
+| Error | Attempt | Resolution |
+|-------|---------|------------|
+| FileNotFoundError | 1 | Created default config |
+| API timeout | 2 | Added retry logic |
+```
+
+### 6. Never Repeat Failures
+```
+if action_failed:
+    next_action != same_action
+```
+Track what you tried. Mutate the approach.
+
+## The 3-Strike Error Protocol
+
+```
+ATTEMPT 1: Diagnose & Fix
+  → Read error carefully
+  → Identify root cause
+  → Apply targeted fix
+
+ATTEMPT 2: Alternative Approach
+  → Same error? Try different method
+  → Different tool? Different library?
+  → NEVER repeat exact same failing action
+
+ATTEMPT 3: Broader Rethink
+  → Question assumptions
+  → Search for solutions
+  → Consider updating the plan
+
+AFTER 3 FAILURES: Escalate to User
+  → Explain what you tried
+  → Share the specific error
+  → Ask for guidance
+```
+
+## Read vs Write Decision Matrix
+
+| Situation | Action | Reason |
+|-----------|--------|--------|
+| Just wrote a file | DON'T read | Content still in context |
+| Viewed image/PDF | Write findings NOW | Multimodal → text before lost |
+| Browser returned data | Write to file | Screenshots don't persist |
+| Starting new phase | Read plan/findings | Re-orient if context stale |
+| Error occurred | Read relevant file | Need current state to fix |
+| Resuming after gap | Read all planning files | Recover state |
+
+## The 5-Question Reboot Test
+
+If you can answer these, your context management is solid:
+
+| Question | Answer Source |
+|----------|---------------|
+| Where am I? | Current phase in task_plan.md |
+| Where am I going? | Remaining phases |
+| What's the goal? | Goal statement in plan |
+| What have I learned? | findings.md |
+| What have I done? | progress.md |
+
+## When to Use This Pattern
+
+**Use for:**
+- Multi-step tasks (3+ steps)
+- Research tasks
+- Building/creating projects
+- Tasks spanning many tool calls
+- Anything requiring organization
+
+**Skip for:**
+- Simple questions
+- Single-file edits
+- Quick lookups
+
+## Templates
+
+Copy these templates to start:
+
+- [templates/task_plan.md](templates/task_plan.md) — Phase tracking
+- [templates/findings.md](templates/findings.md) — Research storage
+- [templates/progress.md](templates/progress.md) — Session logging
+
+## Scripts
+
+Helper scripts for automation:
+
+- `scripts/init-session.sh` — Initialize all planning files
+- `scripts/check-complete.sh` — Verify all phases complete
+- `scripts/session-catchup.py` — Recover context from previous session (v2.2.0)
+
+## Advanced Topics
+
+- **Manus Principles:** See [references/reference.md](references/reference.md)
+- **Real Examples:** See [references/examples.md](references/examples.md)
+
+## Anti-Patterns
+
+| Don't | Do Instead |
+|-------|------------|
+| Use TodoWrite for persistence | Create task_plan.md file |
+| State goals once and forget | Re-read plan before decisions |
+| Hide errors and retry silently | Log errors to plan file |
+| Stuff everything in context | Store large content in files |
+| Start executing immediately | Create plan file FIRST |
+| Repeat failed actions | Track attempts, mutate approach |
+| Create files in skill directory | Create files in your project |
@@ -0,0 +1,202 @@
+# Examples: Planning with Files in Action
+
+## Example 1: Research Task
+
+**User Request:** "Research the benefits of morning exercise and write a summary"
+
+### Loop 1: Create Plan
+```bash
+Write task_plan.md
+```
+
+```markdown
+# Task Plan: Morning Exercise Benefits Research
+
+## Goal
+Create a research summary on the benefits of morning exercise.
+
+## Phases
+- [ ] Phase 1: Create this plan ✓
+- [ ] Phase 2: Search and gather sources
+- [ ] Phase 3: Synthesize findings
+- [ ] Phase 4: Deliver summary
+
+## Key Questions
+1. What are the physical health benefits?
+2. What are the mental health benefits?
+3. What scientific studies support this?
+
+## Status
+**Currently in Phase 1** - Creating plan
+```
+
+### Loop 2: Research
+```bash
+Read task_plan.md           # Refresh goals
+WebSearch "morning exercise benefits"
+Write notes.md              # Store findings
+Edit task_plan.md           # Mark Phase 2 complete
+```
+
+### Loop 3: Synthesize
+```bash
+Read task_plan.md           # Refresh goals
+Read notes.md               # Get findings
+Write morning_exercise_summary.md
+Edit task_plan.md           # Mark Phase 3 complete
+```
+
+### Loop 4: Deliver
+```bash
+Read task_plan.md           # Verify complete
+Deliver morning_exercise_summary.md
+```
+
+---
+
+## Example 2: Bug Fix Task
+
+**User Request:** "Fix the login bug in the authentication module"
+
+### task_plan.md
+```markdown
+# Task Plan: Fix Login Bug
+
+## Goal
+Identify and fix the bug preventing successful login.
+
+## Phases
+- [x] Phase 1: Understand the bug report ✓
+- [x] Phase 2: Locate relevant code ✓
+- [ ] Phase 3: Identify root cause (CURRENT)
+- [ ] Phase 4: Implement fix
+- [ ] Phase 5: Test and verify
+
+## Key Questions
+1. What error message appears?
+2. Which file handles authentication?
+3. What changed recently?
+
+## Decisions Made
+- Auth handler is in src/auth/login.ts
+- Error occurs in validateToken() function
+
+## Errors Encountered
+- [Initial] TypeError: Cannot read property 'token' of undefined
+  → Root cause: user object not awaited properly
+
+## Status
+**Currently in Phase 3** - Found root cause, preparing fix
+```
+
+---
+
+## Example 3: Feature Development
+
+**User Request:** "Add a dark mode toggle to the settings page"
+
+### The 3-File Pattern in Action
+
+**task_plan.md:**
+```markdown
+# Task Plan: Dark Mode Toggle
+
+## Goal
+Add functional dark mode toggle to settings.
+
+## Phases
+- [x] Phase 1: Research existing theme system ✓
+- [x] Phase 2: Design implementation approach ✓
+- [ ] Phase 3: Implement toggle component (CURRENT)
+- [ ] Phase 4: Add theme switching logic
+- [ ] Phase 5: Test and polish
+
+## Decisions Made
+- Using CSS custom properties for theme
+- Storing preference in localStorage
+- Toggle component in SettingsPage.tsx
+
+## Status
+**Currently in Phase 3** - Building toggle component
+```
+
+**notes.md:**
+```markdown
+# Notes: Dark Mode Implementation
+
+## Existing Theme System
+- Located in: src/styles/theme.ts
+- Uses: CSS custom properties
+- Current themes: light only
+
+## Files to Modify
+1. src/styles/theme.ts - Add dark theme colors
+2. src/components/SettingsPage.tsx - Add toggle
+3. src/hooks/useTheme.ts - Create new hook
+4. src/App.tsx - Wrap with ThemeProvider
+
+## Color Decisions
+- Dark background: #1a1a2e
+- Dark surface: #16213e
+- Dark text: #eaeaea
+```
+
+**dark_mode_implementation.md:** (deliverable)
+```markdown
+# Dark Mode Implementation
+
+## Changes Made
+
+### 1. Added dark theme colors
+File: src/styles/theme.ts
+...
+
+### 2. Created useTheme hook
+File: src/hooks/useTheme.ts
+...
+```
+
+---
+
+## Example 4: Error Recovery Pattern
+
+When something fails, DON'T hide it:
+
+### Before (Wrong)
+```
+Action: Read config.json
+Error: File not found
+Action: Read config.json  # Silent retry
+Action: Read config.json  # Another retry
+```
+
+### After (Correct)
+```
+Action: Read config.json
+Error: File not found
+
+# Update task_plan.md:
+## Errors Encountered
+- config.json not found → Will create default config
+
+Action: Write config.json (default config)
+Action: Read config.json
+Success!
+```
+
+---
+
+## The Read-Before-Decide Pattern
+
+**Always read your plan before major decisions:**
+
+```
+[Many tool calls have happened...]
+[Context is getting long...]
+[Original goal might be forgotten...]
+
+→ Read task_plan.md          # This brings goals back into attention!
+→ Now make the decision       # Goals are fresh in context
+```
+
+This is why Manus can handle ~50 tool calls without losing track. The plan file acts as a "goal refresh" mechanism.
@@ -0,0 +1,218 @@
+# Reference: Manus Context Engineering Principles
+
+This skill is based on context engineering principles from Manus, the AI agent company acquired by Meta for $2 billion in December 2025.
+
+## The 6 Manus Principles
+
+### Principle 1: Design Around KV-Cache
+
+> "KV-cache hit rate is THE single most important metric for production AI agents."
+
+**Statistics:**
+- ~100:1 input-to-output token ratio
+- Cached tokens: $0.30/MTok vs Uncached: $3/MTok
+- 10x cost difference!
+
+**Implementation:**
+- Keep prompt prefixes STABLE (single-token change invalidates cache)
+- NO timestamps in system prompts
+- Make context APPEND-ONLY with deterministic serialization
+
+### Principle 2: Mask, Don't Remove
+
+Don't dynamically remove tools (breaks KV-cache). Use logit masking instead.
+
+**Best Practice:** Use consistent action prefixes (e.g., `browser_`, `shell_`, `file_`) for easier masking.
+
+### Principle 3: Filesystem as External Memory
+
+> "Markdown is my 'working memory' on disk."
+
+**The Formula:**
+```
+Context Window = RAM (volatile, limited)
+Filesystem = Disk (persistent, unlimited)
+```
+
+**Compression Must Be Restorable:**
+- Keep URLs even if web content is dropped
+- Keep file paths when dropping document contents
+- Never lose the pointer to full data
+
+### Principle 4: Manipulate Attention Through Recitation
+
+> "Creates and updates todo.md throughout tasks to push global plan into model's recent attention span."
+
+**Problem:** After ~50 tool calls, models forget original goals ("lost in the middle" effect).
+
+**Solution:** Re-read `task_plan.md` before each decision. Goals appear in the attention window.
+
+```
+Start of context: [Original goal - far away, forgotten]
+...many tool calls...
+End of context: [Recently read task_plan.md - gets ATTENTION!]
+```
+
+### Principle 5: Keep the Wrong Stuff In
+
+> "Leave the wrong turns in the context."
+
+**Why:**
+- Failed actions with stack traces let model implicitly update beliefs
+- Reduces mistake repetition
+- Error recovery is "one of the clearest signals of TRUE agentic behavior"
+
+### Principle 6: Don't Get Few-Shotted
+
+> "Uniformity breeds fragility."
+
+**Problem:** Repetitive action-observation pairs cause drift and hallucination.
+
+**Solution:** Introduce controlled variation:
+- Vary phrasings slightly
+- Don't copy-paste patterns blindly
+- Recalibrate on repetitive tasks
+
+---
+
+## The 3 Context Engineering Strategies
+
+Based on Lance Martin's analysis of Manus architecture.
+
+### Strategy 1: Context Reduction
+
+**Compaction:**
+```
+Tool calls have TWO representations:
+├── FULL: Raw tool content (stored in filesystem)
+└── COMPACT: Reference/file path only
+
+RULES:
+- Apply compaction to STALE (older) tool results
+- Keep RECENT results FULL (to guide next decision)
+```
+
+**Summarization:**
+- Applied when compaction reaches diminishing returns
+- Generated using full tool results
+- Creates standardized summary objects
+
+### Strategy 2: Context Isolation (Multi-Agent)
+
+**Architecture:**
+```
+┌─────────────────────────────────┐
+│         PLANNER AGENT           │
+│  └─ Assigns tasks to sub-agents │
+├─────────────────────────────────┤
+│       KNOWLEDGE MANAGER         │
+│  └─ Reviews conversations       │
+│  └─ Determines filesystem store │
+├─────────────────────────────────┤
+│      EXECUTOR SUB-AGENTS        │
+│  └─ Perform assigned tasks      │
+│  └─ Have own context windows    │
+└─────────────────────────────────┘
+```
+
+**Key Insight:** Manus originally used `todo.md` for task planning but found ~33% of actions were spent updating it. Shifted to dedicated planner agent calling executor sub-agents.
+
+### Strategy 3: Context Offloading
+
+**Tool Design:**
+- Use <20 atomic functions total
+- Store full results in filesystem, not context
+- Use `glob` and `grep` for searching
+- Progressive disclosure: load information only as needed
+
+---
+
+## The Agent Loop
+
+Manus operates in a continuous 7-step loop:
+
+```
+┌─────────────────────────────────────────┐
+│  1. ANALYZE CONTEXT                      │
+│     - Understand user intent             │
+│     - Assess current state               │
+│     - Review recent observations         │
+├─────────────────────────────────────────┤
+│  2. THINK                                │
+│     - Should I update the plan?          │
+│     - What's the next logical action?    │
+│     - Are there blockers?                │
+├─────────────────────────────────────────┤
+│  3. SELECT TOOL                          │
+│     - Choose ONE tool                    │
+│     - Ensure parameters available        │
+├─────────────────────────────────────────┤
+│  4. EXECUTE ACTION                       │
+│     - Tool runs in sandbox               │
+├─────────────────────────────────────────┤
+│  5. RECEIVE OBSERVATION                  │
+│     - Result appended to context         │
+├─────────────────────────────────────────┤
+│  6. ITERATE                              │
+│     - Return to step 1                   │
+│     - Continue until complete            │
+├─────────────────────────────────────────┤
+│  7. DELIVER OUTCOME                      │
+│     - Send results to user               │
+│     - Attach all relevant files          │
+└─────────────────────────────────────────┘
+```
+
+---
+
+## File Types Manus Creates
+
+| File | Purpose | When Created | When Updated |
+|------|---------|--------------|--------------|
+| `task_plan.md` | Phase tracking, progress | Task start | After completing phases |
+| `findings.md` | Discoveries, decisions | After ANY discovery | After viewing images/PDFs |
+| `progress.md` | Session log, what's done | At breakpoints | Throughout session |
+| Code files | Implementation | Before execution | After errors |
+
+---
+
+## Critical Constraints
+
+- **Single-Action Execution:** ONE tool call per turn. No parallel execution.
+- **Plan is Required:** Agent must ALWAYS know: goal, current phase, remaining phases
+- **Files are Memory:** Context = volatile. Filesystem = persistent.
+- **Never Repeat Failures:** If action failed, next action MUST be different
+- **Communication is a Tool:** Message types: `info` (progress), `ask` (blocking), `result` (terminal)
+
+---
+
+## Manus Statistics
+
+| Metric | Value |
+|--------|-------|
+| Average tool calls per task | ~50 |
+| Input-to-output token ratio | 100:1 |
+| Acquisition price | $2 billion |
+| Time to $100M revenue | 8 months |
+| Framework refactors since launch | 5 times |
+
+---
+
+## Key Quotes
+
+> "Context window = RAM (volatile, limited). Filesystem = Disk (persistent, unlimited). Anything important gets written to disk."
+
+> "if action_failed: next_action != same_action. Track what you tried. Mutate the approach."
+
+> "Error recovery is one of the clearest signals of TRUE agentic behavior."
+
+> "KV-cache hit rate is the single most important metric for a production-stage AI agent."
+
+> "Leave the wrong turns in the context."
+
+---
+
+## Source
+
+Based on Manus's official context engineering documentation:
+https://manus.im/blog/Context-Engineering-for-AI-Agents-Lessons-from-Building-Manus
@@ -0,0 +1,44 @@
+# Check if all phases in task_plan.md are complete
+# Always exits 0 — uses stdout for status reporting
+# Used by Stop hook to report task completion status
+
+param(
+    [string]$PlanFile = "task_plan.md"
+)
+
+if (-not (Test-Path $PlanFile)) {
+    Write-Host "[planning-with-files] No task_plan.md found — no active planning session."
+    exit 0
+}
+
+# Read file content
+$content = Get-Content $PlanFile -Raw
+
+# Count total phases
+$TOTAL = ([regex]::Matches($content, "### Phase")).Count
+
+# Check for **Status:** format first
+$COMPLETE = ([regex]::Matches($content, "\*\*Status:\*\* complete")).Count
+$IN_PROGRESS = ([regex]::Matches($content, "\*\*Status:\*\* in_progress")).Count
+$PENDING = ([regex]::Matches($content, "\*\*Status:\*\* pending")).Count
+
+# Fallback: check for [complete] inline format if **Status:** not found
+if ($COMPLETE -eq 0 -and $IN_PROGRESS -eq 0 -and $PENDING -eq 0) {
+    $COMPLETE = ([regex]::Matches($content, "\[complete\]")).Count
+    $IN_PROGRESS = ([regex]::Matches($content, "\[in_progress\]")).Count
+    $PENDING = ([regex]::Matches($content, "\[pending\]")).Count
+}
+
+# Report status (always exit 0 — incomplete task is a normal state)
+if ($COMPLETE -eq $TOTAL -and $TOTAL -gt 0) {
+    Write-Host "[planning-with-files] ALL PHASES COMPLETE ($COMPLETE/$TOTAL)"
+} else {
+    Write-Host "[planning-with-files] Task in progress ($COMPLETE/$TOTAL phases complete)"
+    if ($IN_PROGRESS -gt 0) {
+        Write-Host "[planning-with-files] $IN_PROGRESS phase(s) still in progress."
+    }
+    if ($PENDING -gt 0) {
+        Write-Host "[planning-with-files] $PENDING phase(s) pending."
+    }
+}
+exit 0
@@ -0,0 +1,46 @@
+#!/bin/bash
+# Check if all phases in task_plan.md are complete
+# Always exits 0 — uses stdout for status reporting
+# Used by Stop hook to report task completion status
+
+PLAN_FILE="${1:-task_plan.md}"
+
+if [ ! -f "$PLAN_FILE" ]; then
+    echo "[planning-with-files] No task_plan.md found — no active planning session."
+    exit 0
+fi
+
+# Count total phases
+TOTAL=$(grep -c "### Phase" "$PLAN_FILE" || true)
+
+# Check for **Status:** format first
+COMPLETE=$(grep -cF "**Status:** complete" "$PLAN_FILE" || true)
+IN_PROGRESS=$(grep -cF "**Status:** in_progress" "$PLAN_FILE" || true)
+PENDING=$(grep -cF "**Status:** pending" "$PLAN_FILE" || true)
+
+# Fallback: check for [complete] inline format if **Status:** not found
+if [ "$COMPLETE" -eq 0 ] && [ "$IN_PROGRESS" -eq 0 ] && [ "$PENDING" -eq 0 ]; then
+    COMPLETE=$(grep -c "\[complete\]" "$PLAN_FILE" || true)
+    IN_PROGRESS=$(grep -c "\[in_progress\]" "$PLAN_FILE" || true)
+    PENDING=$(grep -c "\[pending\]" "$PLAN_FILE" || true)
+fi
+
+# Default to 0 if empty
+: "${TOTAL:=0}"
+: "${COMPLETE:=0}"
+: "${IN_PROGRESS:=0}"
+: "${PENDING:=0}"
+
+# Report status (always exit 0 — incomplete task is a normal state)
+if [ "$COMPLETE" -eq "$TOTAL" ] && [ "$TOTAL" -gt 0 ]; then
+    echo "[planning-with-files] ALL PHASES COMPLETE ($COMPLETE/$TOTAL)"
+else
+    echo "[planning-with-files] Task in progress ($COMPLETE/$TOTAL phases complete)"
+    if [ "$IN_PROGRESS" -gt 0 ]; then
+        echo "[planning-with-files] $IN_PROGRESS phase(s) still in progress."
+    fi
+    if [ "$PENDING" -gt 0 ]; then
+        echo "[planning-with-files] $PENDING phase(s) pending."
+    fi
+fi
+exit 0
@@ -0,0 +1,120 @@
+# Initialize planning files for a new session
+# Usage: .\init-session.ps1 [project-name]
+
+param(
+    [string]$ProjectName = "project"
+)
+
+$DATE = Get-Date -Format "yyyy-MM-dd"
+
+Write-Host "Initializing planning files for: $ProjectName"
+
+# Create task_plan.md if it doesn't exist
+if (-not (Test-Path "task_plan.md")) {
+    @"
+# Task Plan: [Brief Description]
+
+## Goal
+[One sentence describing the end state]
+
+## Current Phase
+Phase 1
+
+## Phases
+
+### Phase 1: Requirements & Discovery
+- [ ] Understand user intent
+- [ ] Identify constraints
+- [ ] Document in findings.md
+- **Status:** in_progress
+
+### Phase 2: Planning & Structure
+- [ ] Define approach
+- [ ] Create project structure
+- **Status:** pending
+
+### Phase 3: Implementation
+- [ ] Execute the plan
+- [ ] Write to files before executing
+- **Status:** pending
+
+### Phase 4: Testing & Verification
+- [ ] Verify requirements met
+- [ ] Document test results
+- **Status:** pending
+
+### Phase 5: Delivery
+- [ ] Review outputs
+- [ ] Deliver to user
+- **Status:** pending
+
+## Decisions Made
+| Decision | Rationale |
+|----------|-----------|
+
+## Errors Encountered
+| Error | Resolution |
+|-------|------------|
+"@ | Out-File -FilePath "task_plan.md" -Encoding UTF8
+    Write-Host "Created task_plan.md"
+} else {
+    Write-Host "task_plan.md already exists, skipping"
+}
+
+# Create findings.md if it doesn't exist
+if (-not (Test-Path "findings.md")) {
+    @"
+# Findings & Decisions
+
+## Requirements
+-
+
+## Research Findings
+-
+
+## Technical Decisions
+| Decision | Rationale |
+|----------|-----------|
+
+## Issues Encountered
+| Issue | Resolution |
+|-------|------------|
+
+## Resources
+-
+"@ | Out-File -FilePath "findings.md" -Encoding UTF8
+    Write-Host "Created findings.md"
+} else {
+    Write-Host "findings.md already exists, skipping"
+}
+
+# Create progress.md if it doesn't exist
+if (-not (Test-Path "progress.md")) {
+    @"
+# Progress Log
+
+## Session: $DATE
+
+### Current Status
+- **Phase:** 1 - Requirements & Discovery
+- **Started:** $DATE
+
+### Actions Taken
+-
+
+### Test Results
+| Test | Expected | Actual | Status |
+|------|----------|--------|--------|
+
+### Errors
+| Error | Resolution |
+|-------|------------|
+"@ | Out-File -FilePath "progress.md" -Encoding UTF8
+    Write-Host "Created progress.md"
+} else {
+    Write-Host "progress.md already exists, skipping"
+}
+
+Write-Host ""
+Write-Host "Planning files initialized!"
+Write-Host "Files: task_plan.md, findings.md, progress.md"
@@ -0,0 +1,120 @@
+#!/bin/bash
+# Initialize planning files for a new session
+# Usage: ./init-session.sh [project-name]
+
+set -e
+
+PROJECT_NAME="${1:-project}"
+DATE=$(date +%Y-%m-%d)
+
+echo "Initializing planning files for: $PROJECT_NAME"
+
+# Create task_plan.md if it doesn't exist
+if [ ! -f "task_plan.md" ]; then
+    cat > task_plan.md << 'EOF'
+# Task Plan: [Brief Description]
+
+## Goal
+[One sentence describing the end state]
+
+## Current Phase
+Phase 1
+
+## Phases
+
+### Phase 1: Requirements & Discovery
+- [ ] Understand user intent
+- [ ] Identify constraints
+- [ ] Document in findings.md
+- **Status:** in_progress
+
+### Phase 2: Planning & Structure
+- [ ] Define approach
+- [ ] Create project structure
+- **Status:** pending
+
+### Phase 3: Implementation
+- [ ] Execute the plan
+- [ ] Write to files before executing
+- **Status:** pending
+
+### Phase 4: Testing & Verification
+- [ ] Verify requirements met
+- [ ] Document test results
+- **Status:** pending
+
+### Phase 5: Delivery
+- [ ] Review outputs
+- [ ] Deliver to user
+- **Status:** pending
+
+## Decisions Made
+| Decision | Rationale |
+|----------|-----------|
+
+## Errors Encountered
+| Error | Resolution |
+|-------|------------|
+EOF
+    echo "Created task_plan.md"
+else
+    echo "task_plan.md already exists, skipping"
+fi
+
+# Create findings.md if it doesn't exist
+if [ ! -f "findings.md" ]; then
+    cat > findings.md << 'EOF'
+# Findings & Decisions
+
+## Requirements
+-
+
+## Research Findings
+-
+
+## Technical Decisions
+| Decision | Rationale |
+|----------|-----------|
+
+## Issues Encountered
+| Issue | Resolution |
+|-------|------------|
+
+## Resources
+-
+EOF
+    echo "Created findings.md"
+else
+    echo "findings.md already exists, skipping"
+fi
+
+# Create progress.md if it doesn't exist
+if [ ! -f "progress.md" ]; then
+    cat > progress.md << EOF
+# Progress Log
+
+## Session: $DATE
+
+### Current Status
+- **Phase:** 1 - Requirements & Discovery
+- **Started:** $DATE
+
+### Actions Taken
+-
+
+### Test Results
+| Test | Expected | Actual | Status |
+|------|----------|--------|--------|
+
+### Errors
+| Error | Resolution |
+|-------|------------|
+EOF
+    echo "Created progress.md"
+else
+    echo "progress.md already exists, skipping"
+fi
+
+echo ""
+echo "Planning files initialized!"
+echo "Files: task_plan.md, findings.md, progress.md"
@@ -0,0 +1,209 @@
+#!/usr/bin/env python3
+"""
+Session Catchup Script for planning-with-files
+
+Analyzes the previous session to find unsynced context after the last
+planning file update. Designed to run on SessionStart.
+
+Usage: python3 session-catchup.py [project-path]
+"""
+
+import json
+import sys
+import os
+from pathlib import Path
+from typing import List, Dict, Optional, Tuple
+from datetime import datetime
+
+PLANNING_FILES = ['task_plan.md', 'progress.md', 'findings.md']
+
+
+def get_project_dir(project_path: str) -> Path:
+    """Convert project path to Claude's storage path format."""
+    sanitized = project_path.replace('/', '-')
+    if not sanitized.startswith('-'):
+        sanitized = '-' + sanitized
+    sanitized = sanitized.replace('_', '-')
+    return Path.home() / '.claude' / 'projects' / sanitized
+
+
+def get_sessions_sorted(project_dir: Path) -> List[Path]:
+    """Get all session files sorted by modification time (newest first)."""
+    sessions = list(project_dir.glob('*.jsonl'))
+    main_sessions = [s for s in sessions if not s.name.startswith('agent-')]
+    return sorted(main_sessions, key=lambda p: p.stat().st_mtime, reverse=True)
+
+
+def parse_session_messages(session_file: Path) -> List[Dict]:
+    """Parse all messages from a session file, preserving order."""
+    messages = []
+    with open(session_file, 'r') as f:
+        for line_num, line in enumerate(f):
+            try:
+                data = json.loads(line)
+                data['_line_num'] = line_num
+                messages.append(data)
+            except json.JSONDecodeError:
+                pass
+    return messages
+
+
+def find_last_planning_update(messages: List[Dict]) -> Tuple[int, Optional[str]]:
+    """
+    Find the last time a planning file was written/edited.
+    Returns (line_number, filename) or (-1, None) if not found.
+    """
+    last_update_line = -1
+    last_update_file = None
+
+    for msg in messages:
+        msg_type = msg.get('type')
+
+        if msg_type == 'assistant':
+            content = msg.get('message', {}).get('content', [])
+            if isinstance(content, list):
+                for item in content:
+                    if item.get('type') == 'tool_use':
+                        tool_name = item.get('name', '')
+                        tool_input = item.get('input', {})
+
+                        if tool_name in ('Write', 'Edit'):
+                            file_path = tool_input.get('file_path', '')
+                            for pf in PLANNING_FILES:
+                                if file_path.endswith(pf):
+                                    last_update_line = msg['_line_num']
+                                    last_update_file = pf
+
+    return last_update_line, last_update_file
+
+
+def extract_messages_after(messages: List[Dict], after_line: int) -> List[Dict]:
+    """Extract conversation messages after a certain line number."""
+    result = []
+    for msg in messages:
+        if msg['_line_num'] <= after_line:
+            continue
+
+        msg_type = msg.get('type')
+        is_meta = msg.get('isMeta', False)
+
+        if msg_type == 'user' and not is_meta:
+            content = msg.get('message', {}).get('content', '')
+            if isinstance(content, list):
+                for item in content:
+                    if isinstance(item, dict) and item.get('type') == 'text':
+                        content = item.get('text', '')
+                        break
+                else:
+                    content = ''
+
+            if content and isinstance(content, str):
+                if content.startswith(('<local-command', '<command-', '<task-notification')):
+                    continue
+                if len(content) > 20:
+                    result.append({'role': 'user', 'content': content, 'line': msg['_line_num']})
+
+        elif msg_type == 'assistant':
+            msg_content = msg.get('message', {}).get('content', '')
+            text_content = ''
+            tool_uses = []
+
+            if isinstance(msg_content, str):
+                text_content = msg_content
+            elif isinstance(msg_content, list):
+                for item in msg_content:
+                    if item.get('type') == 'text':
+                        text_content = item.get('text', '')
+                    elif item.get('type') == 'tool_use':
+                        tool_name = item.get('name', '')
+                        tool_input = item.get('input', {})
+                        if tool_name == 'Edit':
+                            tool_uses.append(f"Edit: {tool_input.get('file_path', 'unknown')}")
+                        elif tool_name == 'Write':
+                            tool_uses.append(f"Write: {tool_input.get('file_path', 'unknown')}")
+                        elif tool_name == 'Bash':
+                            cmd = tool_input.get('command', '')[:80]
+                            tool_uses.append(f"Bash: {cmd}")
+                        else:
+                            tool_uses.append(f"{tool_name}")
+
+            if text_content or tool_uses:
+                result.append({
+                    'role': 'assistant',
+                    'content': text_content[:600] if text_content else '',
+                    'tools': tool_uses,
+                    'line': msg['_line_num']
+                })
+
+    return result
+
+
+def main():
+    project_path = sys.argv[1] if len(sys.argv) > 1 else os.getcwd()
+    project_dir = get_project_dir(project_path)
+
+    # Check if planning files exist (indicates active task)
+    has_planning_files = any(
+        Path(project_path, f).exists() for f in PLANNING_FILES
+    )
+    if not has_planning_files:
+        # No planning files in this project; skip catchup to avoid noise.
+        return
+
+    if not project_dir.exists():
+        # No previous sessions, nothing to catch up on
+        return
+
+    sessions = get_sessions_sorted(project_dir)
+    if len(sessions) < 1:
+        return
+
+    # Find a substantial previous session
+    target_session = None
+    for session in sessions:
+        if session.stat().st_size > 5000:
+            target_session = session
+            break
+
+    if not target_session:
+        return
+
+    messages = parse_session_messages(target_session)
+    last_update_line, last_update_file = find_last_planning_update(messages)
+
+    # No planning updates in the target session; skip catchup output.
+    if last_update_line < 0:
+        return
+
+    # Only output if there's unsynced content
+    messages_after = extract_messages_after(messages, last_update_line)
+
+    if not messages_after:
+        return
+
+    # Output catchup report
+    print("\n[planning-with-files] SESSION CATCHUP DETECTED")
+    print(f"Previous session: {target_session.stem}")
+
+    print(f"Last planning update: {last_update_file} at message #{last_update_line}")
+    print(f"Unsynced messages: {len(messages_after)}")
+
+    print("\n--- UNSYNCED CONTEXT ---")
+    for msg in messages_after[-15:]:  # Last 15 messages
+        if msg['role'] == 'user':
+            print(f"USER: {msg['content'][:300]}")
+        else:
+            if msg.get('content'):
+                print(f"CLAUDE: {msg['content'][:300]}")
+            if msg.get('tools'):
+                print(f"  Tools: {', '.join(msg['tools'][:4])}")
+
+    print("\n--- RECOMMENDED ---")
+    print("1. Run: git diff --stat")
+    print("2. Read: task_plan.md, progress.md, findings.md")
+    print("3. Update planning files based on above context")
+    print("4. Continue with task")
+
+
+if __name__ == '__main__':
+    main()
@@ -0,0 +1,95 @@
+# Findings & Decisions
+<!-- 
+  WHAT: Your knowledge base for the task. Stores everything you discover and decide.
+  WHY: Context windows are limited. This file is your "external memory" - persistent and unlimited.
+  WHEN: Update after ANY discovery, especially after 2 view/browser/search operations (2-Action Rule).
+-->
+
+## Requirements
+<!-- 
+  WHAT: What the user asked for, broken down into specific requirements.
+  WHY: Keeps requirements visible so you don't forget what you're building.
+  WHEN: Fill this in during Phase 1 (Requirements & Discovery).
+  EXAMPLE:
+    - Command-line interface
+    - Add tasks
+    - List all tasks
+    - Delete tasks
+    - Python implementation
+-->
+<!-- Captured from user request -->
+-
+
+## Research Findings
+<!-- 
+  WHAT: Key discoveries from web searches, documentation reading, or exploration.
+  WHY: Multimodal content (images, browser results) doesn't persist. Write it down immediately.
+  WHEN: After EVERY 2 view/browser/search operations, update this section (2-Action Rule).
+  EXAMPLE:
+    - Python's argparse module supports subcommands for clean CLI design
+    - JSON module handles file persistence easily
+    - Standard pattern: python script.py <command> [args]
+-->
+<!-- Key discoveries during exploration -->
+-
+
+## Technical Decisions
+<!-- 
+  WHAT: Architecture and implementation choices you've made, with reasoning.
+  WHY: You'll forget why you chose a technology or approach. This table preserves that knowledge.
+  WHEN: Update whenever you make a significant technical choice.
+  EXAMPLE:
+    | Use JSON for storage | Simple, human-readable, built-in Python support |
+    | argparse with subcommands | Clean CLI: python todo.py add "task" |
+-->
+<!-- Decisions made with rationale -->
+| Decision | Rationale |
+|----------|-----------|
+|          |           |
+
+## Issues Encountered
+<!-- 
+  WHAT: Problems you ran into and how you solved them.
+  WHY: Similar to errors in task_plan.md, but focused on broader issues (not just code errors).
+  WHEN: Document when you encounter blockers or unexpected challenges.
+  EXAMPLE:
+    | Empty file causes JSONDecodeError | Added explicit empty file check before json.load() |
+-->
+<!-- Errors and how they were resolved -->
+| Issue | Resolution |
+|-------|------------|
+|       |            |
+
+## Resources
+<!-- 
+  WHAT: URLs, file paths, API references, documentation links you've found useful.
+  WHY: Easy reference for later. Don't lose important links in context.
+  WHEN: Add as you discover useful resources.
+  EXAMPLE:
+    - Python argparse docs: https://docs.python.org/3/library/argparse.html
+    - Project structure: src/main.py, src/utils.py
+-->
+<!-- URLs, file paths, API references -->
+-
+
+## Visual/Browser Findings
+<!-- 
+  WHAT: Information you learned from viewing images, PDFs, or browser results.
+  WHY: CRITICAL - Visual/multimodal content doesn't persist in context. Must be captured as text.
+  WHEN: IMMEDIATELY after viewing images or browser results. Don't wait!
+  EXAMPLE:
+    - Screenshot shows login form has email and password fields
+    - Browser shows API returns JSON with "status" and "data" keys
+-->
+<!-- CRITICAL: Update after every 2 view/browser operations -->
+<!-- Multimodal content must be captured as text immediately -->
+-
+
+---
+<!-- 
+  REMINDER: The 2-Action Rule
+  After every 2 view/browser/search operations, you MUST update this file.
+  This prevents visual information from being lost when context resets.
+-->
+*Update this file after every 2 view/browser/search operations*
+*This prevents visual information from being lost*
@@ -0,0 +1,114 @@
+# Progress Log
+<!-- 
+  WHAT: Your session log - a chronological record of what you did, when, and what happened.
+  WHY: Answers "What have I done?" in the 5-Question Reboot Test. Helps you resume after breaks.
+  WHEN: Update after completing each phase or encountering errors. More detailed than task_plan.md.
+-->
+
+## Session: [DATE]
+<!-- 
+  WHAT: The date of this work session.
+  WHY: Helps track when work happened, useful for resuming after time gaps.
+  EXAMPLE: 2026-01-15
+-->
+
+### Phase 1: [Title]
+<!-- 
+  WHAT: Detailed log of actions taken during this phase.
+  WHY: Provides context for what was done, making it easier to resume or debug.
+  WHEN: Update as you work through the phase, or at least when you complete it.
+-->
+- **Status:** in_progress
+- **Started:** [timestamp]
+<!-- 
+  STATUS: Same as task_plan.md (pending, in_progress, complete)
+  TIMESTAMP: When you started this phase (e.g., "2026-01-15 10:00")
+-->
+- Actions taken:
+  <!-- 
+    WHAT: List of specific actions you performed.
+    EXAMPLE:
+      - Created todo.py with basic structure
+      - Implemented add functionality
+      - Fixed FileNotFoundError
+  -->
+  -
+- Files created/modified:
+  <!-- 
+    WHAT: Which files you created or changed.
+    WHY: Quick reference for what was touched. Helps with debugging and review.
+    EXAMPLE:
+      - todo.py (created)
+      - todos.json (created by app)
+      - task_plan.md (updated)
+  -->
+  -
+
+### Phase 2: [Title]
+<!-- 
+  WHAT: Same structure as Phase 1, for the next phase.
+  WHY: Keep a separate log entry for each phase to track progress clearly.
+-->
+- **Status:** pending
+- Actions taken:
+  -
+- Files created/modified:
+  -
+
+## Test Results
+<!-- 
+  WHAT: Table of tests you ran, what you expected, what actually happened.
+  WHY: Documents verification of functionality. Helps catch regressions.
+  WHEN: Update as you test features, especially during Phase 4 (Testing & Verification).
+  EXAMPLE:
+    | Add task | python todo.py add "Buy milk" | Task added | Task added successfully | ✓ |
+    | List tasks | python todo.py list | Shows all tasks | Shows all tasks | ✓ |
+-->
+| Test | Input | Expected | Actual | Status |
+|------|-------|----------|--------|--------|
+|      |       |          |        |        |
+
+## Error Log
+<!-- 
+  WHAT: Detailed log of every error encountered, with timestamps and resolution attempts.
+  WHY: More detailed than task_plan.md's error table. Helps you learn from mistakes.
+  WHEN: Add immediately when an error occurs, even if you fix it quickly.
+  EXAMPLE:
+    | 2026-01-15 10:35 | FileNotFoundError | 1 | Added file existence check |
+    | 2026-01-15 10:37 | JSONDecodeError | 2 | Added empty file handling |
+-->
+<!-- Keep ALL errors - they help avoid repetition -->
+| Timestamp | Error | Attempt | Resolution |
+|-----------|-------|---------|------------|
+|           |       | 1       |            |
+
+## 5-Question Reboot Check
+<!-- 
+  WHAT: Five questions that verify your context is solid. If you can answer these, you're on track.
+  WHY: This is the "reboot test" - if you can answer all 5, you can resume work effectively.
+  WHEN: Update periodically, especially when resuming after a break or context reset.
+  
+  THE 5 QUESTIONS:
+  1. Where am I? → Current phase in task_plan.md
+  2. Where am I going? → Remaining phases
+  3. What's the goal? → Goal statement in task_plan.md
+  4. What have I learned? → See findings.md
+  5. What have I done? → See progress.md (this file)
+-->
+<!-- If you can answer these, context is solid -->
+| Question | Answer |
+|----------|--------|
+| Where am I? | Phase X |
+| Where am I going? | Remaining phases |
+| What's the goal? | [goal statement] |
+| What have I learned? | See findings.md |
+| What have I done? | See above |
+
+---
+<!-- 
+  REMINDER: 
+  - Update after completing each phase or encountering errors
+  - Be detailed - this is your "what happened" log
+  - Include timestamps for errors to track when issues occurred
+-->
+*Update after completing each phase or encountering errors*
@@ -0,0 +1,132 @@
+# Task Plan: [Brief Description]
+<!-- 
+  WHAT: This is your roadmap for the entire task. Think of it as your "working memory on disk."
+  WHY: After 50+ tool calls, your original goals can get forgotten. This file keeps them fresh.
+  WHEN: Create this FIRST, before starting any work. Update after each phase completes.
+-->
+
+## Goal
+<!-- 
+  WHAT: One clear sentence describing what you're trying to achieve.
+  WHY: This is your north star. Re-reading this keeps you focused on the end state.
+  EXAMPLE: "Create a Python CLI todo app with add, list, and delete functionality."
+-->
+[One sentence describing the end state]
+
+## Current Phase
+<!-- 
+  WHAT: Which phase you're currently working on (e.g., "Phase 1", "Phase 3").
+  WHY: Quick reference for where you are in the task. Update this as you progress.
+-->
+Phase 1
+
+## Phases
+<!-- 
+  WHAT: Break your task into 3-7 logical phases. Each phase should be completable.
+  WHY: Breaking work into phases prevents overwhelm and makes progress visible.
+  WHEN: Update status after completing each phase: pending → in_progress → complete
+-->
+
+### Phase 1: Requirements & Discovery
+<!-- 
+  WHAT: Understand what needs to be done and gather initial information.
+  WHY: Starting without understanding leads to wasted effort. This phase prevents that.
+-->
+- [ ] Understand user intent
+- [ ] Identify constraints and requirements
+- [ ] Document findings in findings.md
+- **Status:** in_progress
+<!-- 
+  STATUS VALUES:
+  - pending: Not started yet
+  - in_progress: Currently working on this
+  - complete: Finished this phase
+-->
+
+### Phase 2: Planning & Structure
+<!-- 
+  WHAT: Decide how you'll approach the problem and what structure you'll use.
+  WHY: Good planning prevents rework. Document decisions so you remember why you chose them.
+-->
+- [ ] Define technical approach
+- [ ] Create project structure if needed
+- [ ] Document decisions with rationale
+- **Status:** pending
+
+### Phase 3: Implementation
+<!-- 
+  WHAT: Actually build/create/write the solution.
+  WHY: This is where the work happens. Break into smaller sub-tasks if needed.
+-->
+- [ ] Execute the plan step by step
+- [ ] Write code to files before executing
+- [ ] Test incrementally
+- **Status:** pending
+
+### Phase 4: Testing & Verification
+<!-- 
+  WHAT: Verify everything works and meets requirements.
+  WHY: Catching issues early saves time. Document test results in progress.md.
+-->
+- [ ] Verify all requirements met
+- [ ] Document test results in progress.md
+- [ ] Fix any issues found
+- **Status:** pending
+
+### Phase 5: Delivery
+<!-- 
+  WHAT: Final review and handoff to user.
+  WHY: Ensures nothing is forgotten and deliverables are complete.
+-->
+- [ ] Review all output files
+- [ ] Ensure deliverables are complete
+- [ ] Deliver to user
+- **Status:** pending
+
+## Key Questions
+<!-- 
+  WHAT: Important questions you need to answer during the task.
+  WHY: These guide your research and decision-making. Answer them as you go.
+  EXAMPLE: 
+    1. Should tasks persist between sessions? (Yes - need file storage)
+    2. What format for storing tasks? (JSON file)
+-->
+1. [Question to answer]
+2. [Question to answer]
+
+## Decisions Made
+<!-- 
+  WHAT: Technical and design decisions you've made, with the reasoning behind them.
+  WHY: You'll forget why you made choices. This table helps you remember and justify decisions.
+  WHEN: Update whenever you make a significant choice (technology, approach, structure).
+  EXAMPLE:
+    | Use JSON for storage | Simple, human-readable, built-in Python support |
+-->
+| Decision | Rationale |
+|----------|-----------|
+|          |           |
+
+## Errors Encountered
+<!-- 
+  WHAT: Every error you encounter, what attempt number it was, and how you resolved it.
+  WHY: Logging errors prevents repeating the same mistakes. This is critical for learning.
+  WHEN: Add immediately when an error occurs, even if you fix it quickly.
+  EXAMPLE:
+    | FileNotFoundError | 1 | Check if file exists, create empty list if not |
+    | JSONDecodeError | 2 | Handle empty file case explicitly |
+-->
+| Error | Attempt | Resolution |
+|-------|---------|------------|
+|       | 1       |            |
+
+## Notes
+<!-- 
+  REMINDERS:
+  - Update phase status as you progress: pending → in_progress → complete
+  - Re-read this plan before major decisions (attention manipulation)
+  - Log ALL errors - they help avoid repetition
+  - Never repeat a failed action - mutate your approach instead
+-->
+- Update phase status as you progress: pending → in_progress → complete
+- Re-read this plan before major decisions (attention manipulation)
+- Log ALL errors - they help avoid repetition
@@ -1,10 +1,12 @@
 ---
 name: planning-with-files
-version: "2.10.0"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 homepage: https://github.com/OthmanAdi/planning-with-files
 user-invocable: true
-metadata: {"openclaw":{"os":["darwin","linux","win32"]}}
+metadata:
+  version: "2.16.1"
+  openclaw:
+    os: ["darwin", "linux", "win32"]
 ---

 # Planning with Files
@@ -1,17 +1,8 @@
 ---
 name: planning-with-files
-version: "2.10.0"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 user-invocable: true
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - WebFetch
-  - WebSearch
+allowed-tools: "Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch"
 hooks:
  PreToolUse:
    - matcher: "Write|Edit|Bash|Read|Glob|Grep"
@@ -51,6 +42,8 @@ hooks:
            else
              sh "$SCRIPT_DIR/check-complete.sh"
            fi
+metadata:
+  version: "2.16.1"
 ---

 # Planning with Files
@@ -1,6 +1,6 @@
 ---
 name: pi-planning-with-files
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 ---

 # Planning with Files
@@ -2,6 +2,75 @@

 All notable changes to this project will be documented in this file.

+## [2.18.2] - 2026-02-26
+
+### Fixed
+
+- **Mastra Code hooks were silently doing nothing**
+  - Root cause: Mastra Code reads hooks from `.mastracode/hooks.json`, not from SKILL.md frontmatter. The existing integration had hooks defined only in SKILL.md (Claude Code format), which Mastra Code ignores entirely. All three hooks (PreToolUse, PostToolUse, Stop) were non-functional.
+  - Added `.mastracode/hooks.json` with proper Mastra Code format including `matcher`, `timeout`, and `description` fields
+  - Fixed `MASTRACODE_SKILL_ROOT` env var in SKILL.md Stop hook (variable does not exist in Mastra Code, replaced with `$HOME` fallback to local path)
+  - Bumped `.mastracode/skills/planning-with-files/SKILL.md` metadata version from 2.16.1 to 2.18.1
+  - Corrected `docs/mastra.md` to accurately describe hooks.json (removed false claim that Mastra Code uses the same hook system as Claude Code)
+  - Fixed personal installation instructions to include hooks.json copy step
+
+---
+
+## [2.18.1] - 2026-02-26
+
+### Fixed
+
+- **Copilot hooks garbled characters — still broken after v2.16.1** (Issue #82, confirmed by @Hexiaopi)
+  - Root cause: `Get-Content` in all PS1 scripts had no `-Encoding` parameter — PowerShell 5.x reads files using the system ANSI code page (Windows-1252) by default, corrupting any non-ASCII character in `task_plan.md` or `SKILL.md` before it reaches the output pipe. The v2.16.1 fix was correct but fixed only the output side, not the read side.
+  - Secondary fix: `[System.Text.Encoding]::UTF8` returns UTF-8 with BOM — replaced with `[System.Text.UTF8Encoding]::new($false)` (UTF-8 without BOM) in all four PS1 scripts to prevent JSON parsers from receiving a stray `0xEF 0xBB 0xBF` preamble
+  - Fixed files: `pre-tool-use.ps1`, `session-start.ps1`, `agent-stop.ps1`, `post-tool-use.ps1`
+  - Bash scripts were already correct from v2.16.1
+
+### Thanks
+
+- @Hexiaopi for confirming the issue persisted after v2.16.1 (Issue #82)
+
+---
+
+## [2.18.0] - 2026-02-26
+
+### Added
+
+- **BoxLite sandbox runtime integration** (Issue #84 by @DorianZheng)
+  - New `docs/boxlite.md` guide for running planning-with-files inside BoxLite micro-VM sandboxes via ClaudeBox
+  - New `examples/boxlite/quickstart.py` — working Python example using ClaudeBox's Skill API to inject planning-with-files into a VM
+  - New `examples/boxlite/README.md` — example context and requirements
+  - README: new "Sandbox Runtimes" section (BoxLite is infrastructure, not an IDE — kept separate from the 16-platform IDE table)
+  - README: BoxLite badge and Documentation table entry added
+  - BoxLite loads via ClaudeBox (`pip install claudebox`) using its Python Skill object — no `.boxlite/` folder needed
+
+### Thanks
+
+- @DorianZheng for the BoxLite integration proposal (Issue #84)
+
+---
+
+## [2.17.0] - 2026-02-25
+
+### Added
+
+- **Mastra Code support** — new `.mastracode/skills/planning-with-files/` integration with native hooks (PreToolUse, PostToolUse, Stop), full scripts, templates, and installation guide (platform #16)
+
+### Fixed
+
+- **Skill metadata spec compliance** — applied PR #83 fixes across all 12 IDE-specific SKILL.md files:
+  - `allowed-tools` YAML list → comma-separated string (Codex, Cursor, Kilocode, CodeBuddy, OpenCode)
+  - `version` moved from top-level to `metadata.version` across all applicable files
+  - Description updated with trigger terms ("plan out", "break down", "organize", "track progress") in all IDEs
+  - Version bumped to 2.16.1 everywhere, including canonical `skills/planning-with-files/SKILL.md`
+  - OpenClaw inline JSON metadata expanded to proper block YAML
+
+### Thanks
+
+- @popey for the PR #83 spec fixes that identified the issues
+
+---
+
 ## [2.16.1] - 2026-02-25

 ### Fixed
@@ -92,6 +92,7 @@ These developers have created forks that extend the functionality:

 Thank you to everyone who reported issues, provided feedback, and helped test fixes:

+- [@DorianZheng](https://github.com/DorianZheng) - Issue #84 (BoxLite sandbox integration proposal)
 - [@mtuwei](https://github.com/mtuwei) - Issue #32 (Windows hook error)
 - [@JianweiWangs](https://github.com/JianweiWangs) - Issue #31 (Skill activation)
 - [@tingles2233](https://github.com/tingles2233) - Issue #29 (Plugin update issues)
@@ -118,6 +119,6 @@ If you've contributed and don't see your name here, please open an issue! We wan

 ---

-**Total Contributors:** 12+ and growing!
+**Total Contributors:** 13+ and growing!

-*Last updated: February 21, 2026*
+*Last updated: February 26, 2026*
@@ -1,119 +0,0 @@
-## Help Us Test Session Management Features!
-
-I've implemented session management patterns from Anthropic's article ["Effective harnesses for long-running agents"](https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents) in the **`feature/anthropic-patterns`** branch.
-
-These features need testing before merging to main. **Your feedback is critical!**
-
---
-
-## What's New
-
-### 1. Session Initialization Script
-Run at the start of every session:
-```bash
-bash scripts/init-session.sh
-```
-
-**What it does:**
- ✅ Verifies planning files exist
- ✅ Shows current phase and git status
- ✅ Displays last commit
- ✅ Logs session start to progress.md
- ✅ Creates missing files if needed
-
-### 2. Pass/Fail Status Tracking
-Enhanced `task_plan.md` template with:
- Status icons: ⏸️ Pending | 🔄 In Progress | ✅ Pass | ❌ Fail | ⏭️ Skipped
- Test Results table for each phase
- Git Checkpoints table to log commits
- Phase Summary table for quick overview
-
-### 3. Git Checkpoint Workflow
-New documentation: `docs/git-checkpoints.md`
- "One phase, one commit" pattern
- Use git commits as rollback points
- Integrates with task_plan.md
-
-### 4. Session-Start Verification
-Automated checklist that verifies:
- Planning files present
- Git working tree clean
- Current branch status
- Last commit information
-
---
-
-## How to Test
-
-### 1. Checkout the Branch
-```bash
-cd your-planning-with-files-repo
-git fetch origin
-git checkout feature/anthropic-patterns
-```
-
-### 2. Try It In a Test Project
-```bash
-cd ~/your-test-project
-bash /path/to/planning-with-files/scripts/init-session.sh
-```
-
-### 3. Work Through a Multi-Phase Task
- Let the script create planning files
- Define some phases in task_plan.md
- Complete a phase and test it
- Mark it as ✅ Pass with test results
- Commit: `git commit -m "feat(Phase 1): description"`
- Log the commit hash in Git Checkpoints table
- Start a new session and run init-session.sh again
-
-### 4. Read the Implementation Summary
-See `IMPLEMENTATION_SUMMARY.md` in the branch for full details.
-
---
-
-## What We Need Feedback On
-
-1. **Does init-session.sh work on your system?**
-   - Unix/Mac: Does the bash script run smoothly?
-   - Windows: Does the PowerShell version work?
-
-2. **Is the new task_plan.md template helpful?**
-   - Are the status icons clear?
-   - Is the Test Results table useful?
-   - Does the Git Checkpoints table make sense?
-
-3. **Does the workflow feel natural?**
-   - Plan → Implement → Verify → Commit
-   - Does session recovery work when you restart?
-
-4. **Any bugs or issues?**
-   - Errors when running scripts?
-   - Confusing documentation?
-   - Missing features?
-
-5. **Suggestions for improvement?**
-   - What would make this better?
-   - Any patterns from the Anthropic article we missed?
-
---
-
-## Related Issue
-
-This work resolves [Issue #19](https://github.com/OthmanAdi/planning-with-files/issues/19) requested by @wqh17101.
-
---
-
-## Documentation
-
- [Git Checkpoint Workflow](https://github.com/OthmanAdi/planning-with-files/blob/feature/anthropic-patterns/docs/git-checkpoints.md)
- [Implementation Summary](https://github.com/OthmanAdi/planning-with-files/blob/feature/anthropic-patterns/IMPLEMENTATION_SUMMARY.md)
- [Anthropic Article](https://www.anthropic.com/engineering/effective-harnesses-for-long-running-agents) (inspiration)
-
---
-
-**Please test and share your experience!** Once we have enough feedback and approval, I'll merge this to main.
-
-Thank you!
-
-Ahmad
@@ -35,6 +35,7 @@ Everyone who made this project better — bug reports, PRs, and integrations.

 | Contributor | Contribution |
 |-------------|-------------|
+| [@popey](https://github.com/popey) | Skill metadata & discoverability fixes (PR #83) |
 | [@lincolnwan](https://github.com/lincolnwan) | GitHub Copilot hooks support (PR #80) |
 | [@gydx6](https://github.com/gydx6) | Session catchup false-positive fix (PR #79) |
 | [@ciberponk](https://github.com/ciberponk) | Isolated plan sessions with UUID pinning (PR #77) |
@@ -57,10 +58,14 @@ Everyone who made this project better — bug reports, PRs, and integrations.
 <details>
 <summary><strong>📦 Releases & Session Recovery</strong></summary>

-### Current Version: v2.16.1
+### Current Version: v2.18.2

 | Version | Highlights |
 |---------|------------|
+| **v2.18.2** | Mastra Code hooks fix (hooks.json + docs accuracy) |
+| **v2.18.1** | Copilot garbled characters complete fix |
+| **v2.18.0** | BoxLite sandbox runtime integration |
+| **v2.17.0** | Mastra Code support + all IDE SKILL.md spec fixes |
 | **v2.16.1** | Copilot garbled characters fix — PS1 UTF-8 encoding + bash ensure_ascii (thanks @Hexiaopi!) |
 | **v2.16.0** | GitHub Copilot hooks support (thanks @lincolnwan!) |
 | **v2.15.1** | Session catchup false-positive fix (thanks @gydx6!) |
@@ -95,7 +100,7 @@ When your context fills up and you run `/clear`, this skill **automatically reco
 </details>

 <details>
-<summary><strong>🛠️ Supported IDEs (15 Platforms)</strong></summary>
+<summary><strong>🛠️ Supported IDEs (16 Platforms)</strong></summary>

 | IDE | Status | Installation Guide | Format |
 |-----|--------|-------------------|--------|
@@ -114,11 +119,23 @@ When your context fills up and you run `/clear`, this skill **automatically reco
 | AdaL CLI (Sylph AI) | ✅ Full Support | [AdaL Setup](docs/adal.md) | Personal/Project Skills |
 | Pi Agent | ✅ Full Support | [Pi Agent Setup](docs/pi-agent.md) | Agent Skills |
 | GitHub Copilot | ✅ Full Support | [Copilot Setup](docs/copilot.md) | Hooks |
+| Mastra Code | ✅ Full Support | [Mastra Setup](docs/mastra.md) | Skills + Hooks |

 > **Note:** If your IDE uses the legacy Rules system instead of Skills, see the [`legacy-rules-support`](https://github.com/OthmanAdi/planning-with-files/tree/legacy-rules-support) branch.

 </details>

+<details>
+<summary><strong>🧱 Sandbox Runtimes (1 Platform)</strong></summary>
+
+| Runtime | Status | Guide | Notes |
+|---------|--------|-------|-------|
+| BoxLite | ✅ Documented | [BoxLite Setup](docs/boxlite.md) | Run Claude Code + planning-with-files inside hardware-isolated micro-VMs |
+
+> **Note:** BoxLite is a sandbox runtime, not an IDE. Skills load via [ClaudeBox](https://github.com/boxlite-ai/claudebox) — BoxLite’s official Claude Code integration layer.
+
+</details>
+
 ---

 A Claude Code plugin that transforms your workflow to use persistent markdown files for planning, progress tracking, and knowledge storage — the exact pattern that made Manus worth billions.
@@ -134,7 +151,9 @@ A Claude Code plugin that transforms your workflow to use persistent markdown fi
 [![AdaL CLI](https://img.shields.io/badge/AdaL%20CLI-Skills-9B59B6)](https://docs.sylph.ai/features/plugins-and-skills)
 [![Pi Agent](https://img.shields.io/badge/Pi%20Agent-Skills-FF4081)](https://pi.dev)
 [![GitHub Copilot](https://img.shields.io/badge/GitHub%20Copilot-Hooks-000000)](https://docs.github.com/en/copilot/reference/hooks-configuration)
-[![Version](https://img.shields.io/badge/version-2.16.1-brightgreen)](https://github.com/OthmanAdi/planning-with-files/releases)
+[![Mastra Code](https://img.shields.io/badge/Mastra%20Code-Skills-00BCD4)](https://code.mastra.ai)
+[![BoxLite](https://img.shields.io/badge/BoxLite-Sandbox-6C3483)](https://boxlite.ai)
+[![Version](https://img.shields.io/badge/version-2.18.2-brightgreen)](https://github.com/OthmanAdi/planning-with-files/releases)
 [![SkillCheck Validated](https://img.shields.io/badge/SkillCheck-Validated-4c1)](https://getskillcheck.com)

 ## Quick Install
@@ -271,7 +290,13 @@ planning-with-files/
 │   ├── windows.md
 │   ├── kilocode.md
 │   ├── codex.md
-│   └── opencode.md
+│   ├── opencode.md
+│   ├── mastra.md             # Mastra Code setup
+│   └── boxlite.md            # BoxLite sandbox setup
+├── examples/                # Integration examples
+│   └── boxlite/             # BoxLite quickstart
+│       ├── README.md
+│       └── quickstart.py
 ├── planning-with-files/     # Plugin skill folder
 │   ├── SKILL.md
 │   ├── templates/
@@ -312,6 +337,8 @@ planning-with-files/
 │   └── hooks/
 │       ├── planning-with-files.json  # Hook configuration
 │       └── scripts/         # Hook scripts (bash + PowerShell)
+├── .mastracode/             # Mastra Code skills + hooks
+│   └── skills/
 ├── CHANGELOG.md
 ├── LICENSE
 └── README.md
@@ -340,6 +367,8 @@ planning-with-files/
 | [AdaL CLI Setup](docs/adal.md) | AdaL CLI / Sylph AI integration guide |
 | [Pi Agent Setup](docs/pi-agent.md) | Pi Agent integration guide |
 | [Copilot Setup](docs/copilot.md) | GitHub Copilot hooks integration guide |
+| [Mastra Setup](docs/mastra.md) | Mastra Code integration guide |
+| [BoxLite Setup](docs/boxlite.md) | BoxLite micro-VM sandbox integration guide |


 ## Acknowledgments
@@ -366,4 +395,4 @@ MIT License — feel free to use, modify, and distribute.

 ## Star History

-[![Star History Chart](https://api.star-history.com/svg?repos=OthmanAdi/planning-with-files&type=Date)](https://star-history.com/#OthmanAdi/planning-with-files&Date)
+<a href="https://repostars.dev/?repos=OthmanAdi%2Fplanning-with-files&theme=copper"><img src="https://repostars.dev/api/embed?repo=OthmanAdi%2Fplanning-with-files&theme=copper" width="100%" alt="Star History Chart" /></a>
@@ -1,79 +0,0 @@
-# Welcome to planning-with-files
-
-> **Work like Manus** — the AI agent company Meta acquired for **$2 billion**.
-
-This is a Claude Code skill that transforms your workflow to use persistent markdown files for planning, progress tracking, and knowledge storage.
-
-## What This Project Does
-
-Instead of relying on volatile context windows, planning-with-files teaches Claude to use **files as memory**:
-
- `task_plan.md` - Your roadmap (phases, progress, decisions)
- `findings.md` - Research and discoveries
- `progress.md` - Session logs and test results
-
-When context fills up, you don't lose work. Everything important is on disk.
-
-## Why It Exists
-
-After 50+ tool calls, Claude forgets your original goals. This skill solves that by:
- Re-reading the plan before major decisions (hooks)
- Storing findings in files instead of context
- Logging errors to prevent repetition
- Verifying completion before stopping
-
-## Inspired By
-
-Manus AI pioneered this pattern and went from launch to $100M+ revenue in 8 months. Their secret? **Context engineering through persistent files.**
-
-## Community ❤️
-
-This project grew from **one developer's experiment** to **9,600+ stars** and **10+ contributors** in weeks.
-
-**Thank you to everyone who:**
- ⭐ Starred the repo
- 🔀 Forked and built on this work
- 🐛 Reported issues and tested fixes
- 💡 Suggested features and improvements
- 🛠️ Contributed code, docs, and examples
-
-### Special Thanks
-
- **[@kaichen](https://github.com/kaichen)** - Converted to Claude Code plugin, made it accessible to thousands
- **[@fuahyo](https://github.com/fuahyo)** - Created beginner-friendly walkthrough and examples
- **[@lasmarois](https://github.com/lasmarois)** - Built session recovery feature, saved countless hours
- **[@aimasteracc](https://github.com/aimasteracc)** - Added Windows support and Kilocode integration
- **[@wqh17101](https://github.com/wqh17101)** - Inspired Anthropic patterns integration
-
-And many more! See [CONTRIBUTORS.md](https://github.com/OthmanAdi/planning-with-files/blob/main/CONTRIBUTORS.md)
-
-## Growing Together
-
-What started as a simple 3-file pattern is now:
- 5 IDE integrations (Claude Code, Cursor, Kilocode, OpenCode, Codex)
- Session recovery after `/clear`
- Git checkpoint workflows
- Windows PowerShell support
- Community forks and derivatives
-
-**None of this would exist without you.**
-
-## Get Involved
-
- 💬 [Discussions](https://github.com/OthmanAdi/planning-with-files/discussions) - Share your experience
- 🐛 [Issues](https://github.com/OthmanAdi/planning-with-files/issues) - Report bugs or request features
- 🔀 [Pull Requests](https://github.com/OthmanAdi/planning-with-files/pulls) - Contribute improvements
- ⭐ Star if this helps you work smarter
-
-## Quick Links
-
- [Installation Guide](https://github.com/OthmanAdi/planning-with-files/blob/main/docs/installation.md)
- [Quick Start](https://github.com/OthmanAdi/planning-with-files/blob/main/docs/quickstart.md)
- [Examples](https://github.com/OthmanAdi/planning-with-files/blob/main/examples/README.md)
- [Changelog](https://github.com/OthmanAdi/planning-with-files/blob/main/CHANGELOG.md)
-
---
-
-**Built with appreciation for the open source community.**
-
-*Ahmad Othman Ammar Adi*
@@ -0,0 +1,190 @@
+# BoxLite Setup
+
+Using planning-with-files inside [BoxLite](https://boxlite.ai) micro-VM sandboxes via [ClaudeBox](https://github.com/boxlite-ai/claudebox).
+
+---
+
+## Overview
+
+BoxLite is a micro-VM sandbox runtime — hardware-isolated, stateful, embeddable as a library with no daemon and no root required. The analogy their team uses is "SQLite for sandboxing": you import it directly into your application and each box gets its own kernel, not just namespaces or containers.
+
+[ClaudeBox](https://github.com/boxlite-ai/claudebox) is BoxLite's official Claude Code integration layer. It runs the Claude Code CLI inside a BoxLite micro-VM with persistent workspaces, optional skills, security policies, and resource limits. planning-with-files loads into ClaudeBox as a Skill object — the skill's SKILL.md and scripts get injected into the VM filesystem at startup, exactly where Claude Code expects to find them.
+
+**Why use this combination:**
+- Run untrusted AI-generated code in hardware isolation without touching your host filesystem
+- planning files (`task_plan.md`, `findings.md`, `progress.md`) persist across sessions via ClaudeBox's stateful workspaces at `~/.claudebox/sessions/`
+- Snapshot before a risky phase, roll back if needed
+- All hooks (PreToolUse, PostToolUse, Stop) work because Claude Code runs natively inside the VM
+
+---
+
+## Prerequisites
+
+- Python 3.10+
+- BoxLite runtime (installed automatically as a ClaudeBox dependency)
+- Docker — used to pull and manage OCI images (the sandbox itself runs as a micro-VM, not a Docker container)
+- `CLAUDE_CODE_OAUTH_TOKEN` or `ANTHROPIC_API_KEY` set
+
+---
+
+## Installation
+
+### Install ClaudeBox
+
+```bash
+pip install claudebox
+```
+
+### Set your API credentials
+
+```bash
+export CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-...
+# or
+export ANTHROPIC_API_KEY=sk-ant-...
+```
+
+---
+
+## Quick Start
+
+The minimal example — planning-with-files inside a BoxLite VM:
+
+```python
+import asyncio
+from pathlib import Path
+from claudebox import ClaudeBox, Skill
+
+# Load the SKILL.md content from the installed skill
+SKILL_MD = Path.home() / ".claude" / "skills" / "planning-with-files" / "SKILL.md"
+
+PLANNING_SKILL = Skill(
+    name="planning-with-files",
+    description="Manus-style file-based planning with persistent markdown",
+    files={
+        "/root/.claude/skills/planning-with-files/SKILL.md": SKILL_MD.read_text()
+    }
+)
+
+async def main():
+    async with ClaudeBox(
+        session_id="my-project",
+        skills=[PLANNING_SKILL]
+    ) as box:
+        result = await box.code(
+            "Plan and implement a user authentication feature for the Express API"
+        )
+        print(result.response)
+
+asyncio.run(main())
+```
+
+Claude Code finds the skill at `/root/.claude/skills/planning-with-files/SKILL.md` inside the VM. The three planning files (`task_plan.md`, `findings.md`, `progress.md`) are written to the box's working directory and persist across sessions.
+
+---
+
+## Persistent Sessions
+
+ClaudeBox workspaces survive restarts. Pick up exactly where you left off:
+
+```python
+async def main():
+    # First session — starts the plan
+    async with ClaudeBox(session_id="auth-feature", skills=[PLANNING_SKILL]) as box:
+        await box.code("Create task_plan.md for the authentication feature")
+
+    # Later session — same workspace, plan files still there
+    async with ClaudeBox.reconnect("auth-feature") as box:
+        await box.code("Continue implementing the login endpoint from the plan")
+
+    # Clean up when done
+    await ClaudeBox.cleanup_session("auth-feature", remove_workspace=True)
+
+asyncio.run(main())
+```
+
+---
+
+## How Hooks Work Inside the VM
+
+ClaudeBox runs Claude Code CLI natively inside the BoxLite micro-VM. This means planning-with-files hooks execute exactly as they do on your local machine:
+
+| Hook | Trigger | What It Does |
+|------|---------|--------------|
+| **PreToolUse** | Before Write, Edit, Bash, Read, Glob, Grep | Reads first 30 lines of `task_plan.md` — keeps goals in attention |
+| **PostToolUse** | After Write, Edit | Reminds agent to update plan status after file changes |
+| **Stop** | When agent finishes | Runs completion check script before stopping |
+
+The hook scripts need to be injected alongside SKILL.md. See the full example in `examples/boxlite/quickstart.py` for how to include them.
+
+---
+
+## Session Recovery
+
+When your context fills up and you run `/clear`, the skill recovers the previous session automatically on next activation. Inside a ClaudeBox session, run manually:
+
+```python
+async with ClaudeBox.reconnect("my-project") as box:
+    await box.code(
+        "Run session catchup: python3 ~/.claude/skills/planning-with-files/scripts/session-catchup.py $(pwd)"
+    )
+```
+
+---
+
+## Snapshots
+
+BoxLite supports checkpointing. Snapshot before a risky implementation phase:
+
+```python
+from claudebox import ClaudeBox
+from boxlite import Box
+
+async def main():
+    async with ClaudeBox(session_id="risky-refactor", skills=[PLANNING_SKILL]) as box:
+        # Phase 1 complete — snapshot before the destructive refactor
+        await box.box.snapshot("pre-refactor")
+
+        result = await box.code("Refactor the database layer")
+
+        if "error" in result.response.lower():
+            await box.box.restore("pre-refactor")
+            print("Rolled back to pre-refactor snapshot")
+
+asyncio.run(main())
+```
+
+---
+
+## Troubleshooting
+
+### Skill not activating inside the VM?
+
+The skill file must be at `/root/.claude/skills/planning-with-files/SKILL.md` inside the VM. Verify by injecting a validation step:
+
+```python
+result = await box.code("ls ~/.claude/skills/planning-with-files/")
+print(result.response)
+```
+
+### Hooks not running?
+
+The Stop hook script (`check-complete.sh`) must also be injected. Add it to the `files` dict in your Skill object. See `examples/boxlite/quickstart.py` for the full implementation.
+
+### Docker not found?
+
+ClaudeBox uses Docker to pull OCI images for the VM. Install Docker Desktop (macOS/Windows) or Docker Engine (Linux). The sandbox itself does not run as a Docker container — Docker is only used for image management.
+
+### BoxLite not available on Windows host?
+
+BoxLite requires Linux KVM (Linux) or Hypervisor.framework (macOS). On Windows, use WSL2 with KVM enabled.
+
+---
+
+## See Also
+
+- [BoxLite documentation](https://docs.boxlite.ai)
+- [ClaudeBox repository](https://github.com/boxlite-ai/claudebox)
+- [boxlite-mcp](https://github.com/boxlite-labs/boxlite-mcp) — MCP server for BoxLite sandboxing
+- [Quick Start Guide](quickstart.md)
+- [Workflow Diagram](workflow.md)
+- [Author: @OthmanAdi](https://github.com/OthmanAdi)
@@ -0,0 +1,186 @@
+# Mastra Code Setup
+
+Using planning-with-files with [Mastra Code](https://code.mastra.ai/).
+
+---
+
+## Overview
+
+Mastra Code auto-discovers skills from `.mastracode/skills/` directories. It also has built-in Claude Code compatibility, so it reads `.claude/skills/` too — but the dedicated `.mastracode/` integration gives you native hooks support.
+
+## Installation
+
+### Method 1: Workspace Installation (Recommended)
+
+Share the skill with your entire team by adding it to your repository:
+
+```bash
+# In your project repository
+git clone https://github.com/OthmanAdi/planning-with-files.git /tmp/planning-with-files
+
+# Copy the Mastra Code skill to your repo
+cp -r /tmp/planning-with-files/.mastracode .
+
+# Commit to share with team
+git add .mastracode/
+git commit -m "Add planning-with-files skill for Mastra Code"
+git push
+
+# Clean up
+rm -rf /tmp/planning-with-files
+```
+
+Now everyone on your team using Mastra Code will have access to the skill.
+
+### Method 2: Personal Installation
+
+Install just for yourself:
+
+```bash
+# Clone the repo
+git clone https://github.com/OthmanAdi/planning-with-files.git /tmp/planning-with-files
+
+# Copy skill to your personal Mastra Code skills folder
+mkdir -p ~/.mastracode/skills
+cp -r /tmp/planning-with-files/.mastracode/skills/planning-with-files ~/.mastracode/skills/
+
+# Copy hooks (required for plan enforcement)
+# If you already have ~/.mastracode/hooks.json, merge the entries manually
+cp /tmp/planning-with-files/.mastracode/hooks.json ~/.mastracode/hooks.json
+
+# Clean up
+rm -rf /tmp/planning-with-files
+```
+
+> **Note:** If you already have a `~/.mastracode/hooks.json`, do not overwrite it. Instead, merge the PreToolUse, PostToolUse, and Stop entries from the skill's hooks.json into your existing file.
+
+### Verification
+
+```bash
+ls -la ~/.mastracode/skills/planning-with-files/SKILL.md
+```
+
+Restart your Mastra Code session. The skill auto-activates when you work on complex tasks.
+
+---
+
+## How It Works
+
+### Hooks (via hooks.json)
+
+Mastra Code uses a separate `hooks.json` file for lifecycle hooks. This is different from Claude Code, which defines hooks in SKILL.md frontmatter. Mastra Code reads hooks from:
+
+1. `.mastracode/hooks.json` (project-level, highest priority)
+2. `~/.mastracode/hooks.json` (global)
+
+This integration includes a pre-configured `hooks.json` with all three hooks:
+
+| Hook | Matcher | What It Does |
+|------|---------|--------------|
+| **PreToolUse** | Write, Edit, Bash, Read, Glob, Grep | Reads first 30 lines of `task_plan.md` to keep goals in attention |
+| **PostToolUse** | Write, Edit | Reminds you to update plan status after file changes |
+| **Stop** | (all) | Runs `check-complete.sh` to verify all phases are done |
+
+### Auto-Activation
+
+The skill activates when you:
+- Mention "complex task" or "multi-step project"
+- Ask to "plan out" or "break down" work
+- Request help organizing or tracking progress
+- Start research tasks requiring >5 tool calls
+
+### The Three Files
+
+Once activated, the skill creates:
+
+| File | Purpose | Location |
+|------|---------|----------|
+| `task_plan.md` | Phases, progress, decisions | Your project root |
+| `findings.md` | Research, discoveries | Your project root |
+| `progress.md` | Session log, test results | Your project root |
+
+---
+
+## Claude Code Compatibility
+
+Mastra Code reads from `.claude/skills/` as a fallback. If you already have planning-with-files installed for Claude Code, it will work — but the dedicated `.mastracode/` installation gives you:
+
+- Native hooks via `hooks.json` (PreToolUse, PostToolUse, Stop)
+- Correct script path resolution for Mastra Code directories
+- No path conflicts with Claude Code plugin root
+
+---
+
+## Session Recovery
+
+When your context fills up and you run `/clear`, the skill can recover your previous session.
+
+Run manually:
+
+```bash
+# Linux/macOS
+python3 ~/.mastracode/skills/planning-with-files/scripts/session-catchup.py "$(pwd)"
+```
+
+```powershell
+# Windows PowerShell
+python "$env:USERPROFILE\.mastracode\skills\planning-with-files\scripts\session-catchup.py" (Get-Location)
+```
+
+---
+
+## Team Workflow
+
+### Workspace Skills (Recommended)
+
+With workspace installation (`.mastracode/skills/`):
+- Everyone on team has the skill
+- Consistent planning across projects
+- Version controlled with your repo
+- Changes sync via git
+
+### Personal Skills
+
+With personal installation (`~/.mastracode/skills/`):
+- Use across all your projects
+- Keep it even if you switch teams
+- Not shared with teammates
+
+---
+
+## Troubleshooting
+
+### Skill Not Activating?
+
+1. Verify the file exists: `ls ~/.mastracode/skills/planning-with-files/SKILL.md`
+2. Restart Mastra Code — skills are scanned on startup
+3. Use trigger phrases: "plan out", "break down", "organize", "track progress"
+
+### Hooks Not Running?
+
+Mastra Code reads hooks from `hooks.json`, not from SKILL.md frontmatter. Verify:
+
+1. Check that `.mastracode/hooks.json` exists in your project root (workspace install) or `~/.mastracode/hooks.json` (personal install)
+2. Verify the file contains PreToolUse, PostToolUse, and Stop entries
+3. Restart Mastra Code after adding or modifying hooks.json
+
+### Already Using Claude Code?
+
+No conflict. Mastra Code checks `.mastracode/skills/` first, then falls back to `.claude/skills/`. You can have both installed.
+
+---
+
+## Support
+
+- **GitHub Issues:** https://github.com/OthmanAdi/planning-with-files/issues
+- **Mastra Code Docs:** https://code.mastra.ai/configuration
+- **Author:** [@OthmanAdi](https://github.com/OthmanAdi)
+
+---
+
+## See Also
+
+- [Quick Start Guide](quickstart.md)
+- [Workflow Diagram](workflow.md)
+- [Manus Principles](../skills/planning-with-files/reference.md)
+- [Real Examples](../skills/planning-with-files/examples.md)
@@ -0,0 +1,26 @@
+# BoxLite Examples
+
+Working examples for running planning-with-files inside [BoxLite](https://boxlite.ai) micro-VM sandboxes via [ClaudeBox](https://github.com/boxlite-ai/claudebox).
+
+## Files
+
+| File | Description |
+|------|-------------|
+| `quickstart.py` | Full Python example — loads planning-with-files as a ClaudeBox Skill, runs a planning session inside a BoxLite VM |
+
+## Requirements
+
+```bash
+pip install claudebox
+export CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-...
+```
+
+## Run
+
+```bash
+python quickstart.py
+```
+
+## Documentation
+
+See [docs/boxlite.md](../../docs/boxlite.md) for the full integration guide.
@@ -0,0 +1,122 @@
+"""
+planning-with-files + BoxLite quickstart
+
+Runs Claude Code with the planning-with-files skill inside a BoxLite micro-VM.
+The skill is injected into the VM filesystem via ClaudeBox's Skill API.
+
+Requirements:
+    pip install claudebox
+    export CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-...
+
+Usage:
+    python quickstart.py
+"""
+
+import asyncio
+from pathlib import Path
+
+from claudebox import ClaudeBox, Skill
+
+
+def load_skill() -> Skill:
+    """
+    Build a ClaudeBox Skill from the planning-with-files SKILL.md.
+
+    Reads the SKILL.md from your local Claude Code skills directory.
+    If not installed locally, falls back to fetching from the repo.
+    """
+    skill_base = Path.home() / ".claude" / "skills" / "planning-with-files"
+    skill_md_path = skill_base / "SKILL.md"
+    check_complete_path = skill_base / "scripts" / "check-complete.sh"
+
+    if not skill_md_path.exists():
+        raise FileNotFoundError(
+            "planning-with-files is not installed locally.\n"
+            "Install it first:\n"
+            "  /plugin marketplace add OthmanAdi/planning-with-files\n"
+            "  /plugin install planning-with-files@planning-with-files"
+        )
+
+    files = {
+        "/root/.claude/skills/planning-with-files/SKILL.md": skill_md_path.read_text(),
+    }
+
+    # Include the stop hook script if available
+    if check_complete_path.exists():
+        files["/root/.claude/skills/planning-with-files/scripts/check-complete.sh"] = (
+            check_complete_path.read_text()
+        )
+
+    return Skill(
+        name="planning-with-files",
+        description=(
+            "Manus-style file-based planning. Creates task_plan.md, findings.md, "
+            "and progress.md. Use for complex multi-step tasks requiring >5 tool calls."
+        ),
+        files=files,
+    )
+
+
+async def main():
+    skill = load_skill()
+
+    print("Starting BoxLite VM with planning-with-files skill...")
+
+    async with ClaudeBox(
+        session_id="planning-demo",
+        skills=[skill],
+    ) as box:
+        print("VM running. Invoking planning session...\n")
+
+        result = await box.code(
+            "/planning-with-files:plan\n\n"
+            "Task: Build a REST API endpoint for user authentication with JWT tokens. "
+            "Plan the implementation phases, identify the key files to create, "
+            "and list the dependencies needed."
+        )
+
+        print("=== Claude Code Output ===")
+        print(result.response)
+        print("==========================")
+
+        # Show what planning files were created inside the VM
+        files_result = await box.code(
+            "ls -la task_plan.md findings.md progress.md 2>/dev/null && "
+            "echo '---' && head -20 task_plan.md 2>/dev/null"
+        )
+        print("\n=== Planning Files in VM ===")
+        print(files_result.response)
+
+    print("\nSession complete. Workspace persists at ~/.claudebox/sessions/planning-demo")
+    print("Reconnect later with: ClaudeBox.reconnect('planning-demo')")
+
+
+async def persistent_session_example():
+    """
+    Example of a multi-session workflow.
+    Session 1 creates the plan. Session 2 continues from it.
+    """
+    skill = load_skill()
+
+    # Session 1
+    async with ClaudeBox(session_id="multi-session-demo", skills=[skill]) as box:
+        await box.code(
+            "/planning-with-files:plan\n\n"
+            "Task: Refactor the user service to support multi-tenancy."
+        )
+        print("Session 1 complete. Plan created inside VM.")
+
+    # Session 2 — same workspace, plan files intact
+    async with ClaudeBox.reconnect("multi-session-demo") as box:
+        result = await box.code(
+            "Read task_plan.md and continue with the next incomplete phase."
+        )
+        print("Session 2:", result.response[:200])
+
+    # Clean up
+    await ClaudeBox.cleanup_session("multi-session-demo", remove_workspace=True)
+    print("Workspace cleaned up.")
+
+
+if __name__ == "__main__":
+    asyncio.run(main())
@@ -1,17 +1,8 @@
 ---
 name: planning-with-files
-version: "2.10.0"
-description: Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls. Now with automatic session recovery after /clear.
+description: Implements Manus-style file-based planning to organize and track progress on complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when asked to plan out, break down, or organize a multi-step project, research task, or any work requiring >5 tool calls. Supports automatic session recovery after /clear.
 user-invocable: true
-allowed-tools:
-  - Read
-  - Write
-  - Edit
-  - Bash
-  - Glob
-  - Grep
-  - WebFetch
-  - WebSearch
+allowed-tools: "Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch"
 hooks:
  PreToolUse:
    - matcher: "Write|Edit|Bash|Read|Glob|Grep"
@@ -51,6 +42,8 @@ hooks:
            else
              sh "$SCRIPT_DIR/check-complete.sh"
            fi
+metadata:
+  version: "2.16.1"
 ---

 # Planning with Files
Author	SHA1	Message	Date
OthmanAdi	acfd2f0c74	fix(mastra): add hooks.json, fix SKILL.md path var, correct docs Mastra Code reads hooks from .mastracode/hooks.json, not SKILL.md frontmatter. All three hooks (PreToolUse, PostToolUse, Stop) were silently non-functional. Added hooks.json with proper Mastra format including matchers and timeouts. Fixed MASTRACODE_SKILL_ROOT env var (does not exist in Mastra Code). Corrected docs/mastra.md to accurately describe the hooks.json system and fixed personal install instructions to include the hooks file.	2026-02-26 19:43:46 +01:00
OthmanAdi	931bb545ab	fix: stretch Star History chart to full width	2026-02-26 19:01:16 +01:00
OthmanAdi	15e33d261a	fix(copilot): complete PS1 encoding fix - Get-Content UTF8 + no-BOM (Issue #82 ) v2.16.1 fixed the output pipe encoding but missed the read side. Get-Content without -Encoding in PS5 reads files with the system ANSI code page (Windows-1252), corrupting non-ASCII characters in task_plan.md and SKILL.md before they reach the output pipe. Changes to pre-tool-use.ps1, session-start.ps1, agent-stop.ps1: - All Get-Content calls: added -Encoding UTF8 - [System.Text.Encoding]::UTF8 replaced with [System.Text.UTF8Encoding]::new($false) — UTF-8 without BOM, preventing stray 0xEF 0xBB 0xBF preamble in JSON output Closes #82	2026-02-26 18:59:05 +01:00
OthmanAdi	6e8f128a79	feat: BoxLite sandbox runtime integration (Issue #84 ) Adds documentation and examples for running planning-with-files inside BoxLite micro-VM sandboxes via ClaudeBox. - docs/boxlite.md: full integration guide covering ClaudeBox Skill API, persistent sessions, hooks behavior inside the VM, snapshots, session recovery, and troubleshooting - examples/boxlite/quickstart.py: working Python example using ClaudeBox's Skill object to inject planning-with-files into a VM - examples/boxlite/README.md: example context and requirements - README: new Sandbox Runtimes section (BoxLite is infrastructure, not an IDE - kept separate from the 16-platform IDE table) - README: BoxLite badge, Documentation table entry, version bump to 2.18.0, file structure updated - CHANGELOG: v2.18.0 entry with full details - CONTRIBUTORS: @DorianZheng added for Issue #84 BoxLite loads via pip install claudebox - no .boxlite/ folder needed since ClaudeBox uses a Python Skill object, not file-system discovery. Closes #84	2026-02-26 18:45:54 +01:00
OthmanAdi	7a0d05145a	chore: untrack orphaned draft files WIKI_HOME_PAGE.md and DISCUSSION_2_CONTENT.md were leftover scaffolding — wiki draft never published and old discussion post content. Removed from tracking, added to .gitignore.	2026-02-25 23:34:16 +01:00
OthmanAdi	d1ee93c567	release: v2.17.0 Bump plugin manifest to 2.17.0 so Claude Code pulls fresh on reinstall. Update CHANGELOG, README version badge, and releases table.	2026-02-25 21:22:31 +01:00
OthmanAdi	f45b39a967	fix: bump canonical SKILL.md metadata.version to 2.16.1 PR #83 correctly moved version to metadata.version but left the stale 2.10.0 value. All IDE files had 2.16.1, canonical was the only one still showing 2.10.0.	2026-02-25 21:15:26 +01:00
OthmanAdi	af533413ca	fix(skill-metadata): apply PR #83 description fix to Group C IDEs Gemini, AdaL, Agent, Factory, Pi — no allowed-tools or version fields, description-only update to match canonical trigger terms. Pi name (pi-planning-with-files) and Agent license field preserved.	2026-02-25 21:06:13 +01:00
OthmanAdi	461fc525de	fix(skill-metadata): apply PR #83 spec fixes to Group B IDEs Continue, OpenClaw — no allowed-tools field so that fix doesn't apply. - Removed top-level version field - Updated description with trigger terms - Added metadata.version: "2.16.1" in correct block YAML location OpenClaw: inline JSON metadata expanded to proper block YAML, openclaw.os array preserved exactly.	2026-02-25 21:03:33 +01:00
OthmanAdi	8104801106	fix(skill-metadata): apply PR #83 spec fixes to Group A IDEs Codex, Cursor, Kilocode, CodeBuddy, OpenCode — all had: - allowed-tools as invalid YAML list → fixed to comma-separated string - version at top-level frontmatter → moved to metadata.version - description missing trigger terms → updated to match canonical Each file's IDE-specific SCRIPT_DIR env var preserved exactly. Version bumped to 2.16.1 (current release) across all.	2026-02-25 20:55:24 +01:00
OthmanAdi	a8ce293833	feat: add Mastra Code support (platform #16 ) - Created .mastracode/skills/planning-with-files/ with full hooks integration (PreToolUse, PostToolUse, Stop — native Mastra Code hook support) - SKILL.md ships with PR #83 fixes pre-applied: comma-separated allowed-tools, metadata.version in standard location, enriched trigger terms - Includes references, scripts (cross-platform), and templates - Added docs/mastra.md installation guide (workspace + personal methods) - Updated README: IDE table, badge, file structure, docs table, platform count	2026-02-25 20:28:49 +01:00
OthmanAdi	d604849947	docs: add @popey as contributor, switch to RepoStars widget - Added @popey to contributors table for skill metadata fixes (PR #83) - Replaced star-history.com chart with RepoStars copper theme embed	2026-02-25 20:04:46 +01:00
Ahmad Othman Ammar Adi.	0f2a9cfba4	Merge pull request #83 from popey/improve/skill-review-optimization feat: improve skill metadata and description for better discoverability	2026-02-25 20:01:14 +01:00
Alan PopeandClaude Opus 4.6	428728f5f2	feat: improve skill metadata and description for better discoverability Changes to planning-with-files skill: \| Area \| Before \| After \| \|------\|--------\|-------\| \| Description score \| 0% (blocked) \| 100% \| \| Content score \| 0% (blocked) \| 100% \| \| allowed-tools format \| YAML list (invalid) \| comma-separated string (valid) \| \| metadata.version \| missing \| added (2.10.0) \| \| trigger terms \| limited \| added "plan out", "break down", "organize", "track progress" \| - Fixed `allowed-tools` from YAML list to string format (was causing validation failure) - Moved `version` from top-level frontmatter to `metadata.version` (standard location) - Enriched description with natural trigger terms for better skill matching - No changes to skill behaviour, templates, scripts, or content Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>	2026-02-24 19:44:05 +00:00