workflow-node-builder

To ensure SOP compliance when adding a new external API node, this Skill enforces mandatory SOP document reads, requires explicit node type classification, and specifies deterministic deliverables for backend scaffolding and frontend meta registration.

Registering a new AI model for DAG execution requires applying an SOP-driven onboarding process that forces mandatory reading of model SOP documents and produces a structured implementation plan with stepwise validation.

Workflow nodes are classified into A-type LLM prompt nodes, B-type external tool/API nodes, and C-type plugins. This Skill requires explicit type judgment before any implementation planning to ensure correct backend scaffolding and frontend renderer setup.

Yes, the workflow node integration process supports both frontend and backend development by producing a complete implementation plan that specifies backend node scaffolding alongside frontend renderer and meta registration deliverables.

The best way to integrate a network search tool is to request SOP-enforced onboarding, which mandates reading the correct plugin SOP documents, classifying the node type, and generating a structured validation plan for the integration.

Mandatory SOP document reads are required before implementation to prevent inconsistent or non-compliant workflow-node additions, ensuring that all new external tools, plugins, and AI models follow a deterministic, verifiable delivery process.