name: triad-handoff description: > Use this at the end of any task to produce a reusable handoff artifact that allows a fresh session to resume without relying on chat memory. inputs:

• Task Intake (with Workflow Progress)
• Summary of changes / decisions / results outputs:
• docs/triad/TRIAD_HANDOFF-<YYYYMMDD>-<slug>.md rules:
• Must be skimmable in under 2 minutes.
• Must separate Facts vs Decisions vs Open Questions.
• If any decision violates a core invariant, mark it explicitly as "Requires Human approval".
• "Checklist Gate: Status: DONE is allowed ONLY if Final Checklist is fully satisfied."
• "If any checklist item is unchecked, use Status: PARTIAL or Status: BLOCKED."

triad-handoff

⚠️ STOP: 完了前に ./scripts/verify-workflow を実行してください！ Workflow Progress が OK でないと DONE にできません。

Triad Handoff: <title>

• Date:
• Related Task Intake:
• Status: DONE / PARTIAL / BLOCKED

Facts (what happened)

• ...

Decisions (what we agreed)

• ...

Open Questions (what is unclear)

• ...

Next Actions (ordered)

1. ...
2. ...

Evidence / Pointers

• Changed areas (paths):
• Key files:
• Tests/bench run:
• Screenshots/logs (if any):

Final Checklist (Gate)

MUST: 全項目にチェックがないと Status: DONE 禁止。

Workflow Progress Verification

• Related Task Intake is linked above
• Task Intake contains Workflow Progress section with:
  • WF_WORKFLOW is declared
  • codex-review-request is OK or SKIP (with Skipped Policy)
  • human-approval-gate is OK or SKIP (with Skipped Policy)
  • verify is OK (NON-SKIPPABLE: cargo test/build must pass)
  • triad-handoff is OK (this document)

Skipped Policy Check (if any SKIP in Workflow Progress)

• Step name:
• Reason documented:
• Risk accepted:
• Approved by Human (if required):

Completion Criteria

• All Open Questions resolved (or explicitly deferred with reason)
• Next Actions are clear (or "None" if truly complete)
• Evidence/Pointers is complete

If all boxes are checked: Status: DONE
If any box is unchecked: Status: PARTIAL or Status: BLOCKED