finish-work

To archive completed Trellis tasks and record a session journal, run finish-work after committing your code changes. It classifies dirty paths, auto-commits task archives via task.py, and logs work commit hashes using add_session.py.

Task archiving fails with uncommitted working-tree changes because this Skill acts as a safety guardrail, refusing to run if dirty paths belong to the current task. You must commit your work in the prior workflow phase first.

To wrap up a Trellis coding session, invoke finish-work after your work is committed. It runs a context survey in record mode, detects completed tasks, archives them, and writes a session journal making the repository the source of truth.

Run the session journaling workflow when you want to finish or wrap up an active Trellis task. It requires that all current-task code changes are already committed, ensuring only completed work is archived and journaled.

Yes, you can archive multiple tasks during session wrap-up. The Skill detects the active task and optionally archives other completed-but-unarchived tasks when you confirm, using task.py to auto-commit the archive commits.