New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Speckit Opsmill Auto

by opsmill in opsmill/infrahub

Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously.

Apache-2.0Auto-check passedDevelopment

Install Speckit Opsmill Auto

skills CLI
$ npx skills add opsmill/infrahub --skill speckit-opsmill-auto -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install opsmill/infrahub speckit-opsmill-auto --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/opsmill/infrahub.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/speckit-opsmill-auto .claude/skills/speckit-opsmill-auto && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
speckit-opsmill-auto
GitHub stars
531
Token cost
~1.1k tokens
SKILL.md length
571 words
Files
1
Skills in repo
32
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously.

  • Tasks that involve Spec-driven development
  • SKILL.md covers User Input, Outline and Completion
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Speckit Opsmill Auto is an agent skill from opsmill/infrahub. Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Stops before extract; run that manually.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires spec-kit project structure with .specify/ directory

It sits in Development, covering Spec-driven development. The repository describes itself as: Infrahub is a graph-based data management platform with built-in version control, CI workflows, peer review, and API access. It’s purpose-built to power reliable infrastructure… The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Spec-driven development

Example prompts

  • “/speckit-opsmill-auto”

Requirements

  • Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory

What it can do on your machine

Read from SKILL.md and the folder at commit 460d724. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

  • Compatibility

    Requires spec-kit project structure with .specify/ directory

    From compatibility in the SKILL.md frontmatter.

Context cost

Speckit Opsmill Auto loads about 1.1k tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 571 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~48
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from opsmill/infrahub at commit 460d724, republished under its Apache-2.0 licence (© opsmill). 571 words, ~1,143 tokens.

