Klausemeister

Use when interactively defining a project or feature PRD from a rough idea, problem statement, or product opportunity. Guides phased multiple-choice discovery for problem framing, user journey, edge cases, creative alternatives, and final PRD drafting. Matches the /prd workflow.

Use when the user wants to schedule a Linear project's tickets across worktree queues, distribute work based on dependencies, or says "schedule this project" / "assign tickets to worktrees" / "plan the work" / "save this schedule". Takes a Linear project, builds a dependency-aware assignment plan, then lets the user save the plan, enqueue it immediately, or cancel.

Use when waiting for a Klausemeister ticket's PR checks, merging the PR, and moving the ticket to Done. Matches the /klause-babysit workflow.

Use when defining a Klausemeister Backlog ticket, assessing its definition depth, stamping a simple/medium/complex label, and moving it to Todo. Matches the /klause-define workflow.

Use when executing a Klausemeister Todo ticket, routing implementation by its simple/medium/complex label, and moving it to In Progress. Matches the /klause-execute workflow.

Use when advancing the current Klausemeister item by reading product state and dispatching to the next workflow command. Matches the /klause-next workflow.

Use when opening a PR for Klausemeister In Progress or In Review work and transitioning the ticket to Testing. Matches the /klause-open-pr workflow.

Use when pulling the next Klausemeister inbox item into the processing slot and creating a branch. Matches the /klause-pull workflow.

Use when moving a completed Klausemeister processing item to the outbox. Matches the /klause-push workflow.

Use when manually reviewing current Klausemeister In Progress work before opening a PR. Matches the /klause-review workflow.

Use when scheduling a Linear project's tickets across Klausemeister worktree queues. Matches the /klause-schedule workflow.

Use immediately at session start on any Claude Code running as a Klausemeister meister (identified by KLAUSE_MEISTER=1 in environment). Reads the workflow loop instructions and begins pulling work from the local Klausemeister MCP server. Applies whenever the session is inside a Klausemeister-managed tmux window and needs to know what to do next.

Use when the user wants to open a pull request, submit work for review, merge a branch, or says "open a PR" / "submit this" / "let's merge" / "ship it" / "push this up". Handles the full PR lifecycle automatically — detects and runs project linters and formatters from CLAUDE.md or Makefile, commits changes following project conventions, rebases on the target branch, resolves simple conflicts, pushes with --force-with-lease, creates the PR via gh, then hands off to the /loop skill to poll for mergeability and merge when ready. Always use this skill when the user asks to create a PR for the current branch.

Interactive spec definition for Linear tickets. Takes a vague ticket and refines it into a complete, structured specification through targeted questions and iterative drafting.