Menu
Plan and work through project, client, vendor, or team offboarding. Use for handovers, access removal, ownership transfer, documentation, credential rotation, data cleanup, and knowledge-transfer checklists.
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
| name | offboard |
| description | Plan and work through project, client, vendor, or team offboarding. Use for handovers, access removal, ownership transfer, documentation, credential rotation, data cleanup, and knowledge-transfer checklists. |
Build a checklist that fits the actual engagement. Inspect available context and ask about missing systems, owners, deadlines, regulatory obligations, and the destination team before proposing actions.
For each item, record owner, target date, status, evidence, and blocker. Separate what can be inspected read-only from actions that change access, ownership, or data.
Never delete data, revoke access, rotate credentials, transfer ownership, archive communication, or contact another person without explicit confirmation for that action. Show the exact target and consequence before irreversible or externally visible steps. Preserve an audit trail required by the organization.
Finish with unresolved risks, remaining owners, and the next concrete handover action. Do not generate a separate document unless the user asks for one.
Adapted from Thoughtbot's rails-consultant offboard skill at
revision f2cb97d. Distributed under the accompanying MIT license.
Pressure-test an assumption, architecture decision, estimate, or inherited constraint. Use when the user asks to challenge a belief, play devil's advocate, test reasoning, or find a simpler alternative.
Explain a code location, component, command, or user-facing system flow. Use when the user asks what code does, why it exists, how a feature works, or wants a trace of entry points, branches, dependencies, and side effects.
Prepare difficult technical or delivery news for a client, stakeholder, or team. Use for delays, incidents, security findings, cost changes, failed approaches, or other conversations where clarity and trust matter.
Discover how a codebase already handles a concern before extending it. Use when asked how the repository does something, where a pattern lives, whether implementations are consistent, or what convention new work should follow.
Help the user think through a confusing problem or decision by asking focused questions and reflecting their reasoning. Use when they want to think out loud, untangle a problem, or find the question beneath the question.
Project-aware router for Ruby and Rails development. Use for gems, Rails, RSpec, Minitest, Cucumber, SimpleCov, RuboCop, RubyCritic, PostgreSQL, Active Record, debugging, reviews, performance, security, i18n, Sorbet, RBS, Ruby LSP, or Ruby runtime and tooling work.
