Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

fix(session-flow): settle in-flight work the handoff depends on before writing it

クローズ
  • 何か問題がありますか？
#6,439 コメント 1 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@kyle-sexton がすでに取り組んでいます。

2026年10月11日 から。

  • #7073 @kyle-sexton による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
38/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
markdown, shell
領域
developer-experience, tooling

調査の方向性

Read plugins/session-flow/skills/handoff/SKILL.md (the Named subagents inventoried this turn checklist) and plugins/session-flow/reference/off-thread-work.md. The skill currently inventories running subagents and still writes the save-point; change that path so work the handoff depends on is waited on, folded in, or explicitly left in flight after the user chooses. Done when a handoff is written only after everything it describes is settled, without free-hand edits to the handoff file.

索引モデルが issue の本文から書いたものです。

説明

needs-triage priority: medium

Problem

/session-flow:handoff writes the save-point while subagents the session spawned are still running. When one of them returns after the save, its result lands in the old session, and the handoff file is already stale: its brief, environment, remaining actions and Next: headlines describe the work as still in flight. The user then has to ask for the handoff to be updated, and the update is a hand repair (Edit plus save_point.py validate) of a file the skill says must never be written free-hand.

Observed 2026-10-05: a session wrote a handoff while a naming-tournament subagent was running. The tournament finished seconds later, the user picked a name in the same session, and the handoff had to be patched in five places (brief, completion criteria, environment, open questions, Next:).

Proposed fix

Before new, the skill settles in-flight work instead of only inventorying it:

  • For every subagent this session spawned that is still running, decide whether the handoff's content depends on its result (its output changes the brief, the next action, a decision or a criterion).
  • Dependent and expected to finish: wait for it (the harness re-invokes the session on completion), fold its result in, then write the save-point.
  • Independent of the handoff's content (for example a background dynamic workflow that writes its own durable output and that the next session only reads): hand off without waiting and record it in Environment to re-establish, as today.
  • Stuck or long-running dependent work: say so and let the user choose between waiting, cancelling, or handing off with it recorded as in flight.

The rule in one line: hand off only once everything the handoff describes is settled.

Out of scope

The continuation router's choice between handoff, compaction and clear; prompt-only handoffs with no in-flight work.

Related

  • plugins/session-flow/skills/handoff/SKILL.md "Named subagents inventoried this turn" checklist item (inventories, does not wait)
  • plugins/session-flow/reference/off-thread-work.md

🤖 Generated with Claude Code

主要言語
Shell
スター
22
フォーク
2
平均マージ
7時間 57分
マージ済み PR（30日）
938

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

melodic-software/claude-code-plugins のほかの issue

melodic-software/claude-code-plugins の issue をすべて見る

似ている issue

Shell/Bash の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。