QBall-Inc CLI Usage: When unsure about a CLI's interface or flags, run it with
--helpfirst. Do NOT attempt to discover functionality by reading plugin source code — doing so leads to incorrect execution from assumptions made without context of the holistic flow.
Reload CLEAR Context
This skill forces a reload of all CLEAR domain context into the current session. It re-triggers the SessionStart dispatcher (scripts/dispatchers/session-start.sh) with source: clear, refreshing session state + plan + workpackage + knowledge + sync state without reinitializing the project — see the session-management skill's "SessionStart Dispatcher Orchestration" section for the full fan-out.
The user-relevant surfaces are knowledge, workpackage, and plan (what gets injected into Claude's context); session and sync state are reloaded as supporting infrastructure.
Plugin Root Resolution
CLI commands in this skill reference $CLEAR_PLUGIN_ROOT — a .claude/settings.json env var the shell expands. The SessionStart hook persists it, but settings env vars load at session launch, so on a brand-new consumer's first session (before its next restart) the variable is empty and node "$CLEAR_PLUGIN_ROOT/build/..." fails with MODULE_NOT_FOUND.
First-session bootstrap — if $CLEAR_PLUGIN_ROOT is empty, set it inline in the same Bash call as the CLI (each Bash call is a fresh shell, so a separate export would not carry over):
export CLEAR_PLUGIN_ROOT="${CLEAR_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}"
Prepend it to the CLI in one shell line: export CLEAR_PLUGIN_ROOT="${CLEAR_PLUGIN_ROOT:-${CLAUDE_PLUGIN_ROOT}}"; <node "$CLEAR_PLUGIN_ROOT/build/..." command>. ${CLAUDE_PLUGIN_ROOT} resolves in this SKILL.md body to the actually-loaded plugin path; once the consumer restarts, $CLEAR_PLUGIN_ROOT is populated and the assignment is a harmless no-op.
When to Use This Skill
Load this skill when the user request matches ANY of these patterns:
| Trigger Pattern | Example User Request |
|---|---|
Manual edits to .clear/ files |
"I just edited my workpackage YAML, reload context" |
| Context seems stale or incomplete | "CLEAR context looks wrong, refresh it" |
| Recovery from context issues | "Context is broken, reload everything" |
| Changes made outside CLEAR commands | "I updated plan files manually, sync them" |
| Explicit reload request | "Run cf-reload" |
DO NOT use for:
- Project initialization or reinitializing a corrupted project (use
/cf-init --forceinstead) - Debugging CLEAR internals or inspecting state (use
/cf-debuginstead)
Usage
/cf-reload
No arguments. Reloads all domain context in place.
Instructions
Step 1: Execute the context reload
Run the session-start dispatcher with source: clear to trigger a full context reload:
echo '{"source": "clear", "cwd": "'"$(pwd)"'", "session_id": "manual-reload"}' | "${CLEAR_PLUGIN_ROOT}/scripts/dispatchers/session-start.sh"
Step 2: Confirm the result
After execution, verify that:
- The dispatcher ran without errors
- CLEAR context has been refreshed (confirmation output from the script)
Step 3: Report to the user
Inform the user that CLEAR context (knowledge, workpackage, plan) has been reloaded. If any errors occurred during the reload, report them with the full error output.
Completion Checklist
Before returning to the user, verify:
- Session-start dispatcher executed successfully with
source: clear - Context reload confirmation was received from the script
- No errors were produced during reload