ralph-wiggum-pm

Automate Linear ticket consumption, implementation, PR creation, and review quality gates.

Updated Mar 12, 2026
One-click install
npx skills add https://github.com/LSDIPPOLLC/ai-orchestration --skill ralph-wiggum-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ralph-wiggum-pm
Source: https://github.com/LSDIPPOLLC/ai-orchestration/tree/main/.claude/skills/ralph-wiggum-pm
Command: npx skills add https://github.com/LSDIPPOLLC/ai-orchestration --skill ralph-wiggum-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ralph Wiggum: Project Manager removes the daily grind of manually consuming Linear tickets, implementing changes, running review/quality checks, merging code, and creating follow-up work—so project execution keeps moving without constant human coordination.

Core Features & Use Cases

  • Continuous Linear ticket consumption: Finds the highest-priority unblocked issue in the chosen Linear project (Todo/Backlog), moves it to In Progress, and starts work.
  • End-to-end execution with review and safeguards: Creates a feature branch (for code tasks), implements the work, creates a PR, runs code review, and runs UI quality gates when applicable.
  • Automatic completion logging and follow-up generation: Moves issues to Done (or In Review when needed), records a detailed completion comment, and generates new Linear issues from discovered bugs/improvements/decisions/planning needs.
  • Session recording for visibility: Records consumed and generated ticket activity for the project’s sessions/tracking website pages.

Quick Start

Run the loop for a specific Linear project by issuing: /ralph-wiggum-pm MyProject.

Frequently Asked Questions about ralph-wiggum-pm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Linear ticket processing from implementation to PR generation?

Automate Linear ticket processing by using a deterministic loop that consumes the highest-priority unblocked issue, implements the code, generates a PR, and runs review and quality gates automatically. This removes manual project coordination and keeps execution moving continuously.

Can I automatically run code review and UI quality gates when implementing Linear issues?

Yes, automated code review and UI quality gates run during the execution cycle after a feature branch is created and code is implemented. If quality gates fail, the cycle applies retry and degradation rules so progress continues rather than halting the workflow.

Does Linear ticket automation require any specific MCP tool access to function?

Yes, Linear ticket automation requires Linear MCP tool access to consume issues, move them through Todo, In Progress, Done, or In Review statuses, log detailed completion comments, and generate new follow-up issues from discovered bugs or planning needs.

How does automated workflow orchestration handle follow-up work and session recording?

Automated workflow orchestration handles follow-up work by generating new Linear issues from discovered bugs, improvements, and decisions. It records consumed and generated ticket activity on project session tracking pages to provide full execution visibility.

What happens when quality gates or sub-skills fail during ticket automation?

When quality gates or sub-skills fail during ticket automation, the deterministic loop applies retry and degradation rules so cycles continue running. This ensures continuous project execution even when individual review or quality checks encounter errors.

Is continuous project execution suitable for processing multiple Linear projects simultaneously?

Continuous project execution operates within a single project scope, processing issues in priority order. You run the loop for a specific Linear project by issuing a command with your project name, and it autonomously grinds those tickets to done.