Problem
The work-closeout skill appears to be invoked for closeout requests without reliably including the required Love Gate section in the final closeout response.
The skill contract currently says:
## The Love Gate
Before finalizing the closeout, perform a "Love Gate" check.
...
- **Report findings**: Include a brief "Love Gate" section in your closeout summary.
The output format also lists:
- Love Gate: what you love about the results, and anything you do not love.
Recent transcript evidence
Local session history shows a user correction after an attempted closeout flow:
2026-06-10 15:01:28Z user: use the closeout skill
2026-06-10 15:10:37Z user: what about the love gate and the rest of the skill
There are also nearby direct closeout requests in recent local history, e.g.:
2026-06-10 14:35:40Z user: ok great, use the closeout skill
2026-06-10 15:50:31Z user: can you use the work closeout skill
2026-06-16 17:20:44Z user: ok use the work closeout skill
Those suggest this is not just a one-off prompt phrasing issue; closeout requests are common and the required Love Gate is easy for the agent to skip unless the user explicitly asks for it.
Expected behavior
When work-closeout is used and the response is a closeout/safe-to-exit summary, the final response should include a visible Love Gate item/section, even if it is brief.
Examples:
Love Gate: I like that the docs and PR state are clean. I do not love that the validation was docs-only, but that is appropriate for this change.
or, in a compact final:
Love Gate: Clean and complete; no lingering smells beyond the intentionally deferred follow-up.
Suggested fix
- Add behavior validation that fails if a closeout/safe-to-exit response omits
Love Gate when work-closeout is triggered.
- Consider moving the Love Gate requirement closer to the top of the skill or into a non-optional closeout checklist, since the current section exists but is still being skipped in practice.
- If the final response is very short, still require a one-line Love Gate entry rather than dropping it.
Acceptance criteria
- A closeout prompt such as
use the work closeout skill produces a final answer with a Love Gate section/item.
- A safe-to-exit prompt that routes through
work-closeout also includes Love Gate before the Safe to exit answer or near it.
- Behavior tests or harness fixtures cover this so regressions are caught.
Problem
The
work-closeoutskill appears to be invoked for closeout requests without reliably including the requiredLove Gatesection in the final closeout response.The skill contract currently says:
The output format also lists:
- Love Gate: what you love about the results, and anything you do not love.Recent transcript evidence
Local session history shows a user correction after an attempted closeout flow:
There are also nearby direct closeout requests in recent local history, e.g.:
Those suggest this is not just a one-off prompt phrasing issue; closeout requests are common and the required Love Gate is easy for the agent to skip unless the user explicitly asks for it.
Expected behavior
When
work-closeoutis used and the response is a closeout/safe-to-exit summary, the final response should include a visibleLove Gateitem/section, even if it is brief.Examples:
or, in a compact final:
Suggested fix
Love Gatewhenwork-closeoutis triggered.Acceptance criteria
use the work closeout skillproduces a final answer with aLove Gatesection/item.work-closeoutalso includesLove Gatebefore theSafe to exitanswer or near it.