gnn-template-init

To bootstrap a GNN pipeline step, run the step 0 template to initialize a new module structure from an existing scaffold. This automatically generates the thin orchestrator pattern and modular folder layout required for consistent architecture.

A thin orchestrator pattern is a standardized scaffolding approach that provides a minimal, reusable skeleton for new pipeline steps. It ensures consistent architecture across modules by exposing standardized interfaces for step initialization and MCP tool integration.

No, you do not need to manually configure MCP tool exposure. The template initialization provides standardized interfaces for MCP integration automatically, ensuring versioned metadata and reusable templates are correctly exposed across pipelines.

The best way to standardize project structure is using a canonical, reusable scaffold for new GNN pipeline steps. This ensures consistent architecture and faster onboarding by generating initial project structures with versioned templates.

Yes, you can extend the generated templates with custom logic using the provided example-driven guidance. The reusable skeleton is designed to power ongoing pipeline development while maintaining the standardized step interfaces.

You should avoid template initialization if your pipeline step does not fit the thin orchestrator pattern or requires a non-modular folder layout. The scaffold is built for standardized architecture and may constrain highly custom project structures.