mpi-end-session

Close active MPI sessions, sync rules/docs, and commit touched files.

1|Updated May 13, 2026
One-click install
npx skills add https://github.com/MadPonyInteractive/mpi-kanban --skill mpi-end-session
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mpi-end-session
Source: https://github.com/MadPonyInteractive/mpi-kanban/tree/main/skills/mpi-end-session
Command: npx skills add https://github.com/MadPonyInteractive/mpi-kanban --skill mpi-end-session

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the end-of-session workflow in the MPI Kanban pack by providing a single, repeatable sequence to close the active session, synchronize rules and documentation with code changes, commit touched files, persist new memory, and close the corresponding JSON task card. It also supports legacy Markdown kanban close-out when no JSON board exists as a compatibility fallback.

Core Features & Use Cases

  • End-session orchestration: cleanly wrap the current brainstorming/planning cycle and prepare for handoff or completion.
  • Coordination with the MPI-lib references to keep rules/docs aligned throughout the finalization process.
  • Memory and state persistence: ensure new memory entries are written and coordination state is refreshed before completion.
  • Task-board updates: commit changes to the JSON board and reflect the final status of the current task.
  • Compatibility fallback: support legacy Markdown kanban close-out if no JSON board is present.

Quick Start

Run mpi-end-session after you signal the session is complete to finalize changes and close the active task card.

Frequently Asked Questions about mpi-end-session

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

FAQPage Schema
How do I automate end-of-session git commits and task-board updates for my workflow?

You can automate closing a session by running this skill after signaling completion. It coordinates the finalization loop across all agents, syncing rules and documentation with code changes, persisting new memory, and updating the JSON task-board before closing the active session.

What is the best way to sync documentation and rules with code changes before finalizing a session?

Syncing documentation and rules with code changes before finalizing a session involves coordinating with shared library references. This skill aligns rules and docs throughout the finalization process, writing new memory entries and refreshing coordination state before committing files.

How do I close a JSON task card and move a task to done with explicit user approval?

Closing a JSON task card and moving a task to done requires explicit user approval before finalization. The skill enforces proper gating through state checks, committing changes to the JSON board and reflecting the final task status only after approval is granted.

Can I use a legacy Markdown kanban close-out if no JSON task board exists?

You can use a legacy Markdown kanban close-out when no JSON board exists as a compatibility fallback. The skill supports finalizing the active session using Markdown format, ensuring the task card is closed even without a JSON board present.

Do I need shared library references to coordinate memory and state persistence?

You need shared library references from the MPI-lib skill to coordinate memory and state persistence. The skill relies on these shared references to keep rules and docs aligned, enforce state checks, and ensure coordination state is refreshed before moving a task to done.