Skip to content
sdlc marketplace

sdlc marketplace

SDLC plugins and skills sksizer publishes for coding agents.

5 plugins, 7 skills.

Install

Add the marketplace to Claude Code, then install a plugin from it:

/plugin marketplace add sksizer/marketplace-sdlc
/plugin install <plugin>@sdlc

authoring v0.1.0

Skills for writing and maintaining documents alongside the people who own them.

  • collaborate-in-markdown — Co-edit a markdown document the user has open and is typing in. Read the document, find `@agent` markers, do the work each one asks for, then present every proposed change in chat and get approval before writing anything. Use when the user points at a markdown file containing `@agent` markers, asks you to fill in or answer parts of a doc you are both working on, or says to collaborate on / work through a document together. Exists to keep writes from clobbering content the user is editing live.

codebase v0.1.0

Skills for understanding and improving an unfamiliar body of code.

  • api-enhancement-scan — Given a library or module name, survey every call site of it across the codebase — fanning out subagents over independent codebase sections — and surface recurring caller-side patterns (repeated boilerplate, copy-pasted wrappers, awkward argument plumbing, repeated post-processing) that a new or enhanced API on the called module would absorb. Returns ranked enhancement opportunities, each backed by real call-site citations. Use when asked to find API improvement or enhancement opportunities for a module, library, or package, to spot missing affordances, or to understand how a module is actually used by its callers. Pass --in to survey only named packages or directories instead of the whole project, and --workflow to have it propose a reusable Workflow script for the survey instead of running it ad hoc.
  • explore-codebase — Systematic method for understanding an unfamiliar codebase: getting oriented in a new repo, locating where something is implemented, tracing how a feature or request flows end to end, and building an accurate mental model before answering questions or making changes. Use whenever you're dropped into a repo or the user asks things like "how does X work here", "where is Y handled", "how is this project structured", "help me understand this codebase", "onboard me to this code", "find where Z is implemented", or "explore this repo and write up notes" — or before editing code you haven't read yet. Can optionally save the resulting map as a markdown file, a linked Obsidian-style vault, or a self-contained HTML page carrying diagrams of the structure it found.

demo v0.1.0

A demonstration plugin: one skill, to prove the marketplace builds and installs.

  • hello-world — Prints a greeting and reports the marketplace it was installed from. Use to verify a marketplace install worked.

repo v0.1.0

Skills for keeping a repository's branches, worktrees and configuration tidy.

  • session-cleanup — Tear down the branch and worktree a conversation worked in, but only after proving the work is safe: nothing uncommitted, nothing unpushed, and the branch tip reachable from the default branch. When any of those fail it reports exactly what is unlanded and stops without touching anything. When they pass it deletes the local and remote branch, removes the worktree, and prunes. Invoke at the end of a session for "clean up", "clean up this branch", "we're done here", "tear down the worktree", or "is this safe to delete".

review v0.1.0

Skills for judging a change or a body of code before it merges.

  • comment-review — Review the comments in a diff or a subtree and minimize them against the expression ladder: a fact belongs first in the identifier, then in the signature and types, then in the declaration's doc annotation, and only when none of those can carry it does it earn an inline comment. Deletes comments that restate the code, moves facts down the ladder, tightens what survives to one short literal statement, strips volatile project state, and replaces duplicated prose with a reference to one canonical home. Invoke for "review the comments", "too many comments", "comment cleanup", or as the comment pass on a branch before review.
  • sks-code-review — Shell out to a headless external agent — codex by default, claude on request — for a code review of the current branch against the upstream default branch: potential errors, cleanup areas, duplication, and opportunities to better use or grow our library set.