Route hands-on implementation to Grok headless CLI — ONLY when the user explicitly asks for it (e.g. names Grok, or says "use grok-implementer"). Never trigger automatically. When invoked, the orchestrator AI (Claude Code, Cursor, Codex-as-orchestrator, etc.) freezes a work-order spec, runs Grok to
Route hands-on implementation to Grok headless CLI — ONLY when the user explicitly asks for it (e.g. names Grok, or says "use grok-implementer"). Never trigger automatically. When invoked, the orchestrator AI (Claude Code, Cursor, Codex-as-orchestrator, etc.) freezes a work-order spec, runs Grok to implement, then reviews the diff and re-runs proof. Skip when already inside a Grok session — never
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.