phase3-main-experiment

Orchestrate Phase 3 experiment matrices across datasets, LLMs, and baselines.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/YurainSoon/research-director --skill phase3-main-experiment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: phase3-main-experiment
Source: https://github.com/YurainSoon/research-director/tree/main/.claude/skills/phase3-main-experiment
Command: npx skills add https://github.com/YurainSoon/research-director --skill phase3-main-experiment

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Phase 3 main experiment orchestration solves the bottleneck of turning a Phase 2 validated slice into a full experimental matrix, coordinating spec upgrades, code upgrades, matrix execution, and narrative checkpoints to produce the Main Results table a paper requires.

Core Features & Use Cases

  • Orchestrates spec upgrades (Architect ↔ Confirmer) to expand a minimal matrix to full coverage.
  • Coordinates code upgrades (Coder ↔ Fidelity) and matrix execution across datasets, LLMs, and baselines.
  • Ensures narrative checkpoints via the Story Advisor and produces traceable outputs for analysis and handoff.

Quick Start

Start the Phase 3 pipeline by loading the latest Phase 2 exit, generating framework_vX, and entering the Architect ↔ Confirmer loop to scope and execute the full experiment matrix.

Frequently Asked Questions about phase3-main-experiment

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

FAQPage Schema
How do I scale a validated experiment slice into a full experimental matrix?

To scale a validated experiment slice into a full experimental matrix, use an orchestration pipeline that coordinates spec upgrades, code upgrades, and matrix execution across multiple datasets, LLMs, and baselines while preserving upstream validations.

What is the best way to orchestrate end-to-end research pipelines across multiple datasets and LLMs?

Orchestrating end-to-end research pipelines across multiple datasets and LLMs requires a locked EXPERIMENT_SETUP and validated phase_1 specs, utilizing a robust Runner, Analyst, and Story Advisor loop to ensure reproducible results and traceable decisions.

How do I coordinate code upgrades and spec upgrades for a research matrix?

Coordinate code upgrades and spec upgrades for a research matrix by applying an Architect-Confirmer loop to expand coverage and a Coder-Fidelity loop to execute the matrix, ensuring narrative checkpoints via a Story Advisor for traceable outputs.

Do I need a locked EXPERIMENT_SETUP before starting Phase 3 experiment orchestration?

Yes, you need a locked EXPERIMENT_SETUP and validated phase_1 specs before starting Phase 3 experiment orchestration to enforce requirements and ensure reproducible results when expanding a minimal matrix to full coverage.

How does a Story Advisor loop ensure narrative checkpoints in experimental research?

A Story Advisor loop ensures narrative checkpoints in experimental research by evaluating traceable outputs and decisions during matrix execution, producing the coherent narrative structure required for a Main Results table in a paper.

Why does my experiment matrix execution fail to preserve upstream validations?

Experiment matrix execution fails to preserve upstream validations if the pipeline lacks a locked EXPERIMENT_SETUP or bypasses the structured Runner, Analyst, and Story Advisor loop required to maintain traceable decisions across datasets.