bc-session-close

Close Be Civic procedure sessions by saving progress and submitting approved items.

Updated May 16, 2026
One-click install
npx skills add https://github.com/Be-Civic/be-civic-plugin --skill bc-session-close
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bc-session-close
Source: https://github.com/Be-Civic/be-civic-plugin/tree/main/skills/bc-session-close
Command: npx skills add https://github.com/Be-Civic/be-civic-plugin --skill bc-session-close

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users finish Be Civic administrative sessions by organizing progress, reviewing contributions, submitting approved updates, and preserving unfinished work safely.

Core Features & Use Cases

  • Session Completion Workflow: Runs a structured close process covering progress summaries, state saving, observation review, submission handling, and final guidance.
  • Contribution and Submission Management: Reviews user-approved notes, prepares supported submissions, handles API delivery, and provides local fallback storage when submissions cannot be sent.
  • Use Case: When a customer finishes a Belgian administrative procedure session, use this Skill to save their progress, review possible civic contributions, submit approved items, and prepare the next session.

Quick Start

Use the bc-session-close skill to complete the current Be Civic session and review any pending submissions.

Frequently Asked Questions about bc-session-close

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

FAQPage Schema
How do I safely complete civic procedure sessions and preserve administrative workflow state?

To safely complete civic procedure sessions, run a structured close process that generates progress summaries, saves state, reviews observations, and handles approved administrative submissions. This ensures unfinished administrative work is preserved and properly managed.

What happens to pending civic submissions if the administrative API communication fails?

If API communication fails during civic submissions, the system uses local fallback storage to preserve the approved administrative updates. This deferred submission recovery ensures your dossier checks and contribution handoffs remain intact for later delivery.

How do I review user-approved contributions before finalizing an administrative dossier?

You review user-approved contributions by running the session close workflow, which includes observation review and validation gates. This checks the administrative dossier, prepares supported submissions, and validates items before final API delivery.

Do I need validation gates to handle deferred submission recovery for civic procedures?

Yes, validation gates are required to handle deferred submission recovery safely. They ensure that delayed civic procedure submissions pass state persistence checks and controlled submission handling before being sent through the configured wire utility.