lifecycle-mark-closure-done

Mark closure done — the final step of an opportunity

When to use

• The leader has aggregated the per-assignment outcomes and written closure/report-and-lessons-learned.md for the opportunity, not an assignment.
• The opportunity's pipeline stage is closure. This skill re-reads that from the server and stops if it moved.
• The user says "mark closure done", "close out the opportunity", or similar.

Binary check

Run command -v glassity before the first CLI call. If it is missing, stop and tell the user to install it with brew install glassity/tap/glassity or from https://github.com/glassity/cli/releases. No account yet? Sign up at app.glassity.cloud.

Pre-flight

1. Re-read the authoritative state:

   glassity --output=json opp show "<opportunity-id>"
   

   If the pipeline stage is not closure, stop:

   This opportunity is not in closure (server says <X>). Move it there with glassity opp pipeline-move, then retry.

2. Locate the closure report:

   ls closure/report-and-lessons-learned.md
   

   The path is fixed. The server validates it and rejects anything else, so there is no point trying a variant. Capture the commit with git log -1 --format=%H -- closure/report-and-lessons-learned.md.

Phase 1 — two mutations, chained

Step A — register the closure report

glassity --output=json opp register-opportunity-artifact "<opportunity-id>" \
  --kind closure_report \
  --stage closure \
  --path "closure/report-and-lessons-learned.md" \
  --commit-sha "<sha>" \
  --status approved

Show the verbatim plan; wait for "yes".

Step B — move the opportunity to completed

glassity --output=json opp pipeline-move "<opportunity-id>" \
  --target-stage completed \
  --comment "Closure report registered; opportunity completed."

Show the verbatim plan; wait for "yes".