session-end

Finalize OpenCode missions by updating mission files and generating work logs.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/dusktreader/site-nine --skill session-end-dusktreader
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: session-end
Source: https://github.com/dusktreader/site-nine/tree/main/.opencode/skills/session-end
Command: npx skills add https://github.com/dusktreader/site-nine --skill session-end-dusktreader

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures a disciplined, auditable closure of open missions by updating the mission file, finalizing tasks, and generating a documented end-of-mission log.

Core Features & Use Cases

  • Mission finalization: Update the mission record with duration, files changed, and outcomes.
  • Task and handoff closure: Close open tasks, mark handoffs complete, and prepare a comprehensive handoff.
  • Formal goodbye: Generate a final, stylized farewell and present a complete mission summary for stakeholders.

Quick Start

Run the s9 mission end <mission-id> command to finish the current mission. Check the .opencode/work/missions directory for the final mission entry and related commits. Confirm that tasks are closed and a final goodbye is prepared.

Frequently Asked Questions about session-end

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I properly close a mission with documentation and handoffs?

Mission closure updates the mission file with duration and outcomes, finalizes all open tasks, generates a documented work log, and prepares handoffs for stakeholders. Run `s9 mission end <mission-id>` to complete the process end-to-end, which records changes and commits to .opencode/work/missions.

What should be included in a mission handoff and work log?

A mission handoff documents files changed, task outcomes, duration, and completion status. The work log formalizes this record for stakeholder visibility. session-end captures all required fields during closure and generates a formal summary that serves as the audit trail for mission completion.

Can I use mission-end workflows with OpenCode-driven projects across different roles?

Yes, session-end applies to OpenCode-driven missions regardless of role. It integrates with the s9 CLI and standardizes closure across teams, ensuring consistent mission finalization, task tracking, and documented handoffs whether you're a contributor, lead, or stakeholder.

Where are mission records and closure artifacts stored?

Mission records, work logs, and closure commits are written to the .opencode/work/missions directory. This centralized location maintains the audit trail of all mission activities, making closure artifacts retrievable and traceable for future reference.

What happens to open tasks when I close a mission?

Open tasks are closed and marked complete as part of mission finalization. session-end guides you through closing each task, recording its duration and outcome, ensuring no work is left incomplete before the mission formally ends.