Sponsor Suno AI Music arrow_forward
Skill

Output Build Workflow

Implement an Output SDK workflow from a plan document. Use when the user asks to build, implement, or code a workflow from an existing plan, or after output-plan-workflow has produced a plan and the user is ready to build.

Type
Skill
Repository
growthxai/output
GitHub stars
439
License
Apache-2.0
Repo last updated
Sep 25, 2026

What Output Build Workflow is

Output Build Workflow is a skill published in the growthxai/output repository on GitHub, which has about 439 stars. The repository describes itself as: “The open-source TypeScript framework for building AI workflows and agents. Designed for Claude Code describe what you want, Claude builds it, with all the best practices already in place.”

A skill is a folder with a SKILL.md file: frontmatter with a name and a description, followed by instructions Claude follows. Claude loads a skill automatically when a task matches its description, and you can also run it directly with a slash and its name.

Skills work in Claude Code and in Claude Cowork, which makes Output Build Workflow a portable way to give Claude the same method everywhere.

How to install Output Build Workflow

Claude Code

  1. Download the output-build-workflow folder from the repository.
  2. Save it as ~/.claude/skills/<skill-name>/SKILL.md for all projects, or .claude/skills/<skill-name>/SKILL.md for one project.
  3. Claude loads it automatically when a task matches; you can also run it with / and its name.

Claude Cowork

  1. Zip the skill folder so SKILL.md sits at the top level of the folder.
  2. Open Customize → Skills, click +, then upload the ZIP.
  3. Start a task that matches the description, or call it by name with /.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from coding_assistants/claude/plugins/outputai/skills/output-build-workflow/SKILL.md, shared under the repository's Apache-2.0 license. Read the full file on GitHub.

Your task is to implement an Output.ai workflow based on a provided plan document.

The workflow directory is provided as an argument (the workflow directory path). The workflow skeleton should already have been created there; if it has not, create it first.

Please read the plan file and implement the workflow according to its specifications.

Use the todo tool to track your progress through the implementation process.

Implementation Rules

Overview

Implement the workflow described in the plan document, following Output SDK patterns and best practices.

EXECUTE: Claude Skill: output-meta-pre-flight

Step 1: Plan Analysis

Read and understand the plan document.

  1. Read the plan file from the provided plan file path
  2. Identify the workflow name, description, and purpose
  3. Extract input and output schema definitions
  4. List all required steps and their relationships
  5. Note any LLM-based steps that require prompt templates
  6. Understand error handling and retry requirements

Step 2: Workflow Implementation

Update workflow.ts in the workflow directory with the workflow definition.

  • Import required dependencies (workflow, z from '@outputai/core')
  • Define inputSchema based on plan specifications
  • Define outputSchema based on plan specifications
  • Import step functions from steps.ts
  • Implement workflow function with proper orchestration
  • Handle conditional logic if specified in plan
  • Add proper error handling
  • When catching a specific step or evaluator error, use hasErrorType(error, ErrorClass) instead of instanceof (see output-error-try-catch)
import { workflow, z } from '@outputai/core';
import { stepName } from './steps.js';

const inputSchema = z.object( {
  // Define based on plan
} );

const outputSchema = z.object( {
  // Define based on plan
} );

export default workflow( {
  name: 'workflow-name-from-plan',
  description: 'Description from plan',
  inputSchema,
  outputSchema,
  fn: async input => {
    // Implement orchestration logic from plan
…

Step 3: Steps Implementation

Update steps.ts in the workflow directory with all step definitions from the plan.

  • Import required dependencies (step, z from '@outputai/core')
  • Implement each step with proper schema validation
  • Add error handling and retry logic as specified
  • Ensure step names match plan specifications
  • Add descriptive comments for complex logic
import { step, z } from '@outputai/core';

export const stepName = step( {
  name: 'stepName',
  description: 'Description from plan',
  inputSchema: z.object( {
    // Define based on plan
  } ),
  outputSchema: z.object( {
    // Define based on plan
  } ),
  fn: async input => {
    // Implement step logic from plan
    return output;
  }
} );

Step 3.5: Evaluators Implementation (if needed)

If the plan includes evaluator functions, implement them in evaluators.ts in the workflow directory.

IF plan_includes_evaluators: CREATE evaluators.ts IMPLEMENT evaluator functions per plan ELSE: SKIP to step 4

  • Import required dependencies (evaluator, z, result types from '@outputai/core')
  • Import generateText and aiSdk from @outputai/llm if using LLM-powered evaluators
  • Implement each evaluator with proper schema validation
  • Use appropriate result types (EvaluationBooleanResult, EvaluationNumberResult, EvaluationStringResult)
  • Include confidence scores (0.0-1.0)
  • Add reasoning for transparency
  • All imports use .js extension
  • Consider offline eval tests for dataset-driven verification (see output-dev-eval-testing skill)
import { evaluator, z, EvaluationBooleanResult } from '@outputai/core';

export const evaluateName = evaluator( {
  name: 'evaluate_name',
  description: 'Description from plan',
  inputSchema: z.object( {
    // Define based on plan
  } ),
  fn: async input => {
    // Implement evaluation logic from plan
    return new EvaluationBooleanResult( {
      value: true,
      confidence: 0.95,
      reasoning: 'Explanation of evaluation'
    } );
  }
} );

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Output Build Workflow?

Output Build Workflow is a skill for Claude Code and Claude Cowork from the growthxai/output repository on GitHub. Implement an Output SDK workflow from a plan document. Use when the user asks to build, implement, or code a workflow from an existing plan, or after output-plan-workflow has produced a plan and the user is ready to build.

How do I install Output Build Workflow in Claude Code?

Download the output-build-workflow folder from the repository. Save it as ~/.claude/skills/<skill-name>/SKILL.md for all projects, or .claude/skills/<skill-name>/SKILL.md for one project. Claude loads it automatically when a task matches; you can also run it with / and its name.

Can I use Output Build Workflow in Claude Cowork?

Zip the skill folder so SKILL.md sits at the top level of the folder. Open Customize → Skills, click +, then upload the ZIP. Start a task that matches the description, or call it by name with /.

Is Output Build Workflow safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under Apache-2.0. This directory is independent and not affiliated with Anthropic or the resource's authors.