Claude Plugin

Codex & Claude Plugin

Personal [Claude Code](https://claude.com/claude-code) and Codex plugins.

Install

Claude Code

/plugin marketplace add kardebadas/claude-plugin
/plugin install superb@kardebadas-claude-plugin

Codex

Add the repository's local marketplace, then install `superb` from it:

codex plugin marketplace add /path/to/claude-plugin
codex plugin add superb@personal

The `superb` namespace

One plugin, many skills. The prefix comes from the plugin name, so every skill inside it is invoked as `superb:`:

Skill	Invoke as	What it is
`craft`	superb:craft	Turns a vague product idea into a clear definition of what to build. Puts a questionnaire tailored to the product in front of you — in a local browser UI, or in CRAFT.md — which you answer in your own time; each pass folds your answers in, records confirmed decisions, surfaces assumptions and contradictions, and gets shorter. Deliberately stops before planning — no tasks, no phases, no code.
`pipeline`	superb:pipeline	Takes a settled idea to a finished branch: brainstorm, pressure-test, design gate, master plan, phase expansion, plan gate, then an autonomous per-phase implement/review/fix loop. Keeps its state on disk so a compaction or a crash cannot lose the run, and runs independent tasks as parallel implementers in separate worktrees.

The two are meant to run in order: `superb:craft` decides *what* the product is, `superb:pipeline` decides *how* it gets built and then builds it. Crafting reaching `CRAFT STATUS: VISION CLEAR` is the signal that the pipeline has enough to work from — it is not an instruction to start building.

`pipeline` composes the [superpowers](https://github.com/obra/superpowers) skills, so install that plugin too.

What a session looks like

`superb:craft`

> /superb:craft I want something like Spotify bu