| name | genius-focus |
| description | Use when the user runs /genius-focus or asks GENIUS to break a local sub-problem (a principle/formula/math/method) inside an EXISTING project. Auto-understands the project, surfaces candidate sub-problems, user picks one, then runs a scoped axioms-grounded debate (+gated EVOLVE). |
GENIUS — focus (local breakthrough in an existing project)
Plugin paths. This is a globally-installed plugin; bundled files live under the plugin root, NOT
the current working directory. Resolve the absolute plugin root once: echo "$CLAUDE_PLUGIN_ROOT"
(Bash) → PLUGIN_ROOT. The current project root is the cwd → PROJECT_ROOT (pwd). runDir goes
in the user's CURRENT project as a RELATIVE path (the workflow safety guard rejects absolute paths
and ..).
-
Resolve paths and flags. Resolve PLUGIN_ROOT (echo "$CLAUDE_PLUGIN_ROOT") and
PROJECT_ROOT (pwd). Note --no-explore if present in the args. Set today (YYYY-MM-DD) and
make a slug from the sub-problem (or focus if none yet). Set a relative
runDir = genius-runs/<today>_focus-<slug>.
-
Understand. Launch the Workflow tool with scriptPath: "<PLUGIN_ROOT>/workflows/understand.js"
and args: { projectRoot: "<PROJECT_ROOT>", depth: "full" }. If the current project already has a
recent understand-map.json (same day, under any genius-runs/<today>_understand/), you MAY load
it instead of re-running (saves cost). The Workflow returns { map, critique, facet_summaries } —
OR { park: ... } if it could not map the project (e.g. reader-wipeout / missing projectRoot). On a
return, report the reason and STOP — do NOT persist the park object or build a pick-list
against undefined fields (fail explicitly, no silent fallback).
— so, unless you loaded a cached map, YOU must
persist: create and write both (the raw
returned object) and (readable) into it, PROMPTLY after the Workflow returns
(before the pick-list in step 3), following the same rendering as the skill.
This ensures the understand artifacts are always on disk even if the session is interrupted.
