encerrar-sessao

Triggers R12 PROTOCOLO-WAGNER-SEMPRE closing workflow on session-end cues.

Updated May 14, 2024
One-click install
npx skills add https://github.com/wagnerra23/oimpresso.com --skill encerrar-sessao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: encerrar-sessao
Source: https://github.com/wagnerra23/oimpresso.com/tree/main/.claude/skills/encerrar-sessao
Command: npx skills add https://github.com/wagnerra23/oimpresso.com --skill encerrar-sessao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures the “R12 PROTOCOLO-WAGNER-SEMPRE” closing workflow reliably runs even in long sessions, preventing the protocol steps from being lost after many turns.

Core Features & Use Cases

  • Lazy activation on exact closing cues: triggers immediately when the user signals the end (or “let’s stop / save / continue later / next session” style phrases) or when the agent detects strong “productive completion” signals (e.g., multiple merged PRs, proposed ADR, ≥4h work).
  • MCP-first snapshot and append-only handoff: captures current MCP cycles and tasks, appends a compact handoff file, updates the handoff index, and prepares a clean resume point.
  • Protocol-compliant closure reporting: produces an ≤8-line report that explicitly cites the R12 execution via this specific skill for auditability, with a defense-in-depth companion hook.

Quick Start

When you want to end the current work, tell the agent: “encerrar sessão” (or any close-session cue like “tchau” or “continua depois”), and it will execute the R12 closing handoff workflow.

Frequently Asked Questions about encerrar-sessao

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate session closing with an audit trail and handoff file?

Automating session closing with an audit trail requires triggering a lazy workflow that captures MCP task snapshots, appends a handoff file, updates the memory index, and commits changes via Git for protocol compliance.

What is the best way to create an append-only memory handoff before ending a long development session?

The best way to create an append-only memory handoff is to execute a protocol-driven closing workflow that snapshots current MCP cycles, appends compact handoff notes, and updates the handoff index for the next session.

Does this session closing protocol work with Git commit and MCP task snapshots?

Yes, this session closing protocol works directly with Git commit and MCP task snapshots by enforcing an MCP-first checklist capture, updating the append-only memory index, and pushing the commit to maintain protocol compliance.

How do I ensure protocol compliance when stopping or saving work after multiple merged PRs?

To ensure protocol compliance after multiple merged PRs, you trigger an automated closing workflow that detects productive completion, generates an auditable closure report, and creates an append-only handoff citing the R12 protocol.

Can I use a natural language command to trigger an automated Git commit and handoff workflow?

Yes, you can use natural language commands like "encerrar sessao" or "continua depois" to trigger lazy activation of the protocol workflow, which executes the MCP snapshot, append-only handoff creation, and Git commit automatically.

When should I avoid relying on lazy activation for session closing and audit reporting?

You should avoid relying solely on lazy activation if your development session lacks clear stopping cues or productive completion signals like merged PRs, as the workflow requires explicit triggers to execute the audit trail and handoff creation.