メニュー
Run the continuous experiment loop, including idea tournament, best-first tree expansion, mandatory literature cadence, bold swings, automatic commits, and memory write-back.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Gather literature, extract structured claims, and verify their sources and codebase relevance as one trust-preserving pipeline.
Run an autonomous research or optimization loop with literature-grounded, verifiable long-term memory. Use for measurable optimization and for ranked research-plan ideation.
Generate grounded novel hypotheses from contradictions, complementary claims, and cross-domain mechanism transfers using the unified synthesize tool.
Produce the autoresearch report with full idea lineage — paper → claim → hypothesis → patch → metric change → status → memory update. Use to summarize an autoresearch run into an auditable, human-readable report at .autoresearch-vkf/session/report.md.
| name | autoresearch-vkf-hypothesis-loop |
| description | Run the continuous experiment loop, including idea tournament, best-first tree expansion, mandatory literature cadence, bold swings, automatic commits, and memory write-back. |
Each iteration:
recall_memory; do not repeat settled experiments.plan_next_step. If it returns a REQUIRED literature refresh, run the
autoresearch-vkf-knowledge pipeline, remember_claim the findings, and
re-run the planner. This directive persists until satisfied.[BOLD — mandatory this iteration] pick is not optional.vkf_run_experiment, then vkf_log_experiment with the planner's
parent_id and node_kind.session/prompt.md, post important milestones through
research_update, and immediately start the next iteration.The search is a tree: expand the best node or backtrack and branch. Do not just mutate the latest result. Low-altitude knob tuning is excluded unless the user asked for tuning or there is direct evidence that one specific knob is the active bottleneck.
vkf_log_experiment commits the working change on the current branch. A
non-kept experiment is automatically rolled back with git revert, followed by
a separate memory commit so the knowledge survives. Never run git yourself to
keep or discard an experiment. User commits made between iterations are valid
and remain in the linear history. If the tool reports a revert conflict, restore
the worktree manually and record the issue.
Continue until budget, STOP, target_value, or a user-only blocker. Exhausted
ideas require a literature refresh, not a report.