By schylerchase
Bridges GSD strategic context with CE-quality implementation planning. Produces code-grounded plans with implementation units, test scenarios, feasibility review, and UX-first frontend evaluation.
Configure deep-plan adaptive model routing for the current GSD project. Runs the first-run setup wizard when `.planning/config.json` lacks `deep_plan.model_routing`, and shows a granular edit menu for existing configs.
Diagnose deep-plan install health and project readiness. Use when deep-plan feels broken, when checking if a fresh install is complete, or before running /deep-plan for the first time in a project. Runs install checks (Claude Code, GSD, CE, deep-plan agents) and project checks (GSD artifacts, phase readiness, warm-start data), prints a structured remediation report, and offers to auto-fix fixable issues.
Export phase artifacts as portable handoff bundle for cross-model planning workflows
Check for and install the latest Claude Code deep-plan plugin release from the configured marketplace
UX review with optional fix workflow. Scans frontend files, produces a severity-rated findings report with numbered IDs, then offers to fix all, critical-only, or specific issues.
Validates GSD PLAN.md files against executor expectations — frontmatter schema, task XML structure, must_haves validity, @-reference resolution, and consistency checks. Use this agent when a PLAN.md has been written and needs structural validation before execution. Examples: <example> Context: deep-plan skill has just written a PLAN.md user: "deep plan phase 3" assistant: "Plan written. Running structural validation..." <commentary> After Step 8 (write plan), deep-plan automatically spawns plan-validator to catch format errors that would break gsd-executor. </commentary> </example> <example> Context: User wants to validate an existing plan user: "validate my plan for phase 5" assistant: "I'll use the plan-validator agent to check the PLAN.md structure." <commentary> Direct validation request — user wants to verify a plan before running gsd-execute-phase. </commentary> </example>
Evaluates frontend UI/UX quality against usability heuristics, state design completeness, accessibility standards, interaction patterns, and visual design. Produces a severity-rated findings report with numbered IDs for selective fixing. Use when reviewing existing frontends, after implementing UI changes, or before creating PRs that touch user-facing code. Examples: <example> Context: User wants to review frontend quality after implementing a feature user: "/ux-review src/components/" assistant: "I'll spawn the ux-reviewer agent to evaluate the frontend code..." <commentary> The /ux-review command parses the path argument and spawns this agent to scan and evaluate. </commentary> </example> <example> Context: User wants a UX audit before creating a PR user: "review the UX of my dashboard before I ship" assistant: "I'll use the ux-reviewer agent to check your dashboard code for UX issues." <commentary> Direct review request — agent scans frontend files, evaluates against red flags, and produces a structured findings report. </commentary> </example>
This skill should be used when the user asks to 'deep plan', 'plan a phase deeply', 'run deep-plan', or wants CE-quality implementation planning after /gsd-discuss-phase. Bridges GSD context with code-grounded research, implementation units, test scenarios, and optional feasibility review. Produces GSD-compatible PLAN.md files.
UX-first frontend design for any web work — pages, apps, dashboards, components. Enforces state design, accessibility, interaction quality, and information architecture before aesthetics. Detects existing design systems. Evaluates and identifies bad UI/UX. Use for both creating new interfaces and reviewing existing ones.
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Bridges GSD strategic planning with Compound Engineering implementation planning. Catches build-breaking issues before execution starts.
For a fresh machine, use the deploy bootstrap. It configures the public Claude Code and Codex plugin paths for Deep Plan, Compound Engineering, and Caveman, bridges an existing GSD install into Codex, initializes RTK when available, and prints manual steps for anything that is private or credential-gated.
curl -fsSL https://raw.githubusercontent.com/schylerchase/deep-plan-plugin/main/deploy.sh | bash -s -- --yes
From a cloned checkout:
./deploy.sh --yes
Useful variants:
./deploy.sh --claude-only
./deploy.sh --codex-only
./deploy.sh --dry-run
./deploy.sh --upgrade --yes
GSD is still distributed through its own community channel. The deploy script verifies it and links ~/.claude/get-shit-done into ~/.codex/get-shit-done when present, but it does not fetch private/community-gated assets.
If you already have GSD and Compound Engineering installed:
macOS / Linux:
curl -fsSL https://raw.githubusercontent.com/schylerchase/deep-plan-plugin/main/setup.sh | bash
Windows (PowerShell):
irm https://raw.githubusercontent.com/schylerchase/deep-plan-plugin/main/setup.ps1 | iex
Or manually (all platforms):
claude plugin marketplace add https://github.com/schylerchase/deep-plan-plugin.git
claude plugin install deep-plan@deep-plan-plugin
The deploy script is the easiest Codex path because Codex currently registers marketplaces separately from enabled plugin blocks:
./deploy.sh --codex-only --yes
Manual Codex install:
codex plugin marketplace add https://github.com/schylerchase/deep-plan-plugin
printf '\n[plugins."deep-plan@deep-plan-plugin"]\nenabled = true\n' >> ~/.codex/config.toml
Restart Codex after changing plugin configuration.
Windows — No ED25519 host key is known for github.com
Fresh Windows installs often hit this because SSH has never connected to GitHub before. Two fixes:
Option A — Use explicit HTTPS URLs (works for both plugins):
For Compound Engineering:
claude plugin marketplace add https://github.com/EveryInc/compound-engineering-plugin.git
claude plugin install compound-engineering@compound-engineering-plugin
For deep-plan:
claude plugin marketplace add https://github.com/schylerchase/deep-plan-plugin
claude plugin install deep-plan@deep-plan-plugin
Option B — Trust GitHub's SSH host key (PowerShell):
ssh-keyscan -t ed25519,rsa github.com >> "$env:USERPROFILE\.ssh\known_hosts"
Then re-run the install.
Windows — Resetting a broken install (manual cleanup)
If a previous install attempt failed partway through and you're seeing stale marketplace errors, zombie marketplace cache directories, or SSH host-key failures from earlier attempts, run these steps in a regular (non-admin) PowerShell window. They're safe to re-run — "not installed" and "not found" errors during cleanup are expected and harmless.
1. Close Claude Code completely. All windows. Check Task Manager for leftover claude processes and kill any survivors — marketplace cache directories can be locked by a running instance.
2. Uninstall any stale CE and deep-plan plugins:
claude plugin uninstall compound-engineering
claude plugin uninstall deep-plan
3. Remove stale marketplace registrations:
claude plugin marketplace remove compound-engineering-plugin
claude plugin marketplace remove compound-engineering-claude-code-plugin
claude plugin marketplace remove deep-plan-plugin
4. Delete leftover marketplace cache directories from previous failed clones:
Remove-Item -Recurse -Force "$env:USERPROFILE\.claude\plugins\marketplaces\compound-engineering-claude-code-plugin" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "$env:USERPROFILE\.claude\plugins\marketplaces\compound-engineering-plugin" -ErrorAction SilentlyContinue
Remove-Item -Recurse -Force "$env:USERPROFILE\.claude\plugins\marketplaces\deep-plan-plugin" -ErrorAction SilentlyContinue
5. Reinstall Compound Engineering from the canonical HTTPS URL:
claude plugin marketplace add https://github.com/EveryInc/compound-engineering-plugin.git
claude plugin install compound-engineering@compound-engineering-plugin
6. Reinstall deep-plan from the canonical HTTPS URL:
claude plugin marketplace add https://github.com/schylerchase/deep-plan-plugin.git
claude plugin install deep-plan@deep-plan-plugin
7. Verify both are registered:
claude plugin list
npx claudepluginhub schylerchase/deep-plan-plugin --plugin deep-planUnity Development Toolkit - Expert agents for scripting/refactoring/optimization, script templates, and Agent Skills for Unity C# development
Complete creative writing suite with 10 specialized agents covering the full writing process: research gathering, character development, story architecture, world-building, dialogue coaching, editing/review, outlining, content strategy, believability auditing, and prose style/voice analysis. Includes genre-specific guides, templates, and quality checklists.
Comprehensive .NET development skills for modern C#, ASP.NET, MAUI, Blazor, Aspire, EF Core, Native AOT, testing, security, performance optimization, CI/CD, and cloud-native applications
Complete collection of battle-tested Claude Code configs from an Anthropic hackathon winner - agents, skills, hooks, and rules evolved over 10+ months of intensive daily use
Modern R development skills for Claude Code - tidyverse patterns, rlang metaprogramming, Bayesian inference, performance optimization, and more
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.