---
name: fluxpoint-release
description: Release a node parked on a human or a third party — record the proof that the work actually happened, so the campaign can resume on evidence rather than recollection. Codex entry point for the fluxpoint `release` command.
user-invocable: false
disable-model-invocation: true
---

This skill is how Codex reaches the `release` command of the fluxpoint
plugin; on Claude Code the same command is `/fluxpoint:release`, and the two
Claude-only keys above keep this entry point out of that runtime's menus so
nothing is listed twice.

1. Read `../../commands/release.md`, relative to this file. Under an installed
   plugin that is `${PLUGIN_ROOT}/commands/release.md`; Codex also sets
   `CLAUDE_PLUGIN_ROOT` to the same directory, which is what the command's
   own shell snippets use.
2. Carry out its steps exactly as written, in order, and report as it says.
   The text of the user's request stands in for `$ARGUMENTS` ([node id, or nothing to list what is blocked]).
3. Where the command names a subagent from `agents/`, run one with that
   file's contents as its instructions, or perform the pass inline when no
   subagent can be spawned. Where it names the Workflow tool, note that graph
   execution is Claude Code only and follow the command's own fallback.