tech-spec vs io.github.einvoice-dev1/archsteer
tech-spec is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
tech-spec is a plugin bundle for AI coding tools published by iowarp. No marketplace we read lists it any more. io.github.einvoice-dev1/archsteer is an MCP server published by einvoice-dev1. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. 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 |  io.github.einvoice-dev1/archsteer | |
|---|---|---|
| Community marketplace iowarp/clio-kit | Removed on 2026-10-16 Version: 0.3.1 Forks (GitHub): 5 Stars (GitHub): 8 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.10.0 Downloads/month (PyPI): 301 Downloads/week (PyPI): 46 Forks (GitHub): 0 Stars (GitHub): 5 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 | tech-specno longer listed · | io.github.einvoice-dev1/archsteer |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 8 | 5 |
| Forks (GitHub) (differs) | 5 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (archsteer) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | Not published | 4 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/iowarp/clio-coder | github.com/einvoice-dev1/archsteer |
| Changes in the last 7 days (differs) | 4 | 2 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
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 tech-spec
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Spec-driven development workflow - transforms ideas into structured specifications (requirements, design, tasks) before implementation.
-
Architecture and modernization toolkit: produce a cited architecture document for a locally-cloned repo, and generate a phased modernization plan that auto-runs Documentation mode…
-
Understand the system you have and choose changes with clear boundaries, tradeoffs, and recovery paths.
-
Spec-driven development engine: turns feature specs into working code through structured requirements, wave-based parallel agent execution, and automated quality gates.
-
Context-Driven Development: draft specs and plans before implementation. Structured workflows for features and fixes.
-
A specification discovery plugin for Cowork and Claude Code. Helps product managers, founders, and tech leads figure out what to build before writing a single line of code. Unlike…
What each says it does
tech-spec
Writes a typed call-stack architecture handoff: code-shaped contracts plus execution flows, implementation-ready for another engineer. User-invoked only. Not for weighing approaches or deciding the design; use architecture first.
io.github.einvoice-dev1/archsteer
Architecture governance for AI agents: query the live model, get target patterns, check files.
How to run each
tech-spec
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.einvoice-dev1/archsteer As a local MCP server: PyPI package
claude mcp add --transport stdio archsteer -- uvx archsteer mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: tech-spec · What it can do: io.github.einvoice-dev1/archsteer · 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.