ワンクリックで
land
End session. Reconciles exploration folders, appends context to CAPCOM, syncs Beads, displays session stats.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
End session. Reconciles exploration folders, appends context to CAPCOM, syncs Beads, displays session stats.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Structure work into plans and Beads. Three modes: plan from brainstorm, plan from scratch, or create Beads from existing plan.
Execute a single task with Pathfinder/Builder/Inspector crew. Self-fetches work from Beads.
Select feature, select mode, delegate to execution skill.
Start a Space-Agents session. Displays welcome screen with project status.
HOUSTON spawns Pathfinder, Builder, Inspector per task. Best for medium features (4-10 tasks).
Launch ralph.sh in background. Lightweight mode (default) or full Pod crew (--pod). Best for large features (10+ tasks).
| name | land |
| description | End session. Reconciles exploration folders, appends context to CAPCOM, syncs Beads, displays session stats. |
Capture session context in CAPCOM and reconcile any folder states that were missed during the session.
Check for folder/state mismatches and fix them:
| If folder in... | But has... | Move to... |
|---|---|---|
exploration/ideas/ | plan.md | exploration/planned/ |
exploration/planned/ | Beads feature exists | mission/staged/ |
mission/staged/ | Beads feature closed | mission/complete/ |
For each mismatch: show user, confirm, then mv the folder.
git branch --show-current
git status --short
git log -1 --oneline
bd stats
bd list -t feature --status in_progress
From your session memory, note:
Get next session number:
grep -c "^## \[.*\] Session [0-9]" .space-agents/comms/capcom.md 2>/dev/null || echo 0
Add 1 to get the next session number.
Append full session context to .space-agents/comms/capcom.md:
## [YYYY-MM-DD HH:MM] Session {N}
**Branch:** {branch} | **Git:** {clean/uncommitted}
### What Happened
[Narrative of what was worked on. Be specific - file names, function names, what changed and why.]
### Decisions Made
[Architectural decisions, trade-offs chosen, "we decided X because Y". Skip if none.]
### Gotchas
[Things that surprised you, bugs encountered, "watch out for X". Skip if none.]
### In Progress
[If stopped mid-task: what state, next step, files involved. Skip if clean stop.]
### Next Action
[One clear thing to do next session.]
---
Guidelines:
Pre-flight:
bd doctor --quiet # Warn on failures, don't block
git status # Review pending changes
Stage and commit:
git add <specific files> # Stage code changes (not -A)
bd sync # Sync beads
git commit -m "feat: <summary from session>" # Meaningful message
git push
Commit message should summarize session work (e.g., "feat: update agent terminology, complete feature 1.2").
Query features and show progress:
bd list -t feature
bd list --tree
Output format:
SESSION COMPLETE
────────────────
Tasks completed: {count from session}
Bugs fixed: {count from session}
FEATURES
{for each feature from bd list -t feature}
{status_icon} {feature_title} [{closed_tasks}/{total_tasks}]
{end for}
Context saved to CAPCOM. Run /launch to continue.
Safe travels, Commander.
Status icons: ✓ closed, ◐ in_progress, ○ open, ● blocked