メニュー
Use at the end of a work session on a DAE feature, so the next session picks up cleanly. Triggers — "/engineer.session-summary", "wrap up the session", "write the session log", "I'm stopping for the day".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | session-summary |
| description | Use at the end of a work session on a DAE feature, so the next session picks up cleanly. Triggers — "/engineer.session-summary", "wrap up the session", "write the session log", "I'm stopping for the day". |
Write the per-session entry in a feature's session-log.md so the human can close the laptop and pick back up cleanly. The human-readable counterpart to the machine handoffs. checkpoint: null.
At the end of a work session on a feature. A Stop hook may auto-invoke it; that hook is optional plugin config, not part of this skill.
Not for: mid-session (nothing's wrapping up); syncing the tracker (progress-log); per-skill records (each skill's own handoff).
${CLAUDE_PLUGIN_ROOT}/scripts/dae_resolve.py (see references/resolving.md). Scope = the feature(s) the session touched (default: current branch; multiple → an entry in each; none → nothing to log, stop).handoffs/*.md, git activity on the branch, and conversation context (decisions, problems, deferrals).features/NNN-<slug>/session-log.md:## Session — <ISO date> <start>–<end>
**Current state:** <which checkpoint, one line>
### Previous tasks (done this session)
- ...
### Current task
- <in progress at session end, if any>
### Next tasks
- <concrete, actionable, ordered>
### Open questions / blockers
- <or "None">
Create the file with a # Session log — <title> heading if absent.
Tear down session-end infra. Run ${CLAUDE_PLUGIN_ROOT}/scripts/dae_infra.py teardown (no args = all entries with effective teardown: session-end or always). Default behavior leaves entries with teardown: leave-running (the per-entry default and the project-wide default we ship with) untouched — emulators are expensive to start, and the user typically wants them up across sessions while working on a feature. The teardown's JSON output goes into the session log as a one-line summary.
Branch cleanup if merged. If the current branch is not main/master, run git fetch origin --quiet then git merge-base --is-ancestor HEAD origin/HEAD (fallback origin/main). If the branch is merged, defer to /engineer.post-merge (the dedicated cleanup skill) — at autonomy high/medium auto-invoke it; at low surface the finding. If the branch is not merged, do nothing — the work isn't complete yet. Record the post-merge outcome in the session log.
Handoff — emit a summary.
Emit per ${CLAUDE_PLUGIN_ROOT}/references/handoff-summary.md. checkpoint: null; human_action_needed: no; recommended_next: the first "Next task" from the entry. (session-summary is not the handoff processor, so it follows the normal contract — no exemption.)
Three records, three readers: handoffs/ = machine, per-invocation; progress.md = machine-derived, glanceable; session-log.md = human, per-session, narrative. They don't duplicate — different granularity, different reader.
session-log.md in the storage layout, the session-log ↔ handoffs distinction (Section 5)engineer/scripts/dae_infra.py — invoked here at session endUse when exploring a feature idea before committing, or revisiting a parked one. Triggers — "/engineer.discuss", "/engineer.discuss <slug>", "I have an idea about", "should we build", "let's think about".
Use when a new feature folder must be created for the DAE pipeline, or when discuss promotes/parks an idea. Triggers — "/engineer.feature-init", "create a feature", "start a new feature", "init a feature".
Use at the start of a work session, or any time the question is "what should I pick up now" across the whole project. Triggers — "/engineer.next", "what's next", "what should I work on", "what should I do next", "where do I pick up".
Use to bring a project into the DAE methodology, or to check an onboarded project for gaps. Triggers — "/engineer.onboard", "onboard this project", "set up DAE here", "adopt the methodology", or when a DAE skill fails because no manifest exists.
Use to propagate DAE state — turning handoff summaries into visible progress. Triggers — "/engineer.progress-log", "sync progress", "update the tracker", "reconcile the tracker", "refresh feature status".
Use to drive a bug fix from first report through close, with a "why didn't we catch it?" loop at the end. Triggers — "/engineer.fix", "a bug came in", "this is broken", "a user reported X", "there's a defect", "we have a regression", "this needs a fix", "another report", "more issues", "still failing", "validation failed again", "another bug", "next defect", "more fixes".