/ralph_plan
Create implementation plan for highest priority Linear ticket ready for spec
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/ralph_plan
Context preview
What this command does when you run it.
Create implementation plan for highest priority Linear ticket ready for spec
Command definition
ralph_plan.mddescription: Create implementation plan for highest priority Linear ticket ready for spec
PART I - IF A TICKET IS MENTIONED
0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md 0d. read the ticket and all comments to learn about past implementations and research, and any questions or concerns about them
PART I - IF NO TICKET IS MENTIONED
0. read .claude/commands/linear.md 0a. fetch the top 10 priority items from linear in status "ready for spec" using the MCP tools, noting all items in the `links` section 0b. select the highest priority SMALL or XS issue from the list (if no SMALL or XS issues exist, EXIT IMMEDIATELY and inform the user) 0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md 0d. read the ticket and all comments to learn about past implementations and research, and any questions or concerns about them
PART II - NEXT STEPS
think deeply
1. move the item to "plan in progress" using the MCP tools 1a. read ./claude/commands/create_plan.md 1b. determine if the item has a linked implementation plan document based on the `links` section 1d. if the plan exists, you're done, respond with a link to the ticket 1e. if the research is insufficient or has unaswered questions, create a new plan document following the instructions in ./claude/commands/create_plan.md
think deeply
2. when the plan is complete, `humanlayer thoughts sync` and attach the doc to the ticket using the MCP tools and create a terse comment with a link to it (re-read .claude/commands/linear.md if needed) 2a. move the item to "plan in review" using the MCP tools
think deeply, use TodoWrite to track your tasks. When fetching from linear, get the top 10 items by priority but only work on ONE item - specifically the highest priority SMALL or XS sized issue.
PART III - When you're done
Print a message for the user (replace placeholders with actual values):
✅ Completed implementation plan for ENG-XXXX: [ticket title]
Approach: [selected approach description]
The plan has been:
Created at thoughts/shared/plans/YYYY-MM-DD-ENG-XXXX-description.md
Synced to thoughts repository
Attached to the Linear ticket
Ticket moved to "plan in review" status
Implementation phases:
- Phase 1: [phase 1 description]
- Phase 2: [phase 2 description]
- Phase 3: [phase 3 description if applicable]
View the ticket: https://linear.app/humanlayer/issue/ENG-XXXX/[ticket-slug]
Read more
description: Create implementation plan for highest priority Linear ticket ready for spec
PART I - IF A TICKET IS MENTIONED
0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md 0d. read the ticket and all comments to learn about past implementations and research, and any questions or concerns about them
PART I - IF NO TICKET IS MENTIONED
0. read .claude/commands/linear.md 0a. fetch the top 10 priority items from linear in status "ready for spec" using the MCP tools, noting all items in the `links` section 0b. select the highest priority SMALL or XS issue from the list (if no SMALL or XS issues exist, EXIT IMMEDIATELY and inform the user) 0c. use `linear` cli to fetch the selected item into thoughts with the ticket number - ./thoughts/shared/tickets/ENG-xxxx.md 0d. read the ticket and all comments to learn about past implementations and research, and any questions or concerns about them
PART II - NEXT STEPS
think deeply
1. move the item to "plan in progress" using the MCP tools 1a. read ./claude/commands/create_plan.md 1b. determine if the item has a linked implementation plan document based on the `links` section 1d. if the plan exists, you're done, respond with a link to the ticket 1e. if the research is insufficient or has unaswered questions, create a new plan document following the instructions in ./claude/commands/create_plan.md
think deeply
2. when the plan is complete, `humanlayer thoughts sync` and attach the doc to the ticket using the MCP tools and create a terse comment with a link to it (re-read .claude/commands/linear.md if needed) 2a. move the item to "plan in review" using the MCP tools
think deeply, use TodoWrite to track your tasks. When fetching from linear, get the top 10 items by priority but only work on ONE item - specifically the highest priority SMALL or XS sized issue.
PART III - When you're done
Print a message for the user (replace placeholders with actual values):
✅ Completed implementation plan for ENG-XXXX: [ticket title] Approach: [selected approach description] The plan has been: Created at thoughts/shared/plans/YYYY-MM-DD-ENG-XXXX-description.md Synced to thoughts repository Attached to the Linear ticket Ticket moved to "plan in review" status Implementation phases: - Phase 1: [phase 1 description] - Phase 2: [phase 2 description] - Phase 3: [phase 3 description if applicable] View the ticket: https://linear.app/humanlayer/issue/ENG-XXXX/[ticket-slug]
The best way to get AI coding agents to solve hard problems in complex codebases.
Repo: humanlayer/humanlayer
Other commands on humanlayer.
- /ci_commit
Create git commits for session changes with clear, atomic messages
Open command - /ci_describe_pr
Generate comprehensive PR descriptions following repository templates
Open command - /commit
Create git commits with user approval and no Claude attribution
Open command - /create_handoff
Create handoff document for transferring work to another session
Open command - /create_plan
Create detailed implementation plans through interactive research and iteration
Open command - /create_plan_generic
Create detailed implementation plans with thorough research and iteration
Open command

