Humanlayer Riptide Rpi
- 8 repo stars
- Updated December 29, 2025
- humanlayer/riptide-rpi
humanlayer-riptide-rpi is a Claude Code plugin that runs a Research–Plan–Implement workflow on Linear tickets before code changes land.
About
humanlayer-riptide-rpi is a Claude Code plugin that packages the Riptide Research–Plan–Implement workflow for work tracked in Linear. developers and small teams who ship with agents often paste a ticket ID and get a PR before the problem is understood; RPI splits the job into explicit research, a written plan tied to the issue, and implementation only after that gate. The plugin is aimed at developers using Claude Code alongside Linear for backlog and delivery, especially when tickets are vague or touch unfamiliar parts of the codebase. Install it when you want a repeatable agent methodology instead of one-shot “fix this ticket” prompts. It complements Linear integrations and coding skills by governing how the agent sequences work, not by replacing issue tracking or deployment tooling.
- Research–Plan–Implement (RPI) ritual tuned for Linear tickets
- Forces context gathering before implementation on agent-driven tasks
- Aligns agent output with ticket scope instead of ad-hoc coding
- Workflow plugin (process skill), not a standalone Linear MCP server
- Single-plugin bundle from humanlayer/riptide-rpi
Humanlayer Riptide Rpi by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install humanlayer-riptide-rpi@humanlayer/riptide-rpiAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 8 |
|---|---|
| Last updated | December 29, 2025 |
| Repository | humanlayer/riptide-rpi ↗ |
What it does
Run a structured Research–Plan–Implement loop on Linear issues so Claude does not jump straight into code on under-specified tickets.
Who is it for?
Best when you use Claude Code with Linear and want a fixed RPI ritual on every non-trivial ticket.
Skip if: Skip if you're not on Linear, one-off scripts with no issue tracker, or leaders and only need raw Linear API access without a process layer.
What you get
Each Linear issue gets a disciplined research and plan phase, then implementation that matches the ticket and approved plan.
- Research notes grounded in the Linear ticket and codebase
- An implementation plan aligned to the issue before code edits
- Implementation work that follows the approved RPI steps
By the numbers
- 1 plugin in the bundle (pluginCount: 1)
- Repository humanlayer/riptide-rpi (7 GitHub stars in catalog ingest)
Recommended Plugins
0oastro Kawai Girl Output StyleTransform Claude's responses into kawaii anime girl style\!3
0xbigboss Claude CodeComprehensive configuration system for Claude Code51
2lab Ai Oh My ClaudeClaude Code plugin for AI-powered iterative development loops.37
45ck Claude Sdlc PluginClaude Code plugin for SDLC workflow automation with Storybook planning hub1
70 10 Claude Code Plugins70-10's Claude Code plugins
Aaronbassett Agent FoundryMy personal plugin marketplace for Claude Code4How it compares
Ticket workflow methodology plugin, not a Linear MCP connector or generic coding skill.
FAQ
Who is Humanlayer Riptide Rpi for?
It is for Claude Code users who manage work in Linear and want Research–Plan–Implement enforced on agent-driven tickets.
When should I use Humanlayer Riptide Rpi?
Use it when starting or continuing a Linear issue where jumping straight to code would risk wrong scope, missing context, or unreadable diffs.
How do I add Humanlayer Riptide Rpi to my agent?
Register the humanlayer/riptide-rpi Claude Code plugin from the repo, ensure Linear is reachable in your environment, then invoke the RPI workflow against a ticket ID or URL.