Phase guidance for the neuroflow /tool-build command. Loaded automatically when /tool-build is invoked to orient agent behavior, relevant skills, and workflow hints for the tool-build phase.
From neuroflownpx claudepluginhub stanislavjiricek/neuroflow --plugin neuroflowThis skill uses the workspace's default tool permissions.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
The tool-build phase designs and implements lab tools or software pipelines — real-time systems, data acquisition, LSL integrations, or custom analysis pipelines.
tool-spec.md first; get confirmation before implementation beginsneuroflow:neuroflow-core — read first; defines the command lifecycle and .neuroflow/ write rulesneuroflow:pupil-labs-neon-realtime — if the tool involves Pupil Labs Neon hardware, use this skill for device discovery, multi-threaded streaming architecture, and real-time data collectionoutput_path (tools/), not inside .neuroflow/tool-spec.md to .neuroflow/tool-build/ before writing any implementation.neuroflow/reasoning/tool-build.json/neuroflow:tool-build — runs this workflow as a slash command.