PowerShell named-plan slug mode (#247), exact planning filename boundary for session catchup across every shipped copy (#248), and selector-routed active-pointer replacement with planning-root containment in both initializers (#249), plus the maintainer follow-ups from the release review. CHANGELOG entry, contributor credits for @ShaunLinTW and @kuei51307-hub, README releases row, CITATION date, and the script-driven parity bump of the 19 tracked version files.
3.8 KiB
Windows Setup
Windows-specific installation and usage notes.
Installation on Windows
Via winget (Recommended)
Claude Code supports Windows Package Manager:
winget install Anthropic.ClaudeCode
Then install the skill:
/plugin marketplace add OthmanAdi/planning-with-files
/plugin install planning-with-files@planning-with-files
Local Plugin Development
git clone https://github.com/OthmanAdi/planning-with-files.git
claude --plugin-dir .\planning-with-files
--plugin-dir is session-only. Marketplace installs are managed by Claude Code under %USERPROFILE%\.claude\plugins\cache\; do not clone into or edit that cache.
Skills Only
git clone https://github.com/OthmanAdi/planning-with-files.git
New-Item -ItemType Directory -Force -Path "$env:USERPROFILE\.claude\skills" | Out-Null
Copy-Item -Recurse planning-with-files\skills\planning-with-files $env:USERPROFILE\.claude\skills\
Path Differences
| Unix/macOS | Windows |
|---|---|
~/.claude/skills/ |
%USERPROFILE%\.claude\skills\ |
~/.claude/plugins/cache/ |
%USERPROFILE%\.claude\plugins\cache\ |
Local checkout passed to --plugin-dir |
Any explicit Windows path, including paths with spaces |
Shell Script Compatibility
The helper scripts (init-session.sh, check-complete.sh) are bash scripts.
Option 1: Use Git Bash
If you have Git for Windows installed, run scripts in Git Bash:
./scripts/init-session.sh
Option 2: Use WSL
wsl ./scripts/init-session.sh
Option 3: Native PowerShell
init-session.ps1 is the PowerShell twin of the shell initializer. Since v3.19.0 it supports the same named-plan flow for parallel sessions:
.\scripts\init-session.ps1 # legacy root mode: task_plan.md next to your code
.\scripts\init-session.ps1 "Backend Refactor" # named plan under .planning\<date>-backend-refactor\
.\scripts\init-session.ps1 -PlanDir # named plan with a generated untitled-<id> slug
.\scripts\set-active-plan.ps1 -List # list named plans and the shared pointer
A positional project name creates a named plan, matching init-session.sh. The Cursor native PowerShell hooks still read only the root task_plan.md, so use zero-argument root mode there if you rely on hook injection.
Option 4: Manual alternative
Instead of running scripts, manually create the files:
# Copy templates to current directory
Copy-Item templates\task_plan.md .
Copy-Item templates\findings.md .
Copy-Item templates\progress.md .
Hook Commands
Claude Code plugin hooks use the cache-safe ${CLAUDE_PLUGIN_ROOT} and a Unix-compatible shell. On Windows:
- Hooks run in a Unix-compatible shell environment
- Commands like
cat,head,echowork automatically - No changes needed to the skill configuration
Common Windows Issues
Path separators
If you see path errors, ensure you're using the correct separator:
# Windows
$env:USERPROFILE\.claude\skills\
# Not Unix-style
~/.claude/skills/
Line endings
If templates appear corrupted, check line endings:
# Convert to Windows line endings if needed
(Get-Content template.md) | Set-Content -Encoding UTF8 template.md
Permission errors
Run PowerShell as Administrator if you get permission errors:
# Right-click PowerShell → Run as Administrator
Terminal Recommendations
For best experience on Windows:
- Windows Terminal - Modern terminal with good Unicode support
- Git Bash - Unix-like environment on Windows
- WSL - Full Linux environment
Need Help?
Open an issue at github.com/OthmanAdi/planning-with-files/issues.