kb-session-wrap

Executes GT-KB session wrap-up reconciling Git, MemBase, and session_prompts with blockers recorded.

2|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-session-wrap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-session-wrap
Source: https://github.com/Remaker-Digital/groundtruth-kb/tree/main/.claude/skills/kb-session-wrap
Command: npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-session-wrap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

kb-session-wrap solves the problem of ending a GT-KB session without losing durable knowledge, verification evidence, or continuity context for the next agent.

Core Features & Use Cases

  • Evidence-first knowledge capture: Reconciles live Git/bridge/work-item/spec/test state with the knowledge matrix so future agents inherit what actually happened, not chat recollection.
  • Durable memory updates: Updates MemBase, harvests new Deliberation Archive content when applicable, and records blockers when governance/tooling prevents updates.
  • Verification and hygiene reporting: Runs wrap scanners (hygiene/consistency), records outcomes, and explicitly references ignored local evidence paths instead of force-adding generated or untracked artifacts.
  • Next-session handoff prompt: Generates and inserts a self-contained handoff prompt into session_prompts, or preserves the prompt text plus an explicit blocker if insertion is not possible.

Quick Start

Use the kb-session-wrap skill to run the full session wrap-up for a specific session id like S347 and produce the next-session handoff prompt with blockers recorded.

Frequently Asked Questions about kb-session-wrap

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

FAQPage Schema
How do I preserve verification evidence and context when ending a development session?

Session wrap-up preserves durable verification evidence by reconciling live Git state, bridge statuses, and MemBase work items with the knowledge matrix so future agents inherit what actually happened.

What is the best way to generate a handoff prompt for the next AI agent?

Generate a handoff prompt by running wrap scanners, harvesting authorized deliberations, recording blockers with exact reasons, and inserting a self-contained next-session prompt into session_prompts.

How does knowledge base session wrap-up handle untracked Git artifacts and local evidence?

Knowledge base wrap-up explicitly references ignored local evidence paths instead of force-adding generated or untracked Git artifacts, running hygiene and consistency scanners to record outcomes.

What should I do when governance or tooling prevents updating durable memory during a wrap-up?

When governance or tooling prevents durable memory updates, record blockers with exact reasons and preserve the handoff prompt text alongside an explicit blocker statement for continuity.

When do I need to run reconciliation across Git state and MemBase work items?

Run live reconciliation across Git state, bridge INDEX.md statuses, and MemBase spec assertions during sessions that require durable knowledge capture and continuity context for the next agent.

Can I use kb-session-wrap to close a specific session id like S347?

Yes, kb-session-wrap executes the full GT-KB knowledge-first session wrap-up for a specific session id like S347 and produces the next-session handoff prompt with any blockers recorded.