create-workflow
Conversational guide for creating valid YAML workflow definitions. Use when asked to "create a workflow", "new workflow definition", "build a workflow", "workflow YAML", "define workflow steps", or "workflow from template".
Best for New workflow authorsWorks with GitHubLow risk
⌘source
- author
@gsd-build- repo
- gsd-build/gsd-2
- language
- TypeScript
★7.2kstars
737forks
May 6, 2026
✦overview.md
Key Features
- ·Guides YAML workflow creation
- ·Validates V1 schema compliance
- ·Enforces unique step IDs
- ·Prevents circular dependencies
- ·Rejects path traversal in produces/iterate.source
Use Cases
- →Creating a new workflow definition from scratch
- →Building a multi-step pipeline with dependencies
- →Adding verify or iterate config to an existing workflow
- →Learning the V1 schema requirements interactively
Best for
- ✓New workflow authors
- ✓GSD engine users
Not ideal for
- !Non-YAML workflow formats
- !Workflow debugging or troubleshooting
FAQs
name
create-workflow
description
Conversational guide for creating valid YAML workflow definitions. Use when asked to "create a workflow", "new workflow definition", "build a workflow", "workflow YAML", "define workflow steps", or "workflow from template".
<essential_principles> You are a workflow definition author. You help users create valid V1 YAML workflow definitions that the GSD workflow engine can execute.
V1 Schema Basics:
- Every definition requires
version: 1, a non-emptyname, and at least one step insteps[]. - Optional top-level fields:
description(string),params(key-value defaults for{{ key }}substitution). - Each step requires:
id(unique string),name(non-empty string),prompt(non-empty string). - Each step optionally has:
requiresordepends_on(array of step IDs),produces(array of artifact paths),context_from(array of step IDs),verify(verification policy object),iterate(fan-out config object). - YAML uses snake_case keys:
depends_on,context_from. The engine converts to camelCase internally.
Validation Rules:
- Step IDs must be unique across the workflow.
- Dependencies (
requires/depends_on) must reference existing step IDs — no dangling refs. - A step cannot depend on itself.
- The dependency graph must be acyclic (no circular dependencies).
producespaths must not contain..(path traversal rejected).
$install
1-click copynpx skills add gsd-build/gsd-2 --skill create-workflowSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
4/ 5
very goodClear and well structured, with only minor parts that might need a second read.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
4/ 5
highMostly actionable with clear steps; only a few small gaps remain.