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 Retrospect

by opsmill in opsmill/infrahub

Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.

Apache-2.0Auto-check passedProduct & Project Management

Install Speckit Opsmill Retrospect

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

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

GitHub CLI
$ gh skill install opsmill/infrahub speckit-opsmill-retrospect --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-retrospect .claude/skills/speckit-opsmill-retrospect && 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-retrospect
GitHub stars
533
Token cost
~2.3k tokens
SKILL.md length
1,046 words
Files
1
Skills in repo
32
Repo updated
First seen
Licence
Apache-2.0

At a glance

Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.

  • Works in 6 steps: Resolve Session Context → Identify Findings → Assign Dispositions → …
  • Tasks that involve Spec-driven development
  • SKILL.md covers User Input, Outline, Operating Constraints and Phase 1: Resolve Session Context, plus 6 more sections
  • Calls git and gh

What it does

Speckit Opsmill Retrospect is an agent skill from opsmill/infrahub. Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.

Its SKILL.md is about 2.3k 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 Product & Project Management, covering Spec-driven development, Retrospectives and Context engineering. It works with GitHub. 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
  • Tasks that involve Retrospectives
  • Tasks that involve Context engineering

Example prompts

  • “/speckit-opsmill-retrospect”

Requirements

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

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Resolve Session Context
  2. Identify Findings
  3. Assign Dispositions
  4. Produce Review Report
  5. Save Report
  6. Execute Approved Dispositions

What it can do on your machine

Read from SKILL.md and the folder at commit 2e1f1eb. 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

    Shell commands in SKILL.md call:

    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    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 Retrospect loads about 2.3k tokens when it runs. Until then it costs about 35 tokens; SKILL.md has 1,046 words of instructions outside code blocks.

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

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 2e1f1eb, republished under its Apache-2.0 licence (© opsmill). 1,046 words, ~2,266 tokens.

