Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

phase-preregistration

Estrelas6

Forks0

Atualizado11 de março de 2026 às 20:40

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.

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

stanislavjiricek

stanislavjiricek/neuroflow

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Cientistas de pesquisa em computação e informaçãoInformática e Matemática·SOC 15-1221

SKILL.md

readonly

name	phase-preregistration
description	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.

phase-preregistration

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.

Approach

Identify which mode applies (draft, review, deviation log, link registered report) before starting
Always pull the research question and hypothesis from .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 memory
Ask which registry or template applies before drafting; structure adapts significantly between OSF and AsPredicted
In all pre-registration drafts: hypotheses must be directional and falsifiable, analysis plans fully specified, and exploratory analyses clearly distinguished from confirmatory ones
If a power calculation is missing, prompt the user to provide one before saving the document
After data collection begins, use the deviation log mode to record any plan changes — never silently edit a submitted pre-registration document

Relevant skills

neuroflow:neuroflow-core — read first; defines the command lifecycle and .neuroflow/ write rules

Workflow hints

prereg-[registry]-[date].md — the primary pre-registration document; version-control this file
prereg-review-[date].md — completeness and consistency review report
deviations.md — running log of post-registration deviations; append only, never overwrite past entries
registered-report.md — metadata for any submitted or accepted registered reports (DOI, stage, date)
Pre-registration documents are the scientific record — flag any ambiguity that could allow selective reporting or HARKing (Hypothesizing After Results are Known)
If the user is drafting for a registered report journal submission, note that stage 1 acceptance is typically contingent on the analysis plan being fully specified

Mais deste repositório

mesmo repositório

autoresearch

stanislavjiricek/neuroflow

Infinite improvement loop for any research artifact in any phase — a single managing agent makes one focused change per iteration, judges it against the previous best, keeps or reverts. Its memory is a per-loop wiki it reads before every move and writes after every move. The loop never stops until the human interrupts it. Inspired by Andrej Karpathy's autoresearch (MIT).

2026-06-046

phase-git

stanislavjiricek/neuroflow

Phase guidance for /git — context-aware git shorthand rules, smart push/pull logic, commit message generation, branch management, and PR creation workflow.

2026-06-036

bids

stanislavjiricek/neuroflow

This skill should be used whenever the user mentions BIDS, Brain Imaging Data Structure, BIDS conversion, BIDS validation, BIDS compliance, organizing neuroimaging data, dataset_description.json, participants.tsv, bids-validator, pybids, MNE-BIDS, or asks how to structure EEG/MEG/fMRI/iEEG/PET/DWI data for sharing or preprocessing. Also invoke when the user asks how to name scan files, what sidecar JSON fields are needed, how to set up derivatives/, or how to run fMRIPrep/MRIQC on their dataset. Invoke proactively during /data, /data-preprocess, and /data-analyze phases whenever the dataset structure is relevant to the task at hand.

2026-05-296

phase-data-analyze

stanislavjiricek/neuroflow

Phase guidance for the neuroflow /data-analyze command. Loaded automatically when /data-analyze is invoked to orient agent behavior, relevant skills, and workflow hints for the data-analyze phase.

2026-05-296

phase-data-preprocess

stanislavjiricek/neuroflow

Phase guidance for the neuroflow /data-preprocess command. Loaded automatically when /data-preprocess is invoked to orient agent behavior, relevant skills, and workflow hints for the data-preprocess phase.

2026-05-296

phase-data

stanislavjiricek/neuroflow

Phase guidance for the neuroflow /data command. Loaded automatically when /data is invoked to orient agent behavior, relevant skills, and workflow hints for the data intake phase.

2026-05-296

name	phase-preregistration
description	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.

phase-preregistration

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.

Approach

Identify which mode applies (draft, review, deviation log, link registered report) before starting
Always pull the research question and hypothesis from .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 memory
Ask which registry or template applies before drafting; structure adapts significantly between OSF and AsPredicted
In all pre-registration drafts: hypotheses must be directional and falsifiable, analysis plans fully specified, and exploratory analyses clearly distinguished from confirmatory ones
If a power calculation is missing, prompt the user to provide one before saving the document
After data collection begins, use the deviation log mode to record any plan changes — never silently edit a submitted pre-registration document

Relevant skills

neuroflow:neuroflow-core — read first; defines the command lifecycle and .neuroflow/ write rules

Workflow hints

prereg-[registry]-[date].md — the primary pre-registration document; version-control this file
prereg-review-[date].md — completeness and consistency review report
deviations.md — running log of post-registration deviations; append only, never overwrite past entries
registered-report.md — metadata for any submitted or accepted registered reports (DOI, stage, date)
Pre-registration documents are the scientific record — flag any ambiguity that could allow selective reporting or HARKing (Hypothesizing After Results are Known)
If the user is drafting for a registered report journal submission, note that stage 1 acceptance is typically contingent on the analysis plan being fully specified