handoffplan

Name: handoffplan
Author: REMvisual

36stars3forks

How to install handoffplan?

remvisual/claude-handoff/handoffplan

$npx -y skills add REMvisual/claude-handoff --skill handoffplan

Installs into the current project.

Summary

Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.

Files · 1

View on GitHub

SKILL.md

1	# Handoff Plan
2
3	IMPORTANT: This skill writes files. You MUST NOT be in Claude Code's built-in plan mode.
4	If you are currently in plan mode, exit plan mode first (use ExitPlanMode) before proceeding. This skill produces plan files — it does not use Claude Code's plan mode feature. They are different things.
5
6	Step 1: Run `/handoff` to create the data file — FULL TWO-PHASE PROCESS.
7
8	Execute the full `/handoff` skill first, including the mandatory two-phase write process:
9	- Phase 1: Write the handoff file (all sections, narrative + evidence)
10	- Phase 2 (MANDATORY for Deep and Chunked passes): Read it back, scan conversation for uncaptured data, use Edit to expand toward the ceiling (800 lines for 1M context)
11
12	This is not optional. The handoff is the data store — a thin handoff produces a thin plan. Follow the handoff skill's mining-pass detection, line count checks, and gap research pass exactly as specified.
13
14	Do NOT skip or abbreviate the handoff. Do NOT skip Phase 2. If the handoff is under 500 lines on a Chunked pass, you haven't mined deep enough — go back and expand before writing the plan.
15
16	Do NOT ask to close the session after the handoff. Skip Step 8 of the handoff skill — the close prompt happens after the plan is written, not after the handoff.
17
18	Do NOT enter Claude Code plan mode at any point. This skill writes files and commits. Plan mode is not used.
19
20	This skill creates a plan for the NEXT session to execute. The handoff captures data. The plan defines work. Beads track phases. Then you commit, close, and give the user a paste prompt that tells the next session to start executing Phase 1 immediately — no onboarding, no exploration, just code. The next session gets full clean context because it's a fresh session.
21
22	Arguments: $ARGUMENTS
23
24	---
25
26	CHECKPOINT before Step 2: Count the handoff's lines. Check its mining-pass minimum (Quick: 150/250, Deep: 300, Chunked: 500 — see handoff skill's Line Budget table). If the handoff is under its pass minimum, STOP. Run the handoff's Phase 2 gap research pass now — read back what you wrote, scan the conversation for uncaptured data, and Edit to expand. Do not proceed to the plan with a thin handoff. The plan's quality is bounded by the handoff's quality.
27
28	---
29
30	Step 2: Write the plan file.
31
32	Once the handoff file exists, write the plan. The plan lives in the same directory as the handoff, with the same slug:
33
34	- Handoff: `HANDOFF_{chain_tag}_{slug}_{date}.md` (already written — or `HANDOFF_{slug}_{date}.md` if no beads)
35	- Plan: `PLAN_{chain_tag}_{slug}_{date}.md` (write this now — mirror the handoff's naming)
36
37	### What makes a good plan
38
39	If arguments were provided (check `$ARGUMENTS` above): use them as a soft hint for framing the Problem Statement and phasing. They may suggest the epic scope, priority order, or what the user considers the first phase. Let them shape emphasis, but the handoff data is still the authority on what was actually tried and discovered.
40
41	The plan is an action document. It answers "what do we do next and how?" It should be:
42
43	- Grounded in the handoff data. Every phase should trace back to evidence. Don't propose approaches that contradict what "What We Tried" showed didn't work.
44	- Specific enough to execute without the conversation. Someone reading just the plan + handoff should be able to start coding. No vague "investigate X" — say what to investigate, where, and what outcome you expect.
45	- Honest about what we don't know. If a phase has uncertainty, say so and include how to handle both outcomes.
46	- Referencing, not duplicating. Data lives in the handoff. The plan points to it: "See Evidence section in {handoff_file}". Don't copy tables or measurement lists into the plan.
47
48	### Line budget: 120-250 lines
49
50	Scale with the number of phases and complexity. A 2-phase plan is shorter than a 5-phase plan.
51
52	### Plan Structure
53
54	```markdown
55	# {One-line summary of what we're planning}
56
57	Date: {YYYY-MM-DD}
58	Status: PLANNED
59	Bead(s): {active bead IDs, or "none"}
60	Epic: {parent epic/initiative name, if any}
61	Chain: `{chain_tag}` seq `{N}` (copied from paired handoff)
62	Context: See `{handoff_file_name}` for session data, test results, and prior approaches.
63
64	---
65
66	## Problem Statement
67
68	{3-5 sentences. What are we solving? Why does it matter? What's broken or missing?
69	Be specific — include key numbers from the handoff.
70	Reference the handoff for full data: "See Evidence & Data in {handoff_file}".}
71
72	## Key Findings
73
74	{5-8 bullet summary of the discoveries from this session (and prior sessions) that drive t

People who liked this also viewed

6 picks

Type

lark-drive飞书云空间（云盘/云存储）：管理 Drive 文件和文件夹，包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、评论/权限/订阅、标题、版本、飞书文档密级标签（secure labels）和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题，或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sSkillsJul 2026382k16k
lark-sharedUse for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handlingSkillsJul 2026382k16k
lark-whiteboard飞书画板：查询和编辑飞书云文档中的画板。支持导出画板为预览图片、导出原始节点结构、使用多种格式更新画板内容。当用户需要查看画板内容、导出画板图片、编辑画板时使用此 skill。不负责：飞书云文档内容编辑（lark-doc）、文档内嵌电子表格/Base（lark-sheets / lark-base）。SkillsJul 2026380k16k
lark-task飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。SkillsJul 2026380k16k
lark-attendance飞书考勤打卡：查询自己的考勤打卡记录SkillsJul 2026330k16k
lark-apps妙搭（Spark/Miaoda）应用开发与托管：应用创建、本地全栈开发、云端生成迭代、创意设计（UI mockup / 可交互原型 / 线框图 / 落地页 / 仪表盘 / 幻灯片 deck / 视觉探索）、AI相关能力和飞书平台能力或者其他外部能力集成、日志/Trace/监控指标/PV/UV 查询、环境变量管理、应用角色与成员管理、自动化触发器（定时/记录变更/Webhook/飞书审批）。当用户要SkillsJul 2026227k16k

handoffplan

36stars3forks

View on GitHub

How to install handoffplan?

remvisual/claude-handoff/handoffplan

$npx -y skills add REMvisual/claude-handoff --skill handoffplan

Installs into the current project.

Summary

Run /handoff to capture session data, then write a phased implementation plan that references it. Creates beads for tracking.

Files · 1

View on GitHub

SKILL.md

1	# Handoff Plan
2
3	IMPORTANT: This skill writes files. You MUST NOT be in Claude Code's built-in plan mode.
4	If you are currently in plan mode, exit plan mode first (use ExitPlanMode) before proceeding. This skill produces plan files — it does not use Claude Code's plan mode feature. They are different things.
5
6	Step 1: Run `/handoff` to create the data file — FULL TWO-PHASE PROCESS.
7
8	Execute the full `/handoff` skill first, including the mandatory two-phase write process:
9	- Phase 1: Write the handoff file (all sections, narrative + evidence)
10	- Phase 2 (MANDATORY for Deep and Chunked passes): Read it back, scan conversation for uncaptured data, use Edit to expand toward the ceiling (800 lines for 1M context)
11
12	This is not optional. The handoff is the data store — a thin handoff produces a thin plan. Follow the handoff skill's mining-pass detection, line count checks, and gap research pass exactly as specified.
13
14	Do NOT skip or abbreviate the handoff. Do NOT skip Phase 2. If the handoff is under 500 lines on a Chunked pass, you haven't mined deep enough — go back and expand before writing the plan.
15
16	Do NOT ask to close the session after the handoff. Skip Step 8 of the handoff skill — the close prompt happens after the plan is written, not after the handoff.
17
18	Do NOT enter Claude Code plan mode at any point. This skill writes files and commits. Plan mode is not used.
19
20	This skill creates a plan for the NEXT session to execute. The handoff captures data. The plan defines work. Beads track phases. Then you commit, close, and give the user a paste prompt that tells the next session to start executing Phase 1 immediately — no onboarding, no exploration, just code. The next session gets full clean context because it's a fresh session.
21
22	Arguments: $ARGUMENTS
23
24	---
25
26	CHECKPOINT before Step 2: Count the handoff's lines. Check its mining-pass minimum (Quick: 150/250, Deep: 300, Chunked: 500 — see handoff skill's Line Budget table). If the handoff is under its pass minimum, STOP. Run the handoff's Phase 2 gap research pass now — read back what you wrote, scan the conversation for uncaptured data, and Edit to expand. Do not proceed to the plan with a thin handoff. The plan's quality is bounded by the handoff's quality.
27
28	---
29
30	Step 2: Write the plan file.
31
32	Once the handoff file exists, write the plan. The plan lives in the same directory as the handoff, with the same slug:
33
34	- Handoff: `HANDOFF_{chain_tag}_{slug}_{date}.md` (already written — or `HANDOFF_{slug}_{date}.md` if no beads)
35	- Plan: `PLAN_{chain_tag}_{slug}_{date}.md` (write this now — mirror the handoff's naming)
36
37	### What makes a good plan
38
39	If arguments were provided (check `$ARGUMENTS` above): use them as a soft hint for framing the Problem Statement and phasing. They may suggest the epic scope, priority order, or what the user considers the first phase. Let them shape emphasis, but the handoff data is still the authority on what was actually tried and discovered.
40
41	The plan is an action document. It answers "what do we do next and how?" It should be:
42
43	- Grounded in the handoff data. Every phase should trace back to evidence. Don't propose approaches that contradict what "What We Tried" showed didn't work.
44	- Specific enough to execute without the conversation. Someone reading just the plan + handoff should be able to start coding. No vague "investigate X" — say what to investigate, where, and what outcome you expect.
45	- Honest about what we don't know. If a phase has uncertainty, say so and include how to handle both outcomes.
46	- Referencing, not duplicating. Data lives in the handoff. The plan points to it: "See Evidence section in {handoff_file}". Don't copy tables or measurement lists into the plan.
47
48	### Line budget: 120-250 lines
49
50	Scale with the number of phases and complexity. A 2-phase plan is shorter than a 5-phase plan.
51
52	### Plan Structure
53
54	```markdown
55	# {One-line summary of what we're planning}
56
57	Date: {YYYY-MM-DD}
58	Status: PLANNED
59	Bead(s): {active bead IDs, or "none"}
60	Epic: {parent epic/initiative name, if any}
61	Chain: `{chain_tag}` seq `{N}` (copied from paired handoff)
62	Context: See `{handoff_file_name}` for session data, test results, and prior approaches.
63
64	---
65
66	## Problem Statement
67
68	{3-5 sentences. What are we solving? Why does it matter? What's broken or missing?
69	Be specific — include key numbers from the handoff.
70	Reference the handoff for full data: "See Evidence & Data in {handoff_file}".}
71
72	## Key Findings
73
74	{5-8 bullet summary of the discoveries from this session (and prior sessions) that drive t

People who liked this also viewed

6 picks

Type