speckit-workflow

$npx mdskill add github/spec-kit-copilot/speckit-workflow

Manages Spec Kit automation workflows

  • Runs multi-step automations
  • Depends on Specify CLI
  • Decides based on workflow ID
  • Delivers results via JSON

SKILL.md

.github/skills/speckit-workflowView on GitHub ↗
---
name: speckit-workflow
description: 'Manage and run Spec Kit automation workflows via `specify workflow`. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use speckit-extension), presets (use speckit-preset), or bundles (use speckit-bundle).'
argument-hint: '<run|resume|status|list|add|remove|search|info|catalog> [workflow id or YAML path]'
---

# Spec Kit — workflows

Run and manage spec-kit automation workflows with the **Specify CLI**
`specify workflow` command group.

> **Prerequisite:** needs the `specify` CLI. If `specify --version` fails, install it
> with the **speckit-cli-setup** skill first.

## When to use

- Execute a multi-step spec-kit automation workflow.
- Resume a run that paused at a gate or failed, or check its status.
- Discover, install, or remove workflows.

## How to invoke

```bash
# Discover
specify workflow list
specify workflow search <query>
specify workflow info <id>             # details and step graph

# Run
specify workflow run <id-or-path>
specify workflow run <id> -i key=value -i other=value   # pass inputs
specify workflow run <id> --json                        # machine-readable outcome

# Resume / status
specify workflow status <run>
specify workflow resume <run>

# Install / remove
specify workflow add <id-or-url-or-path>
specify workflow remove <id>

# Catalogs (sources workflows are resolved from)
specify workflow catalog list
specify workflow catalog add <url> [--name <name>]
specify workflow catalog remove <index>         # by index

# Step types — see the speckit-workflow-step skill
specify workflow step --help
```

## Notes

- `run` accepts either an installed workflow **ID** or a path to a local **YAML** file.
- Pass inputs with repeated `-i key=value` (a.k.a. `--input`) flags.
- Use `--json` when you need to parse the run outcome programmatically; surface a
  human summary to the user afterward.
- If a run stops at a gate, use `specify workflow resume` rather than re-running
  from the start.
- To manage the **step types** workflows are built from, use the
  **speckit-workflow-step** skill.

More from github/spec-kit-copilot

SkillDescription
speckit-artifactInspect the effective Spec Kit artifact inventory and composition stacks via `specify artifact`. USE FOR: listing commands/templates/scripts/hooks, explaining which preset or extension layer supplies an artifact, inspecting resolution precedence and hidden layers, checking hook registration, or resolving a stack lookupId to its validated contribution. DO NOT USE FOR: installing or changing presets/extensions (use speckit-preset or speckit-extension), resolving only a preset-managed filename (use speckit-preset), or running an artifact.
speckit-bundleDiscover, install, and author Spec Kit bundles via `specify bundle`. USE FOR: searching/showing/listing bundles, installing/updating/removing a bundle (a curated set of extensions/presets/integrations/workflows), validating a bundle manifest, building a distributable bundle artifact, initializing a project and installing a bundle, managing bundle catalog sources. DO NOT USE FOR: individual extensions/presets/integrations/workflows (use their respective skills).
speckit-checkCheck the local environment for Spec Kit by running `specify check` (and `specify version`). USE FOR: verifying required tools are installed, diagnosing a broken spec-kit setup, reporting CLI version/feature capabilities. DO NOT USE FOR: installing or upgrading the CLI itself (use the speckit-self skill).
speckit-cli-setupDetect and install the Spec Kit `specify` CLI that every other speckit skill depends on. USE FOR: checking whether `specify` is installed/on PATH, installing it when missing, fixing "command not found: specify", confirming the CLI is new enough (>= 0.11). DO NOT USE FOR: upgrading an already-installed CLI to a newer release (use speckit-self) or verifying project tools (use speckit-check).
speckit-extensionManage Spec Kit extensions via `specify extension`. USE FOR: listing installed extensions as text or JSON, installing/removing/updating extensions, searching the extension catalog, showing extension info, enabling/disabling extensions, setting resolution priority, or managing extension catalogs. DO NOT USE FOR: artifact composition stacks (use speckit-artifact), presets (use speckit-preset), bundles (use speckit-bundle), or workflows (use speckit-workflow).
speckit-initScaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running `specify init --integration copilot --integration-options="--skills"`. USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO NOT USE FOR: managing extensions/presets/bundles of an already-initialized project (use the speckit-extension / speckit-preset / speckit-bundle skills instead).
speckit-presetManage Spec Kit presets via `specify preset`. USE FOR: listing installed presets as text or JSON, installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling presets, setting resolution priority, or managing preset catalogs. DO NOT USE FOR: full artifact composition stacks (use speckit-artifact), extensions (use speckit-extension), bundles (use speckit-bundle), or workflows (use speckit-workflow).
speckit-selfCheck for and apply Spec Kit CLI updates via `specify self`. USE FOR: checking whether a newer specify-cli release is available, previewing an upgrade with --dry-run, upgrading the CLI in place (optionally to a pinned tag). DO NOT USE FOR: checking project tools/integrations (use speckit-check) or managing extensions/presets/integrations/workflows.
speckit-workflow-stepManage Spec Kit workflow step types via `specify workflow step`. USE FOR: listing built-in and custom workflow step types, installing/removing a custom step type from a catalog, searching/showing step-type info, managing step-type catalog sources. DO NOT USE FOR: running or installing whole workflows (use speckit-workflow), or bundles (use speckit-bundle).