A Claude Code plugin that automates SDLC tasks: generates structured PR descriptions from commits and diffs, and runs project-customizable multi-dimension code reviews.
Documentation & Skill Reference — interactive skill docs, workflow diagrams, and pipeline visualizations.
- Open Claude Code and run
/plugin - Go to Marketplaces → Add marketplace → enter
rnagrodzki/sdlc-marketplace - Go to Discover → select
sdlc→ Install
/plugin marketplace add rnagrodzki/sdlc-marketplace
/plugin install sdlc@sdlc-marketplace
See docs/getting-started.md for a full first-use walkthrough.
Open /plugin, go to Marketplaces, and toggle auto-update for sdlc-marketplace. When enabled, Claude Code checks for new versions on startup.
/plugin marketplace update sdlc-marketplace
/plugin update sdlc@sdlc-marketplace
| Skill | Description |
|---|---|
/pr-sdlc |
Create a PR with an auto-generated structured description |
/review-sdlc |
Run multi-dimension code review on the current branch |
/received-review-sdlc |
Process code review feedback with verification, self-critique, and implementation |
/version-sdlc |
Bump version, create git tag, optionally generate CHANGELOG, and push |
/commit-sdlc |
Analyze staged changes, generate a commit message matching project style, stash unstaged changes, and commit |
/plan-sdlc |
Write an implementation plan from requirements, a spec, or a user description — produces plans optimized for execute-plan-sdlc |
/execute-plan-sdlc |
Execute an implementation plan with adaptive task classification, wave-based parallel dispatch, and automatic error recovery |
/ship-sdlc |
Chain execute, commit, review, version, and PR into a single shipping pipeline with conditional review-fix loop |
/jira-sdlc |
Create, edit, search, and transition Jira issues with cached project metadata |
/setup-sdlc |
Unified project setup — configure version, ship, review, PR templates, guardrails, and jira settings in one flow |
| Document | Description |
|---|---|
| Getting Started | Installation, first use, what gets created |
| Architecture | Repository structure, plugin system, name resolution |
| Plugin Installation | How plugins are installed, discovered, and resolved at runtime |
| Adding Skills | Create custom skills for your project |
| Skill Best Practices | Design patterns for reliable, maintainable skills |
| Adding Commands | Create custom slash commands (legacy — prefer skills) |
| Adding Hooks | Set up automated actions on session events |
| OpenSpec Integration | Using SDLC skills with OpenSpec for spec-driven development |
| Plugin Interop | Authority model for OpenSpec detection when multiple plugins coexist |
Clear the cache, restart, and reinstall:
rm -rf ~/.claude/plugins/cache/sdlc-marketplaceThen restart Claude Code and run:
/plugin install sdlc@sdlc-marketplace
The version field in plugin.json must be bumped for Claude Code to detect a new version. If the version hasn't changed, Claude Code uses the cached copy.
Open /plugin, go to the Marketplaces tab, and verify auto-update is toggled on for sdlc-marketplace. Auto-update is off by default for third-party marketplaces.
Large repositories may exceed the default git timeout. Set the environment variable before starting Claude Code:
export CLAUDE_CODE_PLUGIN_GIT_TIMEOUT_MS=300000See CHANGELOG.md for release history.