← ClaudeAtlas

wise-workflow-createlisted

Scaffold a new workflow through a step-by-step wizard — collects name, description, project-selection policy, pre-flight pins, inputs, and steps (id, type, type-specific fields, dependencies), previews the generated YAML + README, and writes on confirmation. Writes to `${CLAUDE_PLUGIN_DATA}/workflows/definitions/<name>/` by default, or offers the bundled `plugins/wise/workflows/<name>/` path when run inside a clone of the marketplace repo. Invoked as `/wise-workflow-create` (bare alias) or `/wise:wise-workflow-create` (canonical). Use when the user says "create a workflow", "scaffold a workflow", "new workflow", "author a workflow", or types `/wise-workflow-create`.
e1024kb/wise-claude · ★ 1 · AI & Automation · score 77
Install: claude install-skill e1024kb/wise-claude
# /wise-workflow-create — wizard for a new workflow ## Why this skill exists Writing workflow YAML by hand is error-prone (schema is strict, DAG edges are easy to mis-draw). This skill walks the user through the schema step-by-step via `AskUserQuestion`, validates as it goes, and produces a well-formed file. Two write destinations are supported: - **User-authored (default)** — `${CLAUDE_PLUGIN_DATA}/workflows/definitions/<name>/workflow.yaml`. Private to the user's machine; not tracked in any repo. This is the right place for one-off or personal workflows. - **Bundled (opt-in when in-repo)** — `<repo>/plugins/wise/workflows/<name>/workflow.yaml` inside a clone of the wise plugin's marketplace repo. Ships with the plugin, tracked in git, seen by every wise installer. The wizard only offers this mode when it detects it's running inside such a clone (see [§2.5](#25-detect-write-destination) below). Both destinations use the folder form — `<name>/workflow.yaml` — so a workflow can later grow sibling `templates/` / `prompts/` directories without a layout migration. The wizard deliberately **does not delegate to `skill-creator`** — workflows aren't skills; the YAML shape is our own. ## Arguments Read `$ARGUMENTS`. The first whitespace-separated token is the workflow `<name>`. When `$ARGUMENTS` is empty, stop with an error pointing at the expected form (`/wise-workflow-create my-flow`). - `name` — workflow name; kebab-case; matches the filename. Must not be `l