Research Lab
Use this for research-level work where the answer should be selected from evidence, not intuition. The workflow adapts to software, data analysis, academic synthesis, product strategy, policy, writing, or other domains.
Scope
- Work on one research item at a time.
- Keep research artifacts under
research/<slug>/unless the user or repo has an existing equivalent location. - Use the local project, user-provided sources, web sources, datasets, benchmarks, interviews, or examples as evidence depending on the domain.
- Ask questions only when the research item, constraints, or acceptable output cannot be inferred.
Load References
- Load
references/artifacts.mdbefore creating or resuming a research folder. - Load
references/phases.mdfor the detailed phase-by-phase workflow. - Load
references/domain-adaptation.mdwhen the theme is not software or the evidence and metrics need domain-specific translation. - Load
references/subagent-orchestration.mdwhen the user asks to use subagents to run framework phases.
Startup
- Identify the target research item, theme/domain, expected final output, user constraints, and any existing tracker or checklist item.
- Create a stable slug from the research item.
- Create or resume
research/<slug>/; readstate.md,decision.md, and priorruns/*/results.mdif present. - If the user asks for one phase, complete only that phase and write the handoff. Otherwise, run phases in order while feasible and stop at blockers, missing evidence, or an explicit decision gate.
- If subagent phase delegation is requested, keep the main agent as owner: delegate one phase at a time, review the result, then continue or fix.
Phase Flow
- Prepare: create the workspace, capture scope, list hypotheses, and record open questions.
- Specify: define inputs, outputs, success criteria, evidence sets, metrics, edge cases, and validation requirements.
- Baseline: build or document the simplest credible baseline and measure it.
- Explore: test one new or refined alternative per loop without repeating old approaches.
- Compare: evaluate viable approaches under a shared matrix of criteria, workloads, sources, or cases.
- Decide: select the approach or conclusion only when evidence gates pass; otherwise send the task back to Explore or Compare.
- Apply: create the final implementation, recommendation, report, policy, design, or other artifact exactly from the decision scope.
- Review: rerun targeted validation, compare against the saved decision, and reopen the loop if the result regresses or evidence no longer holds.
Non-Negotiable Rules
- Do not skip the spec, baseline, and decision phases unless the exception is
documented in
decision.mdorstate.mdwith a reason. - Do not create final target-artifact changes or final user-facing conclusions
before
decision.mdexists, unless the user explicitly asks for a lightweight answer. - Ground claims in observed evidence and record enough provenance to reproduce or audit the conclusion.
- Use comparable methods across runs; record environment, sources, assumptions, and limits.
- Update
state.mdafter every completed phase with status, evidence summary, open questions, and next phase. - Preserve prior research artifacts on resume; append new runs instead of rewriting history.
- Do not mark a delegated phase complete until the main agent has reviewed the subagent output and required validation passes.
Deliverables
research/<slug>/README.mdresearch/<slug>/state.mdresearch/<slug>/hypotheses.mdresearch/<slug>/runs/<timestamp>-<phase>/plan.mdresearch/<slug>/runs/<timestamp>-<phase>/results.mdresearch/<slug>/runs/<timestamp>-<phase>/metadata.jsonwhen measurements, sources, or reproducibility details need structured captureresearch/<slug>/decision.mdbefore final application
Handoff
When stopping, report the research path, completed phase, current best strategy or conclusion, missing evidence, and exact next phase.
References
references/artifacts.mdreferences/phases.mdreferences/domain-adaptation.mdreferences/subagent-orchestration.md