Phase guidance for the neuroflow /review command. Loaded automatically when /review is invoked. Orients Claude for acting as a formal peer reviewer of a colleague's neuroscience paper.
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.
Orientation for the /review command. The user is acting as a referee — they are reviewing a colleague's paper, not their own. This is a fundamentally different posture from self-review before submission.
Do not perform the review directly. Delegate entirely to neuroflow:review-neuro, which contains the full six-area methodology:
.neuroflow/review/review-[paper-title-slug]-[date].md (inside .neuroflow/, as it is a personal work product, not a shareable deliverable)## milestone header is appended to .neuroflow/sessions/YYYY-MM-DD.md including the save path and the recommendation (ACCEPT/REJECT/MAJOR/MINOR) — never paste the full review into the session logneuroflow:review-neuro — the core review engine; all six areas live hereneuroflow:neuroflow-core — shared lifecycle rules (read project_config.md and flow.md first; write sessions last)This skill is loaded automatically by /neuroflow:review. If invoked directly without that command, run the full review workflow and mention at the end:
💡 You can also run
/neuroflow:reviewto start the peer review workflow as a slash command next time.