pre-reg-to-dispatch

Converts pre-registered research designs into dispatchable Task Prompts with amendment detection.

1|Updated Dec 13, 2025
One-click install
npx skills add https://github.com/ZK-Theory/TDL --skill pre-reg-to-dispatch-zk-theory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pre-reg-to-dispatch
Source: https://github.com/ZK-Theory/TDL/tree/main/.agents/skills/pre-reg-to-dispatch
Command: npx skills add https://github.com/ZK-Theory/TDL --skill pre-reg-to-dispatch-zk-theory

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an APM Manager turns a pre-registered study design into a dispatchable task, it is easy to accidentally change a parameter or decision rule without filing a pre-registration amendment, silently breaking the confirmatory integrity of the research. This Skill extracts the locked parameters, decision rule, and outcome-to-prose mapping from the pre-registration and detects whether a task merely executes the existing design or requires an amendment filed before dispatch. ## Core Features & Use Cases - Pre-Registration Extraction: Locates the governing pre-registration entry and its machine-readable JSON mirror, then extracts locked parameters, the decision rule, and the outcome-to-prose mapping. - Amendment Detection: Compares the intended task design against the pre-reg and flags any change to parameters, decision rules, null models, or eligibility rules as requiring a filed amendment before dispatch. - Task Prompt Generation: Emits the Research Assurance Requirements block, a task-state manifest, contract specifications, and dispatch-safety constraints (hard stops, blocking gates, no synthetic output in results). - Use Case: A Manager needs to rerun an analysis with a different asymmetry parameter. The Skill compares the change against the locked pre-reg, returns a verdict of "requires amendment before dispatch", and prevents an unregistered design choice from being baked into the run. ## Quick Start Ask the assistant to convert the pre-registered design in the methods log into a dispatchable Task Prompt and check whether any amendment is needed first.

Frequently Asked Questions about pre-reg-to-dispatch

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I convert a pre-registration into a dispatchable task prompt?

Locate the governing pre-registration entry and its JSON mirror, extract the locked parameters, decision rule, and outcome-to-prose mapping, then emit the Research Assurance Requirements block and task-state manifest. The Skill walks through each step and produces a paste-ready block for the Task Prompt.

When does a task require a pre-registration amendment before dispatch?

An amendment is required whenever the task changes a parameter, the decision rule, the null model, or the eligibility rule relative to the locked pre-registration. A routine rerun that merely executes the existing design does not need one.

What is the outcome-to-prose mapping in a pre-registration?

It is the locked mapping that states what each possible outcome (A/B/C) licenses in the manuscript prose. Without it, a result cannot be interpreted without a post-hoc choice, which breaks confirmatory integrity.

Can contract YAMLs be written to the main branch before a task branch exists?

No. Contract YAMLs written to main become orphan files because the future worktree is created from committed main. Instead, embed the contract specification as a planned_contracts array inside the pre-registration and materialize it at dispatch time.

What happens if an external specialist smoke test fails before dispatch?

Authentication, entitlement, timeout, budget, or availability failure is a hard stop. The error is preserved and returned to the owner without dispatch; the Skill forbids hunting credentials, editing environment files, retrying, or substituting a provider.

Why should a bug-fix rerun not restate full compute parameters?

Restating full parameters like B=1000 silently forces an unneeded recompute of expensive cached upstream artifacts. A confirmatory fix should recompute only from the cached intermediate and use an old-vs-new delta as confirmation.