Menu
Fetches a Linear issue and creates a comprehensive plan for implementation.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Autonomous feature development - setup and execution. Triggers on: ralph, set up ralph, run ralph, run the loop, implement tasks. Two phases: (1) Setup - chat through feature, create tasks with dependencies (2) Loop - pick ready tasks, implement, commit, repeat until done.
Preview and screenshot local dev servers and storybooks. Use when asked to view UI components, take screenshots of storybooks, or inspect the web/server apps.
Searches for AMPDO comments in the codebase to gather feedback and execute requested changes.
Guide for writing ast-grep rules to perform structural code search and analysis. Use when users need to search codebases using Abstract Syntax Tree (AST) patterns, find specific code structures, or perform complex code queries that go beyond simple text search. This skill should be used when users ask to search for code patterns, find specific language constructs, or locate code with particular structural characteristics.
| name | work-on-linear-issue |
| description | Fetches a Linear issue and creates a comprehensive plan for implementation. |
Fetches issue details from Linear and guides you through creating a comprehensive implementation plan.
LINEAR_API_KEY environment variable must be set (can also be in .env file)curl and jq must be installedbuiltin:///skills/scripts/work-on-linear-issue <issue-abbreviation>
Examples:
builtin:///skills/scripts/work-on-linear-issue MC-123
builtin:///skills/scripts/work-on-linear-issue https://linear.app/abc/issue/MC-123/issue-title
"AI models are geniuses who start from scratch on every task." — Noam Brown
Onboard yourself to the current task: • Use ultrathink. • Explore the codebase. • Ask questions if needed.
Goal: Be fully prepared to start working on the task.
Take as long as you need to prepare. Over-preparation is better than under-preparation.
Review the issue details fetched from Linear
Examine relevant parts of the codebase
Analyze existing patterns and potential issues
Create a comprehensive plan considering:
Think deeply about edge cases, potential challenges, and best practices
ASK FOR EXPLICIT APPROVAL before starting on the TODO list
Remember: Your task is to create a plan, not to implement changes. Focus on providing a thorough, well-thought-out strategy, then ASK FOR APPROVAL BEFORE STARTING WORK.