What is opsx-development-workflow?

A guided development process that takes a software change from exploration and written requirements through planning, implementation, testing, archiving, and branch completion. It uses OpenSpec for change specifications and Superpowers for development support.

Use it for feature work or other changes that need a complete, repeatable process with explicit checkpoints.

It prevents important stages such as planning, verification, or documenting the finished change from being skipped.

opsx-development-workflow — Skill by kehanzzz

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/kehanzzz/opsx-dev-workflow/skill

Any agent

npx skills add kehanzzz/opsx-dev-workflow --skill skill

Clone the repo

git clone --depth 1 https://github.com/kehanzzz/opsx-dev-workflow

Made for: Claude Code, Codex.

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,981 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00040	$0.03981
Opus 5	$0.00020	$0.01990
Sonnet 5	$0.00008	$0.00796
Haiku 4.5	$0.00004	$0.00398

Measured 2d ago against content hash 47ce6c0fad1d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

opsx-development-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

The scan reads SKILL.md. This mod also ships 37 executable files (scripts/advance-phase.sh, scripts/append-audit-log.sh, scripts/check-workflow-state.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skill/SKILL.md · 391 lines

How it starts

The opening of the file, as written. The whole thing — 391 lines — stays where its author put it; the contents beside it link to each section on GitHub.

OpsX Development Workflow

Overview

Drive development through fixed gates: clarify, create the change and spec, write a plan, execute, verify, archive, and finish.

Start by stating: I am using the opsx-development-workflow skill to drive this end-to-end development workflow.

When to Use

The task must go through the full change / spec / verification / archive loop.
You need to use both OpenSpec and superpowers in the same workflow.
You do not want to skip the planning, verification, or branch finish gates.

Do not use this skill for:

Conversations that only answer questions without producing a tangible implementation.
One-off edits unrelated to the OpsX change workflow.

Preconditions

Required OpenSpec skills: openspec-propose, openspec-verify-change, and openspec-archive-change.
Optional OpenSpec skills: openspec-explore, openspec-new-change, openspec-continue-change, openspec-ff-change, openspec-apply-change, and openspec-sync-specs.
These OpenSpec skills still rely on the upstream openspec CLI under the hood; follow the host's current OpenSpec distribution instead of pinning this repository to older aliases.
Required superpowers skills: superpowers:writing-plans, superpowers:finishing-a-development-branch.
Recommended capability: superpowers:subagent-driven-development. If a subagent is unavailable, the external execution branch described in step 5 is still an option.
Treat superpowers:test-driven-development as a mandatory implementation discipline.
If a required skill is missing, stop immediately and report rather than silently skipping process steps.

Workflow

After creating or selecting a change through openspec-propose or the optional openspec-new-change path, read session-bootstrap.md. It reanchors the current session to the external state stored in the change directory, preventing you from relying solely on conversational memory. It is normal for the pre-change exploration phase to have no workflow-state yet.

Read the full file on GitHub · 391 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 391 lines · 40 tokens per session scan A 47ce6c0fad1d

Subscribe to this mod's changes

opsx-development-workflow is a skill published in the GitHub repository kehanzzz/opsx-dev-workflow (2 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 3,981 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning agent-workflow ai-agent claude-code codex developer-tools gemini-cli

gcloud-usage

This skill should be used when user asks about "GCloud logs", "Cloud Logging queries", "Google Cloud metrics", "GCP observability", "trace analysis", or "debugging production issues on GCP".

fcakyon/claude-codex-settings · 49 tokens

review

5-pass structured code review — correctness, security, performance, readability, consistency.

SethGammon/Citadel · 17 tokens

scaffold

Project-aware file generation. Reads existing codebase conventions (naming, structure, imports, exports, test patterns) then generates new files that match exactly. Wires generated files into the project's registration points.

SethGammon/Citadel · 44 tokens

marshal

Meta-orchestrator that takes any direction — broad, specific, or vague — and autonomously chains skills and context into actionable work. Gathers context from codebase, docs, and memory. Only asks the user when it genuinely cannot proceed. Single-session orchestrator.

SethGammon/Citadel · 56 tokens

organize

Repository structure only: directory layout, file placement, naming conventions, and where-does-this-belong decisions. Detects the project's convention, audits files against it, and executes move plans with import-path updates. Never changes code inside files beyond the import updates a move forces; in-file…

SethGammon/Citadel · 66 tokens

postmortem

Auto-generates a structured postmortem from a completed campaign. Reads the campaign file, telemetry logs, and feature ledger. Produces a documented analysis of what broke, what the safety systems caught, and what patterns emerged. Can also be invoked manually for any incident.

SethGammon/Citadel · 58 tokens