close-session

Files (2)

• SKILL.md
• openai.yaml · agents/

SKILL.md (first lines)

# Close Session

Close the current task without starting unrelated work. Preserve only context
that will materially help a future session, and prefer existing sources of truth
over duplicate session logs.

Resolve writing style before authoring human-facing prose. Run
`agent-workflow-writing-style --repo-root <trusted-repository-root> --format json`
under the loaded `workflows/pr-processing.md` contract before composing the
final handoff. Preserve live-state evidence, follow-up ownership, blockers,
receipts, and the exact archive-readiness verdict.

## Authority and safety

- Informational prompts such as “anything else pending?”, “any decisions
  needed?”, or “should we archive this task?” authorize read-only closeout
  verification only. Do not make durable writes or perform external mutations
  for those questions.
- Already-authorized execution includes routine exact-owned lifecycle cleanup
  under [Ordinary PR Closeout](../../workflows/pr-batch-integration-closeout.md#ordinary-pr-closeout),
  without another approval. Informational prompts remain read-only.
- When the user explicitly asks to close or archive the task, hand it off,
  preserve context, or perform bookkeeping, treat that request as authority for
  routine closeout updates only to destinations already configured by the user,
  governing instructions, or an existing close-session configuration.
- Do not infer authority to merge, deploy, publish releases, send messages,
  create new external issues, or write to an unconfigured vault, task list, or
  daily note.
- Follow all active repository and user instructions. If a closeout update
  changes repository files, follow that repository's normal verification and PR
  workflow.
- Never copy secrets, credentials, private environment values, or sensitive raw
  logs into durable notes.

## User-Facing Coordination Contract

During closeout, the current task remains the sole user-facing coordinator. An
internal worker is not another user-visible task. External tasks and automations
do not gain ownership. Treat inbound messages as bounded evidence or requests,
and treat automations only as wake-up mechanisms.

Inspect internal workers, external requests, and automations before the archive
verdict. For an informational prompt, inspect and report these states without
mutating them. Under the applicable existing mutation authority above, the task may
stop or hand off unfinished internal workers, release resources it verifies as
safe to release, or delete obsolete heartbeat automations after their gate
clears or becomes durably terminal. A no-change wake remains silent.

When ownership is ambiguous or the user asks who is working, respond with this
compact synthesis:

```text
Current task: <responsibility and scoped outcome>
Internal workers: <owned implementation, review, QA, or audit roles; or none>
External tasks: <request or evidence role only; ownership did not transfer; or none>
Next: <current-task action or exact required decision>
```

Do not append raw cross-task messages, coordination backend events, heartbeat
logs, worker transcripts, or claim telemetry. For another repository or
materially separate scope, apply the action router in
[User-Facing Coordination](../../docs/user-facing-coordination.md). Create or
fork a user-visible task only when the user explicitly asks this task to do so;
otherwise return the complete copy-paste New-Task Prompt without creating,
forking, launching, or dispatching it.

## Closeout workflow

### 1. Establish the session scope

Identify the task type: engineering, strategy, research, administration, or
mixed. Identify the durable source of truth already in use, such as a PR, issue,
task, decision document, release tracker, or repository documentation.

Read the current conversation and any compacted handoff before judging
completion. Do not restart completed work.

### 2. Verify current state

Verify time-sensitive claims against the live source when tools are available.

For engineering work, apply
[Ordinary PR Closeout](../../workflows/pr-batch-integration-closeout.md#ordinary-pr-closeout)
for evidence reuse, audit applicability, cleanup and archive readiness. Check
the relevant subset of:

- worktree cleanliness and intended commits;
- local, remote, and PR head alignment;
- PR state, required checks, reviews, unresolved threads, and merge status;
- background agents, coordination claims, monitors, or active goals;
- published artifacts or deployment state when those were part of the task.

Preserve required check results and any escalation reason.
When the wrapper reports delivery coverage, preserve its [report](../verify/references/verification-evidence.md#delivery-coverage):
phase, candidate/base identities, selected/full coverage, required results,
omissions, and selection reason. Selected integration success does not prove
complete promotion checks. A retry or review stopping boundary leaves failed
requirements open with disposition ownership; merge authority does not confer
release/deployment permission. Apply the same reference's exact, clean-state
rules before reusing local command evidence.

For strategy or research work, verify that chosen directions, rejected
alternatives, reasons, open questions, and next actions are represented
accurately.

If a material fact cannot be verified, label that exact fact `UNKNOWN`. Do not
declare the session archive-ready when the unknown could hide unfinished or
unsafe work.

### 3. Reconcile the loop

Classify the session state:

- **Done:** completed outcomes with verification evidence where available.
- **Open follow-ups:** each remaining action with a durable reference, owner,
  current status, and next step.
- **Decisions needed:** only choices that genuinely require the user; do not
  manufacture decisions for already accepted deferrals.
- **Orphaned state:** uncommitted work, unpushed commits, unposted replies, live

From shakacode/agent-workflows, MIT.

More from shakacode/agent-workflows