test: validate install.ps1 + uninstall.ps1 on native Windows PowerShell

[evemcgivern]

Context

`install.ps1` and `uninstall.ps1` were written but never run on real Windows hardware. We need someone with native Windows + PowerShell 5.1+ (or PowerShell 7) to validate the install/uninstall flow end-to-end and report any quirks.

Acceptance criteria

• Clone the toolkit on Windows
• Run `.\install.ps1` — confirm it auto-detects `.claude` (or `.agents`), copies skill, seeds config
• Run `.\install.ps1 -Target "$HOME.agents"` — confirm `-Target` override works
• Run `.\install.ps1 -Help` — confirm help text renders
• Run `python work_plan.py --help` against the installed copy — confirm it executes
• Run `.\uninstall.ps1` — confirm it removes only the marker-verified copies, leaves config + notes alone
• Open an issue or comment here with any quirks found (path-separator weirdness, encoding issues, prompt behavior, etc.)

If everything works flawlessly, the acceptance is just "ran all of the above, nothing broke" — that's still a valuable result.

Pointers

• `install.ps1` and `uninstall.ps1` at the toolkit root
• README "Requirements" section lists the Windows install one-liners for the four prereqs (`winget install ...`)
• The marker file pattern (`.installed-from` inside each copied skill dir) is what makes uninstall safe

Effort

~20-30 minutes if everything works; longer if you find quirks worth fixing in the same PR.

[snakefood3232]

I'd validate install.ps1 and uninstall.ps1 on a native Windows setup, ensuring it auto-detects directories like ~\.claude and supports -Target overrides. I'll run through the steps, including executing python work_plan.py --help to confirm installation integrity. Can have a PR up in about 2 days, assuming no major quirks arise. I've built similar automation scripts for Windows environments in the past, which ensures a quick turnaround and thorough testing.

[evemcgivern]

Still relevant after the plugin conversion — and the script changed, so the criteria need refreshing.

The plugin (/plugin install work-plan@stylus-nexus) is the recommended path on Claude Code, but install.ps1 remains the supported fallback for direct/Cursor/Codex-skills-dir users and was substantially changed in the plugin-packaging work (PRs #83/#85). New behavior to validate on native Windows:

• Installs the bin/work-plan.cmd launcher into <target>\bin\ and work-plan --version resolves through it.
• Copies the standalone dispatcher from installer\work-plan.md (not commands\work-plan.md) → ~\.claude\commands\work-plan.md; the per-verb suite is NOT copied (plugin-only).
• Config self-seeds at ~\.claude\work-plan\config.yml via the CLI (one config home, even with -Target ...\.agents).
• uninstall.ps1 removes the launcher (work-plan.cmd + work-plan) and the dispatcher.

(Original prereq/auto-detect criteria above still apply.)