research-pipeline

To orchestrate an end-to-end research workflow, you sequence three stage commands: idea-discovery, experiment-pipeline, and paper-writing. This enforces structured stage boundaries and generates defined handoff documents like IDEA_REPORT.md and PAPER_PLAN.md across the lifecycle.

Stage handoffs and artifact contracts in a research pipeline are enforced boundaries between discovery, experiments, and writing. They require defined outputs like EXPERIMENT_PLAN.md and RESULTS_SUMMARY.md to ensure structured coordination before progressing to the next phase.

You manage structured handoffs between experiments and manuscript writing by enforcing artifact contracts. The experiment-pipeline stage outputs NARRATIVE_REPORT.md and RESULTS_SUMMARY.md, which serve as the required inputs for the paper-writing stage to begin drafting the final manuscript.

Yes, you can use this research workflow orchestrator for projects requiring strict governance. It applies to projects requiring structured handoffs, artifact contracts, and governance across discovery to manuscript, enforcing three-stage coordination with defined outputs.

The best way to coordinate a full research lifecycle is using a top-level skill that enforces stage boundaries. By orchestrating idea discovery, experiment pipelines, and paper writing, it provides a structured workflow from a broad direction to a published manuscript.

Yes, the research workflow orchestrates three separate stage skills: idea-discovery, experiment-pipeline, and paper-writing. Invoking these stage commands in sequence runs the full end-to-end research lifecycle while enforcing the required artifact contracts.