Download SKILL.mdSave it as .claude/skills/speckit-opsmill-auto/SKILL.md (or your agent's skills folder).
name
speckit-opsmill-auto
description
Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Stops before extract; run that manually.
compatibility
Requires spec-kit project structure with .specify/ directory
metadata.author
github-spec-kit
metadata.source
opsmill:commands/auto.md

User Input

text
$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Outline

You are running the full speckit pipeline end-to-end. The user's input (above) is the feature description that will seed the specification phase.

This skill is a thin orchestrator over two sibling skills:

  • speckit-opsmill-prep — Specify → Plan → Critique → Tasks (+ spec/ask alignment check)
  • speckit-opsmill-implement — Implement → Review → Final report

Run them back-to-back, making all decisions autonomously. Do not stop to ask the user for input between phases — if a sub-phase requires choices (clarification questions in specify, research decisions in plan, drift remediation in alignment), use your best judgment and proceed. The user expects a hands-off, one-shot execution. Extraction (speckit-opsmill-extract) is not run by this command — the user invokes it manually after reviewing the implementation report.

Each phase below is executed by invoking the named skill (e.g. via the agent's Skill tool). Skills are agent-agnostic, so this workflow runs identically across any harness that supports skill discovery — not only those exposing speckit slash commands.

Phase A — Preparation (delegated to speckit-opsmill-prep)

Invoke the speckit-opsmill-prep skill with the user's feature description ($ARGUMENTS) verbatim.

  • This covers Specify → Plan → Critique → Tasks and the trailing spec/ask alignment check.
  • The sub-skill commits its own artifacts after each phase via speckit-checkpoint-commit.
  • If the alignment check inside prep loops (re-running plan/critique/tasks to fix spec drift), let it run to completion. Do not interfere.

Read prep's status line. speckit-opsmill-prep ends its output with a literal final line:

STATUS: <READY|BLOCKED> | SPEC_DIR: <absolute spec-dir path> | REASON: <...>

Parse that line — do not infer success from the prose summary:

  • Take SPEC_DIR from this line as the spec directory to pass to Phase B. This is the deterministic hand-off; do not scrape the path out of free text.
  • If STATUS: BLOCKED (e.g., alignment never converged within its retry budget, or a phase could not complete), surface the reason to the user and stop. Do not proceed to implementation on a misaligned or incomplete spec.
  • Only proceed to Phase B when STATUS: READY.
Show full SKILL.md (244 more words)Show less
Phase B — Implementation tail (delegated to speckit-opsmill-implement)

Invoke the speckit-opsmill-implement skill with the SPEC_DIR path from Phase A as its argument. Because you pass an explicit spec-dir path, the sub-skill runs in autonomous-parent mode: its Phase 0 stop-conditions abort with a STATUS: BLOCKED line instead of pausing for a user.

  • This covers Phase 0 (Preflight) → Phase 5 (Implement loop in clean-context subagents) → Phase 6 (Review) → Phase 7 (Final report).
  • The sub-skill writes <spec-dir>/opsmill-implement-report.md and commits it.

Read implement's status line. speckit-opsmill-implement ends its output with a literal final line:

STATUS: <DONE|INCOMPLETE|BLOCKED> | SPEC_DIR: <...> | REASON: <...>

  • STATUS: BLOCKED — a Phase 0 stop-condition aborted before any implementation (no report written). Surface the reason in the final summary; do not retry from this orchestrator.
  • STATUS: INCOMPLETE — blocked tasks or missing local-pass evidence; capture that for the final summary. The user decides whether to re-run.
  • STATUS: DONE — all chunks completed with evidence.

In every case, do not retry from this orchestrator.

Completion

After both phases are complete, provide a brief summary:

  • Feature name and spec directory
  • Whether the alignment check inside auto-prep required retries (and how many)
  • Number of tasks completed (from the auto-implement report)
  • Any review findings that were fixed inline vs. deferred
  • Any notable decisions you or the sub-skills made autonomously

Do not open a PR, push, run extraction, or start a new feature. The user takes it from there — extraction (/speckit.opsmill.extract) is intentionally left as a manual follow-up so the user can review the implementation report first.

© opsmill, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/speckit-opsmill-auto of opsmill/infrahub.

Open the folder on GitHubat commit 460d724

Compare with similar skills

Speckit Opsmill Auto next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Speckit Opsmill Auto compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Speckit Opsmill Auto this skillopsmill/infrahub531—~1.1kAutomated safety check: PassApache-2.0
OpenSpec Bulk Change ArchiverFission-AI/OpenSpec71k3 repos~5.6kAutomated safety check: PassMIT
Speckit ConstitutionWeihanLi/WeihanLi.Common24211 repos~2.1kAutomated safety check: PassApache-2.0
Speckit Taskstoissueskunstmusik/blue15419 repos~2kAutomated safety check: PassGPL-3.0
Speckit Analyzekunstmusik/blue15418 repos~3kAutomated safety check: PassGPL-3.0
Review Spdzhu1090093659/spec_driven_develop984—~1.5kAutomated safety check: PassMIT

Similar skills

  • OpenSpec Bulk Change Archiver

    Fission-AI/OpenSpec

    Archives several completed OpenSpec changes in one operation, checking the codebase to resolve spec conflicts rather than archiving blindly.

    71k GitHub starsUsed in 3 repos~5.6k tokens
    DevelopmentAuto-check passed

  • Speckit Constitution

    WeihanLi/WeihanLi.Common

    Create or update the project constitution from interactive or provided principle inputs, ensuring all dependent templates stay in sync.

    242 GitHub starsUsed in 11 repos~2.1k tokens
    DevelopmentAuto-check passed

  • Speckit Taskstoissues

    kunstmusik/blue

    Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.

    154 GitHub starsUsed in 19 repos~2k tokens
    DevelopmentAuto-check passed

  • Speckit Analyze

    kunstmusik/blue

    Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.

    154 GitHub starsUsed in 18 repos~3k tokens
    DevelopmentAuto-check passed

  • Review Spd

    zhu1090093659/spec_driven_develop

    Findings-first code review workflow for AI coding agents. An agent skill from zhu1090093659/spec_driven_develop.

    984 GitHub stars~1.5k tokensUpdated 2 mo ago
    DevelopmentAuto-check passed

  • Speckit Plan

    kunstmusik/blue

    Execute the implementation planning workflow using the plan template to generate design artifacts.

    154 GitHub starsUsed in 18 repos~2.1k tokens
    DevelopmentAuto-check passed

More from opsmill/infrahub

All 32 skills in this repo

  • Analyzing CI Flakiness

    opsmill/infrahub

    Analyzes recent CI failures on pull requests to identify flaky tests, using retry outcomes (failed attempt → green re-run) and cross-PR recurrence as evidence, and maintains a local longitudinal…

    531 GitHub stars~2k tokensUpdated today
    Auto-check passed

  • Audit Docs

    opsmill/infrahub

    Audits internal (dev/) and external (docs/) documentation completeness for a feature, subject, or set of existing docs, maps changes indicated by the user, across Infrahub's documentation layers…

    531 GitHub stars~1.5k tokensUpdated today
    Auto-check passed

  • Commit

    opsmill/infrahub

    Stages and commits the current changes onto a safe working branch, enforcing branch discipline and optionally pushing upstream.

    531 GitHub stars~2.8k tokensUpdated today
    Auto-check: notes

  • Creating Changelog Entries

    opsmill/infrahub

    A skill your agent uses when you've fixed a bug, added a feature, or made any user-facing change in a project that uses Towncrier and need to record it for the changelog — before committing or…

    531 GitHub stars~1.9k tokensUpdated today
    Auto-check passed

  • Creating Issues

    opsmill/infrahub

    Turns a single feature idea, improvement, or bug into ONE well-structured GitHub issue.

    531 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • Creating Prd

    opsmill/infrahub

    Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue).

    531 GitHub stars~4k tokensUpdated today
    Auto-check passed

Categories

Questions about Speckit Opsmill Auto

What does Speckit Opsmill Auto do?

Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously. Speckit Opsmill Auto is an agent skill from opsmill/infrahub. Run the full speckit workflow end-to-end — specify, plan, critique, tasks, implement, review — making all decisions autonomously.

When should I use Speckit Opsmill Auto?

Speckit Opsmill Auto fits situations like: tasks that involve Spec-driven development.

How do I install Speckit Opsmill Auto in Claude Code?

Run `npx skills add opsmill/infrahub --skill speckit-opsmill-auto -a claude-code`. Or copy the skill folder (.agents/skills/speckit-opsmill-auto in opsmill/infrahub) into .claude/skills/speckit-opsmill-auto in your project. Claude Code loads it when a task matches its description.

How do I install Speckit Opsmill Auto in Codex?

Run `npx skills add opsmill/infrahub --skill speckit-opsmill-auto -a codex`. Or copy the skill folder (.agents/skills/speckit-opsmill-auto in opsmill/infrahub) into .agents/skills/speckit-opsmill-auto in your project. Codex loads it when a task matches its description.

Can I use Speckit Opsmill Auto in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add opsmill/infrahub --skill speckit-opsmill-auto -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/speckit-opsmill-auto, .gemini/skills/speckit-opsmill-auto, .github/skills/speckit-opsmill-auto and .opencode/skills/speckit-opsmill-auto in your project.

What does Speckit Opsmill Auto need to run?

SKILL.md names no scripts, command-line tools or credentials: Speckit Opsmill Auto is instructions for the agent only. Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory.

Does Speckit Opsmill Auto access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Speckit Opsmill Auto safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Speckit Opsmill Auto use?

Speckit Opsmill Auto is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Speckit Opsmill Auto use?

About 1.1k tokens (SKILL.md is roughly 4.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Speckit Opsmill Auto?

Skills that share tags, products or a category with Speckit Opsmill Auto: OpenSpec Bulk Change Archiver (Fission-AI/OpenSpec, 71k stars), Speckit Constitution (WeihanLi/WeihanLi.Common, 242 stars), Speckit Taskstoissues (kunstmusik/blue, 154 stars) and Speckit Analyze (kunstmusik/blue, 154 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Speckit Opsmill Auto?

opsmill (a GitHub organization) maintains it in opsmill/infrahub, which has 531 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 8, 2026.

Source: opsmill/infrahub on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.