offboard

Name: offboard
Author: thoughtbot

15stars1forks

How to install offboard?

thoughtbot/rails-consultant/offboard

$npx -y skills add thoughtbot/rails-consultant --skill offboard

Installs into the current project.

Summary

Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.

Files · 1

View on GitHub

SKILL.md

1	## Behavior
2
3	Walk through each wrap-up item below as a conversation. Go one item at a time. For each item:
4
5	1. Explain what needs to happen and why.
6	2. If you can assist directly (scan code, check branches, grep for secrets), do it right then.
7	3. Ask whether the item applies, whether it's done, or whether they need help.
8	4. Move on when they confirm.
9
10	Skip items that clearly don't apply based on what you've already learned (e.g., skip Figma items if there's no design work). If you're unsure, ask.
11
12	---
13
14	## Checklist
15
16	### 1. Transfer codebase ownership to the client
17
18	Check who owns the repo. Ask whether the client has admin access and whether any transfer is needed.
19
20	### 2. Upload files to client-accessible storage
21
22	Ask whether all project files (documents, assets, exports) have been uploaded to Basecamp, Drive, or whatever file storage the client uses.
23
24	### 3. Figma file transfer
25
26	Ask whether this engagement involved design work. If yes:
27
28	- Have Figma files been transferred to the client's organization, or exported as `.fig` files and sent?
29	- Does your team have a copy of the files?
30	- Have client members been removed as editors from your Figma team? (Viewers are fine — they don't count toward billing.)
31
32	If no design work, skip this entirely.
33
34	### 4. Archive Slack or other chat rooms
35
36	Ask which shared channels or chat rooms exist and whether they should be archived.
37
38	### 5. Clean up project management tools
39
40	Ask about Trello, Switchboard, or other project management tools. Should boards be archived or closed?
41
42	### 6. Transfer password manager entries
43
44	Ask whether any credentials are stored in your team's password manager that need to be transferred to the client's vault.
45
46	### 7. Delete sensitive user data from machines
47
48	Scan the local project directory for potential sensitive data:
49
50	- Grep for common patterns: API keys, tokens, passwords, `.env` files, credential files, database dumps, SSH keys.
51	- Check for `.env`, `.env.local`, `.env.production`, or similar files.
52	- Check for any database dumps or seed files with real user data.
53
54	Report what you find. Ask whether there's anything else on their machine that needs to be cleaned up.
55
56	### 8. Remove remote RSA keys on machines
57
58	Ask whether they added any SSH keys to client servers or services that should be removed.
59
60	### 9. Return client equipment
61
62	Ask whether they have any client equipment (laptops, hardware) to return.
63
64	### 10. Archive the retrospective
65
66	Ask whether the project retrospective has been documented and stored somewhere the team can reference it.
67
68	### 11. Archive design artifacts
69
70	Ask whether screenshots and other design artifacts have been saved somewhere accessible to the team. Skip if no design work.
71
72	### 12. Remind client to rotate credentials
73
74	This is important — any credentials or API keys the client shared should be rotated after offboarding.
75
76	Ask whether they've reminded the client to change credentials and API keys that were shared during the engagement.
77
78	### 13. Tidy up Google Docs
79
80	Ask whether project-related Google Docs have been organized into a folder and made accessible at the organization level.
81
82	### 14. Book knowledge transfer session
83
84	Ask whether a knowledge transfer session has been scheduled to walk the client through all resources, the codebase, and anything they'll need to maintain going forward.
85
86	If the codebase is in the current working directory, offer to help prepare — check the README, look at open branches, scan for TODOs, and identify areas that might need a walkthrough.
87
88	---
89
90	## Tone
91
92	Calm, professional, thorough. You're a colleague helping them make sure nothing falls through the cracks. Don't rush — each item matters. But don't over-explain items they've already handled.

People who liked this also viewed

6 picks

Type

offboard

15stars1forks

View on GitHub

How to install offboard?

thoughtbot/rails-consultant/offboard

$npx -y skills add thoughtbot/rails-consultant --skill offboard

Installs into the current project.

Summary

Walk through the Designer/Developer wrap-up checklist for offboarding a client engagement — conversationally, one item at a time.

Files · 1

View on GitHub

SKILL.md

1	## Behavior
2
3	Walk through each wrap-up item below as a conversation. Go one item at a time. For each item:
4
5	1. Explain what needs to happen and why.
6	2. If you can assist directly (scan code, check branches, grep for secrets), do it right then.
7	3. Ask whether the item applies, whether it's done, or whether they need help.
8	4. Move on when they confirm.
9
10	Skip items that clearly don't apply based on what you've already learned (e.g., skip Figma items if there's no design work). If you're unsure, ask.
11
12	---
13
14	## Checklist
15
16	### 1. Transfer codebase ownership to the client
17
18	Check who owns the repo. Ask whether the client has admin access and whether any transfer is needed.
19
20	### 2. Upload files to client-accessible storage
21
22	Ask whether all project files (documents, assets, exports) have been uploaded to Basecamp, Drive, or whatever file storage the client uses.
23
24	### 3. Figma file transfer
25
26	Ask whether this engagement involved design work. If yes:
27
28	- Have Figma files been transferred to the client's organization, or exported as `.fig` files and sent?
29	- Does your team have a copy of the files?
30	- Have client members been removed as editors from your Figma team? (Viewers are fine — they don't count toward billing.)
31
32	If no design work, skip this entirely.
33
34	### 4. Archive Slack or other chat rooms
35
36	Ask which shared channels or chat rooms exist and whether they should be archived.
37
38	### 5. Clean up project management tools
39
40	Ask about Trello, Switchboard, or other project management tools. Should boards be archived or closed?
41
42	### 6. Transfer password manager entries
43
44	Ask whether any credentials are stored in your team's password manager that need to be transferred to the client's vault.
45
46	### 7. Delete sensitive user data from machines
47
48	Scan the local project directory for potential sensitive data:
49
50	- Grep for common patterns: API keys, tokens, passwords, `.env` files, credential files, database dumps, SSH keys.
51	- Check for `.env`, `.env.local`, `.env.production`, or similar files.
52	- Check for any database dumps or seed files with real user data.
53
54	Report what you find. Ask whether there's anything else on their machine that needs to be cleaned up.
55
56	### 8. Remove remote RSA keys on machines
57
58	Ask whether they added any SSH keys to client servers or services that should be removed.
59
60	### 9. Return client equipment
61
62	Ask whether they have any client equipment (laptops, hardware) to return.
63
64	### 10. Archive the retrospective
65
66	Ask whether the project retrospective has been documented and stored somewhere the team can reference it.
67
68	### 11. Archive design artifacts
69
70	Ask whether screenshots and other design artifacts have been saved somewhere accessible to the team. Skip if no design work.
71
72	### 12. Remind client to rotate credentials
73
74	This is important — any credentials or API keys the client shared should be rotated after offboarding.
75
76	Ask whether they've reminded the client to change credentials and API keys that were shared during the engagement.
77
78	### 13. Tidy up Google Docs
79
80	Ask whether project-related Google Docs have been organized into a folder and made accessible at the organization level.
81
82	### 14. Book knowledge transfer session
83
84	Ask whether a knowledge transfer session has been scheduled to walk the client through all resources, the codebase, and anything they'll need to maintain going forward.
85
86	If the codebase is in the current working directory, offer to help prepare — check the README, look at open branches, scan for TODOs, and identify areas that might need a walkthrough.
87
88	---
89
90	## Tone
91
92	Calm, professional, thorough. You're a colleague helping them make sure nothing falls through the cracks. Don't rush — each item matters. But don't over-explain items they've already handled.

People who liked this also viewed

6 picks

Type