Skip to content
cccskills
FreePublished on GitHub

speckit-workflow-step

Manage 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).

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md1.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Spec Kit — workflow step types

Manage the step types that workflows are composed of, using the Specify CLI specify workflow step command group. (Requires Specify CLI >= 0.11.)

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

When to use

  • Inspect which step types (built-in or custom) are available to workflows.
  • Install or remove a custom step type, or manage step-type catalog sources.

How to invoke

# Discover step types
specify workflow step list
specify workflow step search <query>
specify workflow step info <step-id>

# Install / remove custom step types
specify workflow step add <step-id>            # from the step catalog
specify workflow step remove <step-id>

# Manage step catalog sources
specify workflow step catalog list
specify workflow step catalog add <url>
specify workflow step catalog remove <index>   # by index

Notes

  • Step types are the building blocks referenced by workflow YAML; install the step types a workflow needs before running it (see the speckit-workflow skill).
  • list shows both built-in and custom step types; only custom ones can be removed.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Inspect 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.

The English summary is being prepared. Showing the original description.

github/spec-kit-copilot18Updated Oct 6, 2026

Discover, 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).

The English summary is being prepared. Showing the original description.

github/spec-kit-copilot18Updated Oct 6, 2026

Check 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).

The English summary is being prepared. Showing the original description.

github/spec-kit-copilot18Updated Oct 6, 2026

Detect 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).

The English summary is being prepared. Showing the original description.

github/spec-kit-copilot18Updated Oct 6, 2026

Manage 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).

The English summary is being prepared. Showing the original description.

github/spec-kit-copilot18Updated Oct 6, 2026

Scaffold 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).

The English summary is being prepared. Showing the original description.

github/spec-kit-copilot18Updated Oct 6, 2026

See all skills by github

Report a problem with this skill