agentic-development-lifecycle vs SHIP
agentic-development-lifecycle is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
agentic-development-lifecycle is a plugin bundle for AI coding tools published by hiepdnh. No marketplace we read lists it any more. SHIP is an MCP server published by letsship.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |   SHIP | |
|---|---|---|
| Community marketplace hiepdnh/agentic-development-lifecycle | Removed on 2026-10-22 Version: 1.3.0 Forks (GitHub): 1 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.24.0 Forks (GitHub): 0 Stars (GitHub): 1 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 | agentic-development-lifecycleno longer listed · | SHIP |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 7 | 1 |
| Forks (GitHub) (differs) | 1 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.letsship.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 47 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/hiepdnh/agentic-development-lifecycle | github.com/letsship/mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-21 | 2026-10-12 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 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 agentic-development-lifecycle
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Never re-explain your project to Claude again. devpace remembers context across sessions, manages requirement changes, and ensures quality gates — all automatically. Zero setup…
-
Software engineering workflows with skills for planning, implementation, quality review, and structured thinking, plus a suite of specialist agents
-
Engineering & tech skills: Code Review Checklist, Incident Postmortem, API Docs Writer, Architecture Decision Record, Debugging Log Analyser, PR Description Writer, System Design…
-
Codely's team skills: planning, docs, OpenSpec, and git conventions.
-
Structured, standards-aware SDLC orchestration for Claude Code — 5 workflow types, 23 agents, 15+ skills, visual companion server for product design.
-
Get Shit Done Plugin - handles large codebase contexts - structured workflow plugin for Claude Code with 60+ slash commands, 21 agents, MCP server, hooks, and cross-session memory
What each says it does
agentic-development-lifecycle
Agentic Development Lifecycle — SDLC skill framework for Claude Code, OpenCode, Cursor & Antigravity (English / Tiếng Việt / 日本語)
SHIP
Assign Linear, Jira or GitHub issues to an AI coding agent team that plans, builds, reviews, tests.
How to run each
agentic-development-lifecycle
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
SHIP As a remote MCP server
claude mcp add --transport http ship https://mcp.letsship.ai/mcp --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 SHIP 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: agentic-development-lifecycle · What it can do: SHIP · 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.