Skip to content
cccskills
FreePublished on GitHub

speckit-artifact

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-copilot
See how to install

Files included (1)

  • SKILL.md3.0 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Spec Kit — artifacts

Inspect commands, templates, scripts, hooks, and their effective composition stacks with the Specify CLI specify artifact command group. Requires Specify CLI >= 1.0.7.

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

When to use

  • List every command, template, script, and hook visible to a Spec Kit project.
  • Explain which project, preset, extension, or built-in layer supplies an artifact.
  • Inspect precedence, composition strategy, active layers, and hidden layers.
  • Check whether declared hooks are registered and active.
  • Resolve a stack entry back to the validated manifest contribution Spec Kit uses.

How to invoke

# Full artifact inventory, including composition stacks
specify artifact list --json

# Inspect one artifact by bare name or source-agnostic artifact id
specify artifact info <name> --json
specify artifact info <kind>:<name> --json
specify artifact info <name> --kind <command|template|script|hook> --json

# Resolve a manifest-backed stack layer to its effective contribution
specify artifact lookup <lookupId> --json

Identifiers

  • An artifact id has the form <kind>:<name>, such as command:speckit.specify. Pass this value to specify artifact info.
  • A stack entry's lookupId identifies the preset or extension contribution behind that layer. Pass this opaque value unchanged to specify artifact lookup.
  • Built-in layers do not have a lookupId. Project or convention-only layers may not have a manifest contribution that lookup can resolve.

Notes

  • All specify artifact subcommands are read-only.
  • --json is currently required. A missing --json is a usage error.
  • Run commands from an initialized Spec Kit project containing .specify/.
  • list and info return ordered stacks. For commands, templates, and scripts, index 0 is the winning layer. Hook stacks are additive, so multiple entries can be active.
  • Composition strategies are replace, wrap, prepend, append, and additive for hooks.
  • active and hidden are independent: an inactive layer can still participate in composed output unless a higher replace layer hides it.
  • Hook artifact ids percent-encode event and target-command components. Reuse ids and lookupIds exactly as returned instead of constructing them manually.

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

speckit-bundle

Free

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

speckit-check

Free

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

speckit-cli-setup

Free

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

speckit-extension

Free

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

speckit-init

Free

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

speckit-preset

Free

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

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