workflow-creator

Generates a workflow-spec.md and SKILL.md package from brainstormed user ideas using discovered atomic skills.

339|58|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/Heyvhuang/ship-faster --skill workflow-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-creator
Source: https://github.com/Heyvhuang/ship-faster/tree/main/skills/workflow-creator
Command: npx skills add https://github.com/Heyvhuang/ship-faster --skill workflow-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps teams design end-to-end workflows by composing existing skills into a single reusable workflow package, turning rough ideas into a concrete, testable workflow skeleton and SSOT (workflow-spec.md) via brainstorm, discovery, and generation steps.

Core Features & Use Cases

  • Compose existing skills into end-to-end workflows rather than copying content.
  • Generate a new workflow-<slug>/ skill package and the SSOT at references/workflow-spec.md.
  • Enforce a plan-then-confirm execution model and record proposals, tasks, and approvals in run artifacts.

Quick Start

Use the workflow-creator to generate a new workflow-<slug> from an idea by following prompts to brainstorm, discover skills, and write a workflow_spec.md and SKILL.md.

Frequently Asked Questions about workflow-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I orchestrate existing skills into an end-to-end automation workflow?

You can orchestrate existing atomic skills into an end-to-end automation workflow by composing them into a single resumable package, which generates a concrete workflow specification and a single source of truth.

What is a plan-then-confirm workflow execution model?

A plan-then-confirm workflow execution model enforces governance by requiring explicit approval before proceeding, recording proposals, tasks, and confirmations in run artifacts like proposal.md and tasks.md.

How do I turn a rough project idea into a concrete workflow specification?

To turn a rough idea into a concrete workflow specification, you brainstorm, discover local skills, and generate a new workflow package containing an SSOT workflow-spec.md and a SKILL.md skeleton.

Do I need local skills installed to generate a reusable workflow package?

Yes, local skill discovery is required to generate a reusable workflow package, allowing the workflow-creator to compose existing atomic capabilities rather than copying content or starting from scratch.

What artifacts are generated when composing scattered capabilities into a governance workflow?

Composing scattered capabilities into a governance workflow generates a workflow-<slug>/ skill package containing artifacts like proposal.md, tasks.md, context.json, and references/workflow-spec.md as the SSOT.

Can I use skills.sh lookup if local skill discovery finds no matching atomic skills?

Yes, if local skill discovery is insufficient, you can use an optional skills.sh lookup to find matching atomic skills to compose into your end-to-end workflow specification.