stefan-jansen

Coding Agent Plugins — Productivity skill for Claude Code

Productivity community

Plugin marketplace for coding-agent-toolkit — workflow, memory, transition, development, and code-quality plugins for Claude Code.

How to install Coding Agent Plugins

This entry records only its repository, not the path inside it, so there is no exact command to give. Open stefan-jansen/coding-agent-plugins and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Coding Agent Plugins does

Plugin marketplace for coding-agent-toolkit — workflow, memory, transition, development, and code-quality plugins for Claude Code.

Alternatives in Productivity

Performance Optimization Skill — Systematic performance analysis and optimization for RTK CLI tool, focusing on startup time (<10ms), memory us 11.9k ★
Ra Qm Team Skills — Regulatory affairs and quality management 5.3k ★
/strategy — Run an end-to-end strategy workflow with decision-quality outputs 2.3k ★

README

coding-agent-plugins

Plugin marketplace for [coding-agent-toolkit](https://github.com/stefan-jansen/coding-agent-toolkit).

Provides a small set of workflow, memory, and code-quality plugins for Claude Code. Each plugin is a directory with a `plugin.json` and its own README documenting the skills/commands it ships.

Getting started

1. Clone the marketplace

git clone git@github.com:stefan-jansen/coding-agent-plugins.git ~/path/to/coding-agent-plugins

2. Register it and enable plugins

cd ~/path/to/coding-agent-plugins
scripts/enable.sh                    # workflow, memory, transition, development, system
scripts/enable.sh workflow memory    # or pick your own set
scripts/enable.sh --list             # show what is enabled

The script merges into `~/.claude/settings.json`, so the plugins are on in every project on this machine and no project repo carries agent config. It is idempotent and backs the file up before its first change. To do it by hand, or to scope plugins to one project instead, see [Where to enable](#where-to-enable).

3. Reload plugins

Run `/reload-plugins` in a running session to pick up a newly enabled or edited plugin, or start a new session.

Plugins

**Foundation** — generic infrastructure most projects want:

Plugin	Ships	Description
`workflow`	`/align` `/decompose` `/plan-issues` `/next-issue` `/ship` `/handoff` `/continue` `/delegate` `/next` `/work` `/spike`	Structured task execution — spec → issues → implement → deliver, plus session handoffs
`memory`	`/memory-gc` `/memory-review` `/memory-update` `/index` `/performance`	Persistent project memory under a token budget
`transition`	PreCompact / PostCompact / SessionEnd hooks	Write a session summary to `.workspace/transitions/YYYY-MM-DD/HHMMSS.md` on every compaction
`development`	`/analyze` `/review` `/docs` `/test` `/fix` `/git` `/prepare-review`	Code analysis, review, TDD, debugging, docs, git