capcom
Check mission status and progress via fresh subagent. Queries Beads for features, tasks, bugs, and recent work activity. Keeps HOUSTON context lean.
What this skill does
# /capcom - Status Check
Check current status and progress using Beads. Spawns a fresh subagent to do the heavy lifting, keeping HOUSTON's context lean.
---
## Instructions
When the user runs `/capcom`, spawn a Task agent to gather and format status:
### Step 1: Spawn CAPCOM Subagent
Use the Task tool with subagent_type `general-purpose`:
```
You are a CAPCOM status agent for Space-Agents.
TASK: Query the current state using Beads and return a formatted status report.
Run these Beads commands:
1. Statistics overview:
bd stats
2. Features (in_progress first, then open):
bd list -t feature --status in_progress
bd list -t feature --status open
3. Tasks by status:
bd list -t task --status in_progress
bd list -t task --status open
4. Open bugs:
bd list -t bug --status open
5. Blocked issues:
bd blocked
6. Dependency tree (full structure):
bd list --tree
7. Recent work activity (check comments on in_progress issues):
For each in_progress issue, run: bd comments {issue-id}
Filter comments containing [ATTEMPT], [PROGRESS], [BLOCKED], or [HANDOVER] titles
FORMAT your response as:
[CAPCOM_REPORT]
STATISTICS
─────────────────
[bd stats summary]
FEATURES
─────────────────
[In Progress]
{list in_progress features with status indicator}
[Open]
{list open features with priority}
TASKS
─────────────────
[In Progress]
{list in_progress tasks}
[Open/Ready]
{list open tasks}
BUGS
─────────────────
{list open bugs by priority}
BLOCKED
─────────────────
{list blocked issues with what blocks them}
DEPENDENCY TREE
─────────────────
{bd list --tree output}
RECENT ACTIVITY
─────────────────
{Recent [ATTEMPT], [PROGRESS], [BLOCKED] comments from active work}
End with [CAPCOM_COMPLETE]
```
### Step 2: Display and Highlight
Display subagent report. Emphasize blocked issues and critical bugs.
---
## Example Output
```
CAPCOM STATUS REPORT
────────────────────
STATISTICS: 25 issues (13 open, 2 in_progress, 5 blocked)
FEATURES [In Progress]
◐ space-agents-1.1: Execution Flow Skills (P1)
TASKS [In Progress]
◐ space-agents-1.1.3: Update /capcom...
BLOCKED
● space-agents-1.3.2 ← space-agents-1.3.1
DEPENDENCY TREE
[bd list --tree output]
RECENT ACTIVITY
[PROGRESS] space-agents-1.1.3 (10m): Updated skill...
────────────────────
HOUSTON standing by.
```
---
## Optional Filters
- `/capcom bugs` - Show only bugs
- `/capcom blocked` - Show only blocked issues
- `/capcom feature {id}` - Show specific feature and its tasks
---
## Error Handling
| Condition | Response |
|-----------|----------|
| Beads not initialized | Prompt `/install` |
| Subagent fails | Fall back to direct `bd stats && bd list --tree` |
| No active work | Suggest `/exploration` or `bd create` |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.