komandant

Use when the user invokes /env-check or asks to verify Claude Code env setup in the current repo. Audits per-language LSP plugin enablement (both directions), a linting pre-commit hook, project-local memory, hook-driven git-worktree isolation readiness (a WorktreeCreate hook that creates .worktrees/<branch> and copies .worktreeinclude literally, split provisioning — ops/setup-env.sh with branch-derived ports + COMPOSE_PROJECT_NAME and ops/seed-db.sh with a .seeded-gated DB seed — wired into make up, WorktreeRemove teardown, a PreToolUse cross-worktree edit blocker), and relevance of enabled plugins/MCP servers to the project. Detection runs in parallel Opus subagents; fixes are applied in the main thread.

Use when drafting, writing, or filing a GitHub issue that komandant — or any autonomous coding agent — will implement unattended. Covers the required

Use when the user runs /komandant:setup or asks to install, configure, or bootstrap the komandant daemon after installing the plugin. Interactive postinstall — preflight checks, local go build of the binary, workflow install into ~/.claude/workflows, conversational config.json scaffold, optional launchd service, and the run commands.

Use when handing off to a fresh Claude session in the same worktree — splits the current tmux pane top-bottom (anchored to this session's pane) and launches a new `claude --dangerously-skip-permissions` pre-loaded with an initial prompt. The prompt can be a handoff doc reference (`@<doc>`), a slash command (`/brainstorming`, `/writing-plans @<spec>`, `/subagent-driven-development @<plan>`), or any free-text instruction — pass skill args through verbatim. Triggers on phrases like "continue in new session", "fresh session", "hand off to new claude", or after producing a spec/plan/handoff that's ready for the next phase.

Use when handing off to a fresh Claude session in a brand-new git worktree (isolated branch + tmux window). Runs `wtn` to create the worktree and launches claude pre-loaded with an initial prompt — a handoff doc reference (`@<doc>`), a slash command (`/brainstorming`, `/writing-plans @<spec>`, `/subagent-driven-development @<plan>`), or any free-text instruction; pass skill args through verbatim. Triggers on "continue in worktree", "spin up a worktree", "new branch for this", or after producing a spec/plan/handoff that's ready for the next phase in isolation.