output-dev-create-skeleton

To scaffold an Output workflow skeleton, run the Output SDK CLI to automatically generate the standard project layout. This creates ready-to-use folders and files under src/workflows/{workflow-name}/ to enforce naming consistency and remove manual setup.

A standard Output workflow folder structure includes main files: workflow.ts, steps.ts, and types.ts. It also generates optional prompts and scenarios directories to accelerate onboarding and reduce project boilerplate.

You need to generate a workflow skeleton when starting a brand-new Output workflow or onboarding teammates. It standardizes the project layout, enforces naming conventions, and documents the required file structure before implementation begins.

Yes, you can use the Output SDK CLI to standardize project layout across your team. It generates a consistent folder structure and provides guidance on naming conventions, ensuring all teammates follow the same workflow structure conventions.

No, generating an Output workflow skeleton removes manual folder and file creation. The skeleton conventions are enforced automatically by the CLI, which generates the standard template layout so developers can skip boilerplate setup.

The best way to structure a new Output workflow is using a scaffolding tool to generate a skeleton layout. This enforces consistent project structure by creating standard files like workflow.ts and steps.ts, reducing boilerplate and accelerating onboarding.