Close Loop
Use this skill when the user says "close loop", "close-loop", "wrap up the session", "close session", "end session", "end of day", or invokes /close-loop. This is the full end-of-session controller (ship + memory + self-improve + publish); for archiving a single Trellis task use finish-work instead.
Run four phases in order and return one consolidated inline report.
Modular structure
This skill is split into components for maintainability:
components/01-design-principles.mdcomponents/02-phase-1-ship-state.mdcomponents/03-phase-2-memory.mdcomponents/04-phase-3-4-and-output.md
Follow these components in order.
Quick run order
- Apply execution policy and action gates (
01-design-principles.md) - Execute Ship State (
02-phase-1-ship-state.md) - Consolidate Memory (
03-phase-2-memory.md) - Run improvements + publish queue + output contract (
04-phase-3-4-and-output.md)
Required output
Return:
- Artifact A: human-readable report sections exactly as defined in component 04
- Artifact B: machine-readable JSON block exactly as defined in component 04
Resources
references/memory-frameworks.mdassets/templates/wrap-report-template.md