Skip to content

README.md

Latest commit

 

History

History
161 lines (115 loc) · 6.81 KB

README.md

File metadata and controls

161 lines (115 loc) · 6.81 KB
Raw
 ██████╗ █████╗ ██████╗ ███████╗███╗   ██╗███████╗ █████╗
██╔════╝██╔══██╗██╔══██╗██╔════╝████╗  ██║╚══███╔╝██╔══██╗
██║     ███████║██║  ██║█████╗  ██╔██╗ ██║  ███╔╝ ███████║
██║     ██╔══██║██║  ██║██╔══╝  ██║╚██╗██║ ███╔╝  ██╔══██║
╚██████╗██║  ██║██████╔╝███████╗██║ ╚████║███████╗██║  ██║
 ╚═════╝╚═╝  ╚═╝╚═════╝ ╚══════╝╚═╝  ╚═══╝╚══════╝╚═╝  ╚═╝

Standalone solos. No orchestra required.

Utility agents that each have one job — and do it well, with no pipeline, no orchestration, and no ceremony.

Claude Code License: MIT Version

What Is Cadenza?

In a concerto, the cadenza is the moment the orchestra pauses and a single instrument plays alone — free, expressive, complete on its own terms.

Cadenza is a Claude Code plugin built on that same idea. It contains specialist agents, each handling one task: generating changelogs, writing PR descriptions, authoring PHPUnit tests, and producing retrospective reports. No pipeline. No spec. No twelve-agent handoff chain. Just ask, and it's done.

Use Cadenza on its own for projects that don't need a full delivery pipeline. Or pair it with Maestro — both plugins can be installed in the same project and coexist without conflict.

Install

/plugin install cadenza@wp-media

That's it. Project identity is auto-detected from your repo — no config file to add. All agents are ready.

The Soloists

Each one performs alone.

Agent Command What it does
changelog-agent /cadenza:changelog Collects merged PRs since the last release, groups them by user impact, and writes a PO-ready changelog draft
pr-agent /cadenza:pr Reads your branch commits and diffs, then writes a structured PR description — without pushing anything
test-writer /cadenza:test Discovers your project's test conventions, then authors PHPUnit unit and integration tests for PHP source files
retrospective-agent /cadenza:retrospective Scans completed pipeline runs, surfaces DOD pass rates and loop-back patterns, and suggests concrete AGENTS.md learnings
issue-writer /cadenza:issue Turns raw context, a thread, or a rough note into a well-structured GitHub issue, then shows it for confirmation before creating
(built-in) /cadenza:commit Analyses changed files, groups them into atomic commits with generated messages, then offers to push

Commands

Command What it does
/cadenza Show the full command map
/cadenza:changelog [v1.2.3] Generate a PO-ready changelog from merged PRs
/cadenza:pr Write a PR description for the current branch
/cadenza:test [path/to/File.php] Author PHPUnit tests for a source file (or auto-detect from branch diff)
/cadenza:retrospective [date-from date-to] Analyse completed pipeline runs and surface learnings
/cadenza:issue [raw context] Turn raw context or a thread into a well-structured GitHub issue
/cadenza:commit [without <file>] Atomic commits with generated messages, then offer to push

Zero Config, Any Project

Every agent auto-detects project identity at startup — from your git remote, your plugin's Plugin Name: header, composer.json, or the repo directory name. The agents live in the plugin. Your projects have nothing to commit.

Cadenza plugin (installed once)        Your projects
──────────────────────────────         ────────────────────────────────────
agents/                                project-a/
  changelog-agent.md  ──────────────►    (auto-detected)
  pr-agent.md         ──────────────►
  test-writer.md      ──────────────►  project-b/
  retrospective-agent.md ───────────►    (auto-detected)
  issue-writer.md     ──────────────►
skills/
  changelog/                           project-c/
  pr/                                    (auto-detected)
  test/
  retrospective/
  issue/
  commit/

When Cadenza ships a new version, every project picks it up on the next Claude session — no action needed.

Configuration

None. Everything is auto-detected from your repo — nothing to commit.

Using Cadenza Alongside Maestro

Cadenza and Maestro can both be installed in the same project and operate without conflict.

When Maestro is installed, its pipeline invokes the same agents internally. Cadenza exposes them as standalone /cadenza:* commands — available anytime, outside any pipeline run.

Want to watch every agent event live? Add Podium.

/plugin install podium@wp-media
/podium start   →   http://localhost:4820

Repository Layout

cadenza/
│
├── AGENTS.md                        ← Base guardrails every project extends
│
├── agents/                          ← 5 standalone agents
│   ├── changelog-agent.md
│   ├── issue-writer.md
│   ├── pr-agent.md
│   ├── retrospective-agent.md
│   └── test-writer.md
│
├── skills/                          ← Skills (slash commands)
│   ├── cadenza/
│   ├── changelog/
│   ├── commit/
│   ├── issue/
│   ├── pr/
│   ├── retrospective/
│   └── test/
│
└── refs/                            ← Bundled reference files
    └── pr-template.md               ← Default PR description template

The orchestra pauses. You play.

Part of the Orchestra suite — Maestro · Podium · Cadenza

Built at WP-Media