Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Seven-stage research workflow (SCOPE→LITERATURE→REASON→DESIGN→COMPUTE→SYNTHESIZE→WRITE). Use for: structuring an AI agent's research process, generating literature review prompts, scoping methodology. Usage: from infrastructure.research import ResearchWorkflow; ResearchWorkflow.describe() Config: set stage overrides in projects/{name}/manuscript/config.yaml `research_workflow:` block.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | 63% | 0% |
| case-03 | ✗→✓ | ▲ Improved | 85% | 0% |
| case-07 | ✗→✓ | ▲ Improved | -51% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -12% | 0% |
| case-09 | ✗→✓ | ▲ Improved | -5% | 0% |
Seven-stage research workflow scaffolding for AI-assisted research processes. Each stage produces structured prompts and acceptance criteria for agent loops.
| # | Stage | Purpose | | --- | --- | --- | | 1 | SCOPE | Define research question, scope, and success criteria | | 2 | LITERATURE | Survey prior work; produce annotated bibliography | | 3 | REASON | Identify gaps, contradictions, and open questions | | 4 | DESIGN | Formulate methodology and experimental plan | | 5 | COMPUTE | Execute analysis; collect and validate results | | 6 | SYNTHESIZE | Interpret results relative to prior work | | 7 | WRITE | Draft manuscript sections and iterative revision |
pythonfrom infrastructure.research import ResearchWorkflow # Print all stage descriptions ResearchWorkflow.describe() # Get a structured prompt for a specific stage prompt = ResearchWorkflow.prompt("SCOPE", question="What drives protein misfolding?") print(prompt) # Iterate stages in order for stage in ResearchWorkflow.stages(): print(f"{stage.index}. {stage.name}: {stage.description}")
bash# Run research workflow scaffolding for a named project uv run python scripts/pipeline/stage_10_research_workflow.py --project my_project # Run only specific stages uv run python scripts/pipeline/stage_10_research_workflow.py --project my_project --stages SCOPE,LITERATURE # Generate stage prompts without executing uv run python scripts/pipeline/stage_10_research_workflow.py --project my_project --dry-run
Set stage overrides in projects/{name}/manuscript/config.yaml:
yamlresearch_workflow: question: "How do transformer attention patterns relate to syntactic structure?" stages: SCOPE: depth: detailed LITERATURE: max_papers: 50 sources: - arxiv - semantic_scholar WRITE: target_venue: NeurIPS
pythonfrom infrastructure.research import ( ResearchWorkflow, # instance API — workflow.stage(name) / all_stages() / describe() ResearchStage, # Stage descriptor: name, label, description, inputs, outputs, gate, status, order ResearchWorkflowConfig, # Parsed config.yaml `research_workflow:` block )
> Doc/code drift (tracked for follow-up): the "Stages" table, .prompt(), > .stages(), .render(), and .record_output() calls elsewhere in this > file describe an OpenScience-ported design (uppercase SCOPE/LITERATURE/... > stage names, per-stage sub-agent fan-out and prompt templates) that > ResearchWorkflow/ResearchStage do not implement — the real stage names > are lowercase (scope, survey, hypothesise, experiment, validate, review, > write) and there is no .prompt()/.stages()/.render() API. Treat > those sections as design intent, not a verified API surface.
pythonfrom infrastructure.research import ResearchWorkflow # Generate LITERATURE stage prompt for a specific project prompt = ResearchWorkflow.prompt( "LITERATURE", question="Neural scaling laws", context={"prior_papers": 12, "target_venue": "ICML"}, )
pythonfrom infrastructure.research import ResearchWorkflow # Use in an agent loop for stage in ResearchWorkflow.stages(): prompt = stage.render(project_context) response = llm_call(prompt) stage.record_output(response, output_dir="output/research/")
bashuv run pytest tests/infra_tests/research/ -v
AGENTS.md — operating contract and architecture../search/SKILL.md — literature search integration../llm/SKILL.md — LLM review integrationOther measured skills in the registry, with their headline benchmark lift.