What is the CAPCOM log mentioned in the skill?

CAPCOM is an append-only Markdown file that serves as a master ledger for all activities and decisions made across your Space-Agents sessions.

Does this skill delete any of my code files?

No, it only clears the internal session buffer in .space-agents/staging/buffer.md to keep the environment clean for the next session.

What happens to my unsaved progress when I run /dock?

The skill reads your staging buffer, summarizes your work into the permanent CAPCOM log, and creates a handover file so no context is lost for the next session.

How do I resume work after docking?

Simply start a new session; the handover document generated during the dock process will provide the necessary context to pick up exactly where you left off.

Space-Agents Session Dock

Name: Space-Agents Session Dock
Author: thebrownproject

bythebrownproject

Productivity & Workflow

Terminates Space-Agents sessions by logging summaries, generating handovers, and clearing temporary buffers with a professional NASA-style logout.

About

The dock skill serves as the standardized exit procedure for the Space-Agents framework, assuming the role of HOUSTON, the Flight Director. It ensures project hygiene and continuity by querying session statistics from SQLite, appending a permanent summary to the CAPCOM log, and silently generating a handover document for the next session. By clearing the staging buffer and presenting a visual ASCII summary of objectives completed and voyage progress, it provides a clean, professional point of closure for AI-driven development workflows.

Key Features

Append-only CAPCOM logging for a permanent, auditable project history
0 GitHub stars
Automated session statistics retrieval from SQLite databases
Automated staging buffer cleanup to prevent context pollution in future sessions
NASA-inspired ASCII logout interface with visual progress bars
Silent handover generation for seamless context transfer between sessions

Use Cases

Maintaining a permanent ledger of project milestones and architectural decisions
Preparing detailed context for a future session through automated handover files
Finalizing a development sprint with a structured summary of key accomplishments

About

Key Features

Append-only CAPCOM logging for a permanent, auditable project history
0 GitHub stars
Automated session statistics retrieval from SQLite databases
Automated staging buffer cleanup to prevent context pollution in future sessions
NASA-inspired ASCII logout interface with visual progress bars
Silent handover generation for seamless context transfer between sessions

Use Cases

Maintaining a permanent ledger of project milestones and architectural decisions
Preparing detailed context for a future session through automated handover files
Finalizing a development sprint with a structured summary of key accomplishments