メニュー
flightwake cross-session handoff — write CONTEXT for work that is unfinished and will continue later. Use when stopping mid-build on multi-session work, when the user says handoff / continue next time, or before context runs out on a large task.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
flightwake 登記坑 — 把非顯而易見的陷阱寫進 TRAPS registry。Use immediately when a surprising root cause is found (weird error, vendor quirk, encoding trap), or when the user says 記一下這個坑/trap.
flightwake trap registration — write a non-obvious trap into the TRAPS registry. Use immediately when a surprising root cause is found (weird error, vendor quirk, encoding trap), or when the user says log this trap / trap.
flightwake cold start — restore state before touching a repo. Use when starting work in a repo that has .flightwake/, when the user says take over / continue / coldstart, or at the start of any session touching a flightwake-managed repo.
flightwake wrap-up record — write the flight record and update STATE. Use when wrapping up work that touched schema/prod, spanned 3+ commits, or when the session is ending; also when the user says wrap up / record this.
flightwake 冷啟動 — 接手一個 repo 前先恢復狀態。Use when starting work in a repo that has .flightwake/, when the user says 接手/繼續上次/coldstart, or at the start of any session touching a flightwake-managed repo.
flightwake 收尾記錄 — 寫飛行紀錄並更新 STATE。Use when wrapping up work that touched schema/prod, spanned 3+ commits, or when the session is ending; also when the user says 收尾/記錄一下/record.
| name | fw-handoff |
| description | flightwake cross-session handoff — write CONTEXT for work that is unfinished and will continue later. Use when stopping mid-build on multi-session work, when the user says handoff / continue next time, or before context runs out on a large task. |
Purpose: let any session cold-start into unfinished construction. The trigger is before stopping — not before starting — a CONTEXT written after touching reality is the only kind that's real.
.flightwake/records/YYMMDD-slug-CONTEXT.md with four mandatory sections:
This is flightwake's version of opening a phase: one CONTEXT, no upfront plan decomposition — the plan is the executing session's in-the-moment judgment.
If the repo also has a legacy .planning/ directory, the CONTEXT may live in its phases/ directory to keep the existing index (same format as this file).