Phase guidance for the neuroflow /preregistration command. Loaded automatically when /preregistration is invoked to orient agent behavior, relevant skills, and workflow hints for creating and managing pre-registration documents.
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 preregistration phase produces and manages pre-registration documents that commit the research team to a specific hypothesis, design, and analysis plan before data collection begins.
.neuroflow/ideation/ if it exists; pull paradigm details from .neuroflow/experiment/ if it exists — do not ask the user to repeat information already in project memoryneuroflow:neuroflow-core — read first; defines the command lifecycle and .neuroflow/ write rulesprereg-[registry]-[date].md — the primary pre-registration document; version-control this fileprereg-review-[date].md — completeness and consistency review reportdeviations.md — running log of post-registration deviations; append only, never overwrite past entriesregistered-report.md — metadata for any submitted or accepted registered reports (DOI, stage, date)