chengjingtao contributor

Opsx Ext

Install when you use OpenSpec and need skills that break a large epic into discrete OpenSpec change proposals before implementation.

Overview

opsx-ext is a plugin marketplace for the Validate phase that bundles OpenSpec extension skills to decompose epics into openspec changes.

What is this marketplace?

  • 1-plugin marketplace (skills) with opsx-epic and opsx-ext OpenSpec extension skills
  • Designed to break down epics into openspec changes for incremental delivery
  • OpenSpec Extension metadata v0.0.1 from chengjingtao
  • Non-strict plugin loading for flexible skill paths
  • Planning/spec marketplace rather than code generators
  • 1 plugins in marketplace listing
  • 2 skills referenced: opsx-epic, opsx-ext
  • Metadata version 0.0.1

Compatible agents: Claude Code, Cursor, Codex

What problem does it solve?

Fat epics stall shipping because you lack a consistent way to split them into OpenSpec-sized changes the agent and team can execute in order.

Who is it for?

Builders using OpenSpec who want Claude to help slice epics into incremental change specs during planning.

Skip if: Teams with no OpenSpec workflow who only want inline code completion without specification artifacts.

What do I get? / Deliverables

After install, you can invoke opsx-epic and opsx-ext to produce structured OpenSpec change breakdowns from epics before build.

  • Configured skills plugin with opsx-epic and opsx-ext
  • Epic broken into OpenSpec-oriented change outlines
  • Clearer incremental scope before build kickoff

Plugins in this marketplace

1 plugin — install individually after you add the marketplace.

Recommended Marketplaces

Journey fit

Primary fit

Epic-to-change decomposition happens while scoping what to build and how to slice releases, which is the validate phase before heavy build work. opsx-epic and opsx-ext skills explicitly target breaking epics into OpenSpec changes, which is scope definition and specification shaping.

How it compares

OpenSpec planning marketplace, not an MCP integration or production monitoring pack.

Common Questions / FAQ

Who is Opsx Ext for?

It is for solo builders and small teams practicing OpenSpec who need agent skills to turn epics into discrete change proposals.

When should I use Opsx Ext?

Use it during validate when scoping a feature epic and you need OpenSpec-aligned change splits before implementation starts.

How do I add Opsx Ext to my agent?

Add the chengjingtao/openspec-ext marketplace in Claude Code, enable the skills plugin, and run opsx-epic or Opsx Ext against your epic descriptions in OpenSpec.

This week for builders

Five minutes, every Monday — the tools, releases and tactics for shipping solo.

unsubscribe anytime.