sdlc vs iKanban
sdlc is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
sdlc is a plugin bundle for AI coding tools published by SDLC Team. No marketplace we read lists it any more. iKanban is an MCP server published by i-kanban.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace 45ck/claude-sdlc-plugin | Removed on 2026-10-16 Version: 1.1.1 Forks (GitHub): 1 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | sdlcno longer listed · | iKanban |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.i-kanban.com/sse) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 18 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/45ck/claude-sdlc-plugin | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 days ago, requires a key |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of sdlc
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Specification Driven Development workflow commands and agents, based on Github Spec Kit and OpenSpec. Uses specialized agents for effective context management and quality review.
-
Complete SDLC framework with 180+ specialized agents for software development lifecycle management.
-
Agent dev workflows: UI friction fixes, release patterns. Any platform: options-then-build for UI friction, sprint or release-to-test release patterns pinned to CLAUDE.md.
-
Specification-driven development workflow: setup → specify → plan → tasks → implement
-
Software development lifecycle automation - slash commands, agents, and GitHub/GitLab webhook watchers
-
Full SDLC pipeline with 7 agents: architecture, code review, QA, security. Two decisions per feature, the rest is automated.
What each says it does
sdlc
SDLC workflow automation with Storybook-powered planning hub
iKanban
Tasks, sprints, releases and docs for engineering teams with AI coding agents.
How to run each
sdlc
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
iKanban As a remote MCP server
claude mcp add --transport http ikanban https://mcp.i-kanban.com/sse --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only iKanban has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: sdlc · What it can do: iKanban · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.