Use when converting a repository-specific question into an executable plan for the canonical perception-vs-imagery platform, including which configs to use, which controls belong in the fixed ladder, what artifacts must be produced, and how to keep Animus subsystem work separate from paper-claim work.
Use this skill after a question has been scoped and before code changes or long runs begin.
START_HERE.mddocs/ARCHITECTURE.mddocs/REPRODUCIBILITY.mddocs/VALIDATION.mddocs/CURRENT_EVIDENCE_FREEZE.mddocs/PAPER_1_CLAIMS_MAP.mddocs/BENCHMARK_LADDER.mdconfigs/canonical/Animus subsystem engineeringThreshold researchData acquisition / benchmark expansion.venv, and docs updates.configs/canonical/animus_core_decoder.yamlconfigs/canonical/multisubj_overlap_bootstrap.yamlconfigs/canonical/max_available_overlap.yamlconfigs/canonical/threshold_shared_private_p16.yamlconfigs/canonical/shared_private_smoke.yamlvit_l14_image_768 fixed unless the task is explicitly about target-space changes.private_dim=16diagnostic, not headline benchmark.docs/PAPER_1_CLAIMS_MAP.md, restate it as future evidence required rather than as a current claim.Produce a compact plan containing:
smoke_only, bootstrap_ready, paper_ready, or blockeddocs/CURRENT_EVIDENCE_FREEZE.md or only a narrower run reportablation-runner for executionpaper-drafter only after real results existrepro-auditor if the main question is rerunnability rather than designNormal sequence: research-scout -> experiment-design -> ablation-runner.
scripts/ surfaces unless the user explicitly wants historical reproduction.paper-drafter after results exist.