Download SKILL.mdSave it as .claude/skills/speckit-opsmill-retrospect/SKILL.md (or your agent's skills folder).
name
speckit-opsmill-retrospect
description
Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.
compatibility
Requires spec-kit project structure with .specify/ directory
metadata.author
github-spec-kit
metadata.source
opsmill:commands/retrospect.md

User Input

text
$ARGUMENTS

You MUST consider the user input before proceeding (if not empty). Treat it as optional scope guidance, such as a focus area, a pasted transcript summary, or a preferred disposition.

Outline

Run a retrospective on the current agent session while the work is still fresh in context. The goal is to identify concrete improvements to the repository's context-management surface area: AGENTS.md, CLAUDE.md, .claude/settings.json, .agents/skills/, .agents/commands/, .specify/templates/, dev/knowledge/, dev/guides/, dev/guidelines/, dev/adr/, and product or architecture decisions that caused avoidable friction.

This command closes the loop from "the agent struggled with X" to "X is captured as an approved repo improvement, dedicated PR, GitHub issue, or local-only note."

Operating Constraints

  • Stay read-only until the user approves the report and any disposition buckets. Do not edit files, commit, push, or create GitHub issues before approval.
  • Present the full retrospective before taking action. Ask for explicit approval per disposition bucket: fix-now, open-pr, github-issue, and local-only.
  • For fix-now, present a diff preview or precise patch plan before writing files. Apply only the approved changes.
  • For github-issue, defer to the existing creating-issues skill when available; if it is unavailable, use gh issue create only after the user approves the exact issue content.
  • Respect AGENTS.md guardrails. Ask First topics, including database migrations, GraphQL schema changes, new dependencies, CI/CD workflow changes, and authentication or authorization changes, are never auto-applied. Route them to open-pr or github-issue.
  • Never edit generated files. If a finding points at generated output, identify the source template or generator instead.
  • Do not treat personal preferences as repo policy. Use local-only for non-project-specific workflow preferences.

Phase 1: Resolve Session Context

  1. Identify the repository root and current branch:
    • Run git rev-parse --show-toplevel.
    • Run git branch --show-current.
    • Run git status --short to understand whether there are existing edits.
  2. Determine whether the session is inside an active spec-kit feature:
    • Try .specify/scripts/bash/check-prerequisites.sh --json --paths-only.
    • If it succeeds, record FEATURE_DIR and use FEATURE_DIR/retrospective.md as the report path.
    • If it fails or the project is not on a spec-kit feature branch, continue as an ad-hoc session and use .claude/retrospectives/YYYYMMDD-HHMMSS-<short-branch-or-session-slug>.md as the report path.
  3. Load only the context needed to classify findings:
    • Root AGENTS.md and any area-specific AGENTS.md touched this session.
    • CLAUDE.md and .claude/settings.json if present.
    • Relevant skill prompts in .agents/skills/ and commands in .agents/commands/.
    • Relevant spec-kit templates in .specify/templates/.
    • Relevant dev/knowledge/, dev/guides/, dev/guidelines/, or dev/adr/ pages.
    • Current diff and recent commands from the conversation context.

Phase 2: Identify Findings

Review the current conversation and repository context for friction that was avoidable through better shared context. Organize findings into exactly these categories:

  1. Instructions / Configuration Gaps
    • Missing, unclear, duplicated, or contradictory guidance in AGENTS.md, CLAUDE.md, .claude/settings.json, skill prompts, commands, or spec-kit templates.
    • Required repo workflows that the agent had to infer or rediscover.
  2. Documentation Gaps
    • Missing or stale content in dev/knowledge/, dev/guides/, dev/guidelines/, or dev/adr/.
    • Docs that contradicted current code or left out required verification steps.
  3. Architectural Friction
    • Product, architecture, or code choices that forced repeated workarounds.
    • Candidates for ADRs, refactors, or product follow-up.
  4. Mistakes & Corrections
    • Wrong turns taken during the session.
    • The guardrail, instruction, template change, or test that would have prevented the mistake.

Prefer concrete findings over broad observations. Each finding must cite the session event or repository location that motivated it.

Show full SKILL.md (507 more words)Show less

Phase 3: Assign Dispositions

For each finding, propose one disposition:

DispositionUse WhenAction After Approval
fix-nowSmall, low-risk repo context updates that belong on the current branch and do not touch Ask First topics.Show diff preview, then edit files only after approval.
open-prContext or harness changes that should be reviewed separately from the current feature branch, or anything touching Ask First topics.Draft a branch/PR plan. Do not branch, commit, push, or open a PR unless explicitly approved.
github-issueLarger work, ambiguous ownership, product/architecture debt, ADR candidates needing human authorship, or work outside current scope.Use the creating-issues skill to draft each issue; create only after approval.
local-onlyPersonal workflow preferences or notes that should not become repo policy.Record only in approved local .specify/memory/report locations supported by the runtime.

Disposition rules:

  • If a finding involves database schema or migration changes, GraphQL schema changes, new dependencies, CI/CD workflows, authentication, authorization, or generated files, do not assign fix-now.
  • If a finding needs product or architecture ownership, prefer github-issue unless the user explicitly asks for a dedicated PR.
  • If a finding is already fully covered by existing docs or instructions, do not include it as a finding; mention it only in a brief "No action" note if helpful.

Phase 4: Produce Review Report

Before writing any files, present the retrospective in chat using this structure:

markdown
## Session Retrospective

**Scope**: <current feature, branch, or ad-hoc session>
**Proposed report path**: <path>

### Findings

| ID | Category | Evidence | Improvement | Disposition |
|----|----------|----------|-------------|-------------|
| R1 | Instructions / Configuration Gaps | <specific session event or file path> | <concrete change> | fix-now |

### Disposition Buckets

#### fix-now

- R1: <target file and change summary>

#### open-pr

- R2: <branch or PR scope>

#### github-issue

- R3: <issue title>

#### local-only

- R4: <memory/report note>

### Approval Request

Reply with one or more approved buckets, for example:

- `approve report only`
- `approve fix-now`
- `approve github-issue R3`
- `approve all except open-pr`

The report must include concrete findings in all four categories. If a category genuinely has no findings, include the category with None found and a one-sentence reason.

Phase 5: Save Report

Save the retrospective report only after the user approves report only, a disposition bucket, or all.

Report path:

  • Active spec-kit feature: specs/<current-feature>/retrospective.md.
  • Ad-hoc session: .claude/retrospectives/YYYYMMDD-HHMMSS-<short-branch-or-session-slug>.md.

If the report path already exists, append a numeric suffix rather than overwriting it.

Phase 6: Execute Approved Dispositions

Process only the buckets the user approved.

fix-now
  1. Show a diff preview or exact patch plan for the approved findings.
  2. Wait for confirmation if the preview changes the original scope.
  3. Apply edits with normal repository editing rules.
  4. Run relevant validation. For prompt, command, and Markdown-only changes, at minimum verify paths exist and the command can be discovered from the extension manifest and runtime command file. Run broader lint or tests when touched files are covered by existing automation.
open-pr
  1. Draft the proposed branch name, PR title, PR body summary, and changed file list.
  2. Ask for explicit approval before creating a branch, committing, pushing, or opening a PR.
  3. If approved, use the repository's normal PR workflow.
github-issue
  1. For each approved finding, invoke the creating-issues skill with the finding as source material.
  2. Present the exact issue title/body/labels for approval.
  3. Create issues only after approval.
local-only
  1. Record the note only in runtime-supported local memory or in the approved retrospective report.
  2. Do not add local-only preferences to repo files unless the user explicitly reclassifies them as repo policy.

Completion

After approved actions are complete, provide a brief summary:

  • Report path
  • Actions taken
  • Validation run
  • Any remaining unapproved buckets

© 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-retrospect of opsmill/infrahub.

Open the folder on GitHubat commit 2e1f1eb

Compare with similar skills

Speckit Opsmill Retrospect 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 Retrospect compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Speckit Opsmill Retrospect this skillopsmill/infrahub533—~2.3kAutomated safety check: PassApache-2.0
CCPM Project Managementautomazeio/ccpm8.4k—~1.1kAutomated safety check: PassMIT
Badstephenleo/bmad-autonomous-development107—~7.7kAutomated safety check: PassMIT
PRP PlanWirasm/prp2.3k—~4kAutomated safety check: PassMIT
Sagawarpdotdev/common-skills611—~4.1kAutomated safety check: PassMIT
Retrokoolamusic/claudefiles130—~2.8kAutomated safety check: PassMIT

Similar skills

  • CCPM Project Management

    automazeio/ccpm

    Runs a spec-driven workflow from PRD to epic to GitHub issues to parallel agents, with status, standup and blocked-work reports from bundled scripts.

    8.4k GitHub stars~1.1k tokensUpdated 6 mo ago
    Product & Project ManagementAuto-check passed

  • Bad

    stephenleo/bmad-autonomous-development

    BMad Autonomous Development — orchestrates parallel story implementation pipelines.

    107 GitHub stars~7.7k tokensUpdated 5 mo ago
    Agent WorkflowsAuto-check passed

  • PRP Plan

    Wirasm/prp

    Writes an implementation-ready plan for a feature, bug fix, refactor or chore from a PRD, issue or description, grounded in codebase evidence, and can post it back to the source issue.

    2.3k GitHub stars~4k tokensUpdated 7 days ago
    DevelopmentAuto-check passed

  • Saga

    warpdotdev/common-skills

    Run an autonomous, spec-driven development "saga" for medium-to-large features using an orchestrator agent and a fleet of worker subagents.

    611 GitHub stars~4.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

  • Retro

    koolamusic/claudefiles

    A skill your agent uses when a user completes a phase, sprint, milestone, or meaningful unit of work and needs a retrospective.

    130 GitHub stars~2.8k tokensUpdated today
    Product & Project ManagementAuto-check passed

  • Spec Writer

    garrytan/gstack

    Converts a vague idea into a precise, executable spec in five phases, files it as an issue and can start an agent on it in a fresh worktree.

    136k GitHub stars~14k tokensUpdated today
    DevelopmentAuto-check: notes

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…

    533 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…

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

    533 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…

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

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

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

Works with

Categories

Questions about Speckit Opsmill Retrospect

What does Speckit Opsmill Retrospect do?

Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions. Speckit Opsmill Retrospect is an agent skill from opsmill/infrahub. Run a session retrospective that surfaces context-management gaps and routes them to approved follow-up actions.

When should I use Speckit Opsmill Retrospect?

Speckit Opsmill Retrospect fits situations like: tasks that involve Spec-driven development; tasks that involve Retrospectives; tasks that involve Context engineering.

How do I install Speckit Opsmill Retrospect in Claude Code?

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

How do I install Speckit Opsmill Retrospect in Codex?

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

Can I use Speckit Opsmill Retrospect 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-retrospect -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-retrospect, .gemini/skills/speckit-opsmill-retrospect, .github/skills/speckit-opsmill-retrospect and .opencode/skills/speckit-opsmill-retrospect in your project.

What does Speckit Opsmill Retrospect need to run?

Going by SKILL.md and its folder, Speckit Opsmill Retrospect needs the command-line tools its instructions call (git and gh). Compatibility (from SKILL.md): Requires spec-kit project structure with .specify/ directory.

Does Speckit Opsmill Retrospect access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Speckit Opsmill Retrospect 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 Retrospect use?

Speckit Opsmill Retrospect 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 Retrospect use?

About 2.3k tokens (SKILL.md is roughly 9.1k 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 Retrospect?

Skills that share tags, products or a category with Speckit Opsmill Retrospect: CCPM Project Management (automazeio/ccpm, 8.4k stars), Bad (stephenleo/bmad-autonomous-development, 107 stars), PRP Plan (Wirasm/prp, 2.3k stars) and Saga (warpdotdev/common-skills, 611 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Speckit Opsmill Retrospect?

opsmill (a GitHub organization) maintains it in opsmill/infrahub, which has 533 GitHub stars. The repository holds 32 skills in this directory. The repository was last updated on October 9, 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.