ralph-driven-development-linear_skill

Overview

This skill automates a Ralph Driven Development workflow that pulls issues from a Linear project and runs them sequentially with Codex. It advances issues automatically, tracks progress, and supports configurable retries and timeouts. Use it to turn a Linear backlog into an automated runner that executes tasks end-to-end.

How this skill works

The runner authenticates with Linear MCP, resolves the target project, and fetches open issues in order. For each issue it launches a Codex process (configurable executable and args), monitors execution, records success or failure, and advances the issue on completion. The workflow supports retries, limits on tasks, and dry-run mode to validate configuration without executing Codex.

When to use it

• Automating execution of Linear project issues with minimal manual intervention
• Running sequential Codex agents against a scoped backlog
• Continuously advancing issues after Codex completes tasks
• Testing runner configuration with dry-run before full execution
• Limiting runs with max-tasks or enforcing max attempts per issue

Best practices

• Ensure codex is on the PATH and reachable from your environment
• Authenticate Linear MCP beforehand using codex mcp login linear
• Start with --dry-run to confirm project resolution and AGENTS.MD settings
• Set sensible --codex-timeout and --max-attempts-per-task to avoid runaway runs
• Log outputs to an explicit --log-path so you can audit progress and failures

Example use cases

• Process a VisionOS feature backlog by running Codex against each Linear issue sequentially
• Automate repetitive maintenance tasks tracked in a Linear project and advance completed items
• Limit a pilot run with --max-tasks 3 to validate agent behavior before scaling
• Run with alternative Codex args to test different agent models or safety modes
• Use --dry-run in CI to verify project connectivity and AGENTS.MD parsing