create-handoff

Name: create-handoff
Author: tobihagemann

1installs29forks

How to install create-handoff?

tobihagemann/turbo/create-handoff

$npx -y skills add tobihagemann/turbo --skill create-handoff

Installs into the current project.

Summary

Write a handoff file at .turbo/handoff/<YYYY-MM-DD>-<slug>.md capturing current session state — task, status, open decisions, in-flight changes, next step — so a fresh session can continue without re-deriving context. Use when the user asks to \"create a handoff\", \"create hando

Files · 1

View on GitHub

SKILL.md

1	# Create Handoff
2
3	Write a session handoff file at `.turbo/handoff/<YYYY-MM-DD>-<slug>.md` so a fresh session can pick up where this one left off.
4
5	## Step 1: Resolve the Target Path
6
7	Get today's date: `date +%Y-%m-%d`.
8
9	Pick a slug for the current task:
10
11	- Lowercase
12	- Replace non-alphanumeric characters with hyphens
13	- Collapse consecutive hyphens
14	- Trim leading and trailing hyphens
15	- Truncate to 40 characters at a word boundary
16
17	If the work is anchored to an existing artifact (a plan at `.turbo/plans/<slug>.md`, a shell at `.turbo/shells/<slug>.md`, or a spec at `.turbo/specs/<slug>.md`), reuse that artifact's slug verbatim.
18
19	The user may pass an explicit slug or path; honor it.
20
21	The target path is `.turbo/handoff/<YYYY-MM-DD>-<slug>.md`. If the path already exists, append `-2`, `-3`, etc. until the path is free.
22
23	State the chosen path before continuing.
24
25	## Step 2: Gather Session State
26
27	Run `git status --short` to see uncommitted changes in the working tree.
28
29	Survey the conversation context for:
30
31	- Current task: what is being worked on, in one or two sentences
32	- Workflow status: where in the workflow this session is (drafting, refining iteration N, applying findings, implementing step M of K, investigating, blocked on Q, etc.)
33	- Active artifact: path to the plan, shell, spec, or other file at the center of the work, if one exists
34	- Open decisions: questions raised but not resolved, choices the user is still weighing, escalations awaiting input
35	- In-flight changes: staged or unstaged edits that are not yet committed; what each change is doing and what is missing
36	- Next step: the first concrete action the new session should take
37
38	When something is genuinely unclear and would leave a gap in the handoff, use `AskUserQuestion` to resolve it. Default to inferring quietly when the conversation makes the answer clear.
39
40	## Step 3: Write the Handoff File
41
42	Create `.turbo/handoff/` if it does not exist. Write the file at the path picked in Step 1.
43
44	Lead with `# Handoff: <Task Title>`. Cover the items gathered in Step 2 in whatever structure fits the session — drafting, refining, implementing, and investigating sessions each have different shapes and don't all map to the same headings. Close with a clear statement of the next concrete action so the new session knows exactly what to do first.
45
46	Keep it dense. Omit anything that has no real content.
47
48	## Step 4: Confirm
49
50	Tell the user where the handoff was written and quote the next-step statement so the path forward is visible at a glance.
51
52	Then use the TaskList tool and proceed to any remaining task.

People who liked this also viewed

6 picks

Type

create-handoff

1installs29forks

View on GitHub

How to install create-handoff?

tobihagemann/turbo/create-handoff

$npx -y skills add tobihagemann/turbo --skill create-handoff

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Create Handoff
2
3	Write a session handoff file at `.turbo/handoff/<YYYY-MM-DD>-<slug>.md` so a fresh session can pick up where this one left off.
4
5	## Step 1: Resolve the Target Path
6
7	Get today's date: `date +%Y-%m-%d`.
8
9	Pick a slug for the current task:
10
11	- Lowercase
12	- Replace non-alphanumeric characters with hyphens
13	- Collapse consecutive hyphens
14	- Trim leading and trailing hyphens
15	- Truncate to 40 characters at a word boundary
16
17	If the work is anchored to an existing artifact (a plan at `.turbo/plans/<slug>.md`, a shell at `.turbo/shells/<slug>.md`, or a spec at `.turbo/specs/<slug>.md`), reuse that artifact's slug verbatim.
18
19	The user may pass an explicit slug or path; honor it.
20
21	The target path is `.turbo/handoff/<YYYY-MM-DD>-<slug>.md`. If the path already exists, append `-2`, `-3`, etc. until the path is free.
22
23	State the chosen path before continuing.
24
25	## Step 2: Gather Session State
26
27	Run `git status --short` to see uncommitted changes in the working tree.
28
29	Survey the conversation context for:
30
31	- Current task: what is being worked on, in one or two sentences
32	- Workflow status: where in the workflow this session is (drafting, refining iteration N, applying findings, implementing step M of K, investigating, blocked on Q, etc.)
33	- Active artifact: path to the plan, shell, spec, or other file at the center of the work, if one exists
34	- Open decisions: questions raised but not resolved, choices the user is still weighing, escalations awaiting input
35	- In-flight changes: staged or unstaged edits that are not yet committed; what each change is doing and what is missing
36	- Next step: the first concrete action the new session should take
37
38	When something is genuinely unclear and would leave a gap in the handoff, use `AskUserQuestion` to resolve it. Default to inferring quietly when the conversation makes the answer clear.
39
40	## Step 3: Write the Handoff File
41
42	Create `.turbo/handoff/` if it does not exist. Write the file at the path picked in Step 1.
43
44	Lead with `# Handoff: <Task Title>`. Cover the items gathered in Step 2 in whatever structure fits the session — drafting, refining, implementing, and investigating sessions each have different shapes and don't all map to the same headings. Close with a clear statement of the next concrete action so the new session knows exactly what to do first.
45
46	Keep it dense. Omit anything that has no real content.
47
48	## Step 4: Confirm
49
50	Tell the user where the handoff was written and quote the next-step statement so the path forward is visible at a glance.
51
52	Then use the TaskList tool and proceed to any remaining task.

People who liked this also viewed

6 picks

Type