requirement-elicitation vs DevPlan MCP Server
requirement-elicitation is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑24.
requirement-elicitation is a plugin bundle for AI coding tools published by Britt Crawford. No marketplace we read lists it any more. DevPlan MCP Server is an MCP server published by mmorris35. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  DevPlan MCP Server | |
|---|---|---|
| Community marketplace britt/agent-skills | Removed on 2026-10-24 Version: 1.1.0 Forks (GitHub): 1 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 Forks (GitHub): 4 Stars (GitHub): 7 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 | requirement-elicitationno longer listed · | DevPlan MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 8 | 7 |
| Forks (GitHub) (differs) | 1 | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (devplan-mcp-server.mike-c63.workers.dev/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/britt/agent-skills | github.com/mmorris35/devplan-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 301 (7 h ago) |
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 requirement-elicitation
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Spec-driven development methodology with skills for requirements, design, tasks, AI prompting, QA, and troubleshooting
-
Transform vague prompts into precise, well-structured specifications using EARS (Easy Approach to Requirements Syntax) methodology. Use when users provide loose requirements…
-
Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear or features are complex.
-
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation
-
Grill the user about a requirement, decision, or idea before implementation, then produce an actionable planning report without writing code
-
Interview command for fleshing out big feature plans and specifications
What each says it does
requirement-elicitation
Adaptive conversational wizard for eliciting project requirements across functional, nonfunctional, and edge-case dimensions
DevPlan MCP Server
Transform project ideas into paint-by-numbers development plans with phases, tasks, and subtasks.
How to run each
requirement-elicitation
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
DevPlan MCP Server As a remote MCP server
claude mcp add --transport http devplan-mcp-server https://devplan-mcp-server.mike-c63.workers.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only DevPlan MCP Server 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: requirement-elicitation · What it can do: DevPlan MCP Server · 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.