Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Beschreibung vom Entwickler (englisches Original)
Token-efficient SSH MCP with hash-verified files and persistent tmux sessions. 14 tools.
Diese drei werden nie zu einer Punktzahl zusammengefasst: Meinungen, Messungen und Beliebtheit sind verschiedene Dinge.
Für diesen Server haben wir noch keine Zusammenfassung in einfacher Sprache geschrieben. Unten stehen die Fakten, die wir aus der Registry gelesen haben.
Wähle die KI-App, die du nutzt, und kopiere die Einstellungen.
Du brauchst
Welche App nutzt du?
Wähle oben deine App. Wir merken sie uns, damit der Button beim nächsten Mal „In … installieren“ anzeigt.
Öffne Claude Desktop → Settings → Developer → Edit Config und füge dies in claude_desktop_config.json ein
{
"mcpServers": {
"hex-ssh": {
"command": "npx",
"args": [
"-y",
"@levnikolaevich/hex-ssh-mcp"
]
}
}
}Führe das in deinem Terminal aus
claude mcp add hex-ssh -- npx -y @levnikolaevich/hex-ssh-mcpIn .cursor/mcp.json in deinem Projekt oder in ~/.cursor/mcp.json einfügen
{
"mcpServers": {
"hex-ssh": {
"command": "npx",
"args": [
"-y",
"@levnikolaevich/hex-ssh-mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
In .vscode/mcp.json in deinem Projekt einfügen
{
"servers": {
"hex-ssh": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@levnikolaevich/hex-ssh-mcp"
]
}
}
}Dein Browser fragt, ob er die App öffnen darf, dann zeigt die App die Einstellungen und bittet dich um Bestätigung. Schlüsselwerte bleiben leer, damit du sie selbst einträgst.
Dieser Server läuft auf deinem Computer, und ChatGPT kann sich nur mit Servern im Internet verbinden. Wähle eine andere App.
Deine Auswahl bleibt in einem Cookie auf diesem Gerät; kein Konto nötig.
Diese Einstellungen werden aus dem Registry-Eintrag des Entwicklers erzeugt. Wenn in der README etwas anderes steht, folge der README.
Läuft auf deinem Computer; die Tool-Liste erscheint nach der Installation in deiner KI-App.
Wir prüfen Informationen, die jeder sehen kann; den Code haben wir nicht gelesen. Checks, die nicht zutreffen, werden nicht mitgezählt. · Geprüft am 6. Nov. 2026
Der Registry-Name wurde mit dem GitHub-Konto levnikolaevich bestätigt, dem das Repo gehört
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieses Repo haben wir noch nicht von GitHub gelesen
Dieser Server läuft auf deinem Computer; es gibt keinen Endpunkt im Internet
Läuft auf deinem Computer und nutzt stattdessen lokale Einstellungen
Läuft auf deinem Computer; Tool-Listen können wir nur von Endpunkten im Internet lesen
Verglichen mit allen aktiven Servern dieser Kategorie in der Registry. Sterne zählen nur, wenn dem Herausgeber das Repo gehört.
Er hat 1 von 1 zutreffenden Basischecks bestanden. Den Code haben wir nicht gelesen. Bevor du einen Schlüssel oder Token hinzufügst, sieh nach, welche Zugriffe der Server verlangt, und nutze einen Schlüssel, der nur die Berechtigungen hat, die du brauchst.
Die Registry nennt keinen erforderlichen Schlüssel, manche Server bitten dich aber bei der ersten Nutzung, dich anzumelden.
Er läuft auf deinem Computer. Deine KI-App startet ihn bei Bedarf, und die Daten laufen nicht über die Server des Entwicklers (außer der Server ruft selbst einen Onlinedienst auf).
Das GitHub-Repo wurde zuletzt – geändert, und die neueste Version (1.9.2) kam vor 6 Monaten in die Registry.
Apps, die MCP unterstützen, etwa Claude Desktop, Claude Code, Cursor und VS Code. Außerdem brauchst du Node.js auf deinem Computer.
In derselben Kategorie: Spec Driven Development, Remote Desktop Commander, Fomu MCP
Server derselben Kategorie von anderen Entwicklern, sortiert nach Sternen.
So liest du eine Karte:★ GitHub-SterneiDrei Säulen: Bewertungen · Checks · NutzungiAktualisiert = neueste Version in der Registry veröffentlichti
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Kenya government form guides: checklists, draft letters, eCitizen, Huduma, timelines. Sample data.
Unverändert aus dem Repo des Entwicklers übernommen. PopNx MCP hat den Inhalt weder geprüft noch empfiehlt es ihn. HTML, Bilder und Skripte wurden entfernt. Links führen von dieser Website weg.
Open-source standalone agent skills, distributed as plugins for Claude Code and OpenAI Codex, help turn product ideas, code fixes, architecture reviews and deployments into scoped work with a verifiable result. Each workflow defines what to check, what it may change, and how to report evidence and remaining gaps.
Project page · Install · Full catalog
Choose by the result you need. Each skill works independently.
| Your task | Plugin | Result |
|---|---|---|
| Is this idea worth building? | product-discovery-suite | Opportunity assessment, requirements, or interaction design. |
| How should this system change? | architecture-suite | System map, design decision, or migration plan. |
| Is this plan ready to implement? | delivery-planning-suite | Reviewed plan, ordered work, and test strategy. |
| Fix, upgrade, simplify, or speed up this code. | implementation-suite | Scoped change with behavior and benefit checks. |
| Set up lint, type or architecture checks that enforce project rules. | implementation-suite | Verified quality gates, with project compliance reported separately. |
| What could go wrong with this delivery or codebase? | quality-assurance-suite | Evidence-backed findings or scoped acceptance tests. |
| Get this change published or deployed. | delivery-suite | Authorized publication or deployment, verified at its destination. |
| Why did this fail, or did the feature help? | operations-suite | Incident diagnosis or product outcome assessment. |
| Can I trust the instructions in this skill? | skill-maintenance-suite | Skill boundaries, consistency, and distribution review. |
| Prepare Docker containers, configuration, access control or recovery. | engineering-foundation-suite | Native technical contracts and verified changes. |
For a feature or fix, start with implementation-suite. Replace it with another plugin from Choose a route for a different task.
Claude Code:
/plugin marketplace add levnikolaevich/claude-code-skills
/plugin install implementation-suite@levnikolaevich-skills-marketplace /reload-plugins
Codex:
codex plugin marketplace add levnikolaevich/claude-code-skills
codex plugin add implementation-suite@levnikolaevich-skills-marketplace
Invoke a skill by its full name: /implementation-suite:ln-41-surgical-change-implementer in Claude Code or $ln-41-surgical-change-implementer in Codex, followed by your task. For example: “Fix the total calculation when an item has a discount. Preserve the current rounding rules.”
For personal defaults shared by Claude Code and Codex, use the optional user instructions template and connection guide. Personalize and merge it into your existing configuration; plugin installation does not change global instructions.
Decide what is worth building, who it serves, and what a useful first version must do.
| Index | Skill | Purpose |
|---|---|---|
| 11 | Opportunity Evaluator | Evaluates new product opportunities through demand, channels and economics before committing to build. |
| 12 | Product Requirements Builder | Defines product requirements, business rules and acceptance criteria for a committed intent; edits product docs only. |
| 13 | Interaction Design Builder | Designs user flows, interaction states and mockups for a defined product scope; does not implement UI code. |
Understand the system you have and choose changes with clear boundaries, tradeoffs, and recovery paths.
| Index | Skill | Purpose |
|---|---|---|
| 21 | System Design Baseline Builder | Defines measurable architecture drivers and constraints before system design; edits architecture docs only. |
| 22 | Current Architecture Documenter | Documents current architecture from implementation evidence; does not propose a target or audit fitness. |
| 23 | System Design Proposal Builder | Designs target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement. |
| 24 | Architecture Decision Recorder | Records one architecture decision with alternatives, consequences and status; does not design the whole system. |
| 25 | Architecture Diagram Builder | Creates evidence-backed current or target architecture diagrams; not UI design. |
| 26 | Architecture Migration Planner | Plans architecture migrations with compatibility, data safety, rollout and recovery; does not execute them. |
Find missing decisions and risky dependencies before they become implementation rework.
| Index | Skill | Purpose |
|---|---|---|
| 31 | Delivery Plan Builder | Builds dependency-ordered delivery plans from requirements and repository evidence; read-only. |
| 32 | Test Strategy Planner | Plans risk-based test portfolios and acceptance evidence; does not write or execute tests. |
| 33 | Plan Reviewer | Reviews a concrete implementation plan for missing decisions, feasibility and risk before execution; read-only. |
Fix the cause, reuse what already works, and keep changes focused on a verified outcome.
| Index | Skill | Purpose |
|---|---|---|
| 41 | Surgical Change Implementer | Implements one scoped product feature or fix using existing contracts; not upgrades, performance tuning or establishing cross-cutting technical foundations. |
| 42 | Dependency Upgrader | Upgrades dependencies in reversible batches with version-specific compatibility and regression checks. |
| 43 | Code Modernizer | Modernizes a bounded capability to reduce demonstrated maintenance cost; not routine upgrades or performance tuning. |
| 44 | Performance Optimizer | Profiles and improves a measured performance bottleneck; retains only verified improvements. |
| 45 | Benchmark Comparator | Compares tools or implementations through controlled benchmarks and independent correctness checks. |
| 46 | Quality Gate Engineer | Configures and verifies lint, type, architecture and other engineering checks; not product cleanup, policy invention or deployment redesign. |
Find gaps that could break a release, mislead a maintainer, or make a passing test meaningless.
| Index | Skill | Purpose |
|---|---|---|
| 51 | Acceptance Test Builder | Builds, updates or retires scoped acceptance tests and verifies execution; does not repair product code. |
| 52 | Delivery Reviewer | Reviews a completed change for acceptance, regressions and release risk; read-only, not a whole-codebase audit. |
| 53 | Documentation Auditor | Audits documentation and comments for trust, coverage, consistency and freshness; read-only. |
| 54 | Codebase Auditor | Audits cross-cutting codebase health, security and maintainability; not a single-change review or specialist audit. |
| 55 | Test Suite Auditor | Audits existing tests for risk coverage, reliable oracles and maintenance value; does not edit tests. |
| 56 | Architecture Auditor | Audits implemented architecture boundaries, dependencies and ownership; not target design or plan review. |
| 57 | Persistence Auditor | Audits queries, transactions, consistency and persistence resource lifetimes; read-only. |
Publish the intended changes and verify what reached the remote repository or target environment.
| Index | Skill | Purpose |
|---|---|---|
| 61 | Repository Publisher | Commits, pushes and remotely verifies authorized repository changes; does not create releases. |
| 62 | Release Publisher | Prepares and publishes an explicitly requested tagged GitHub release; does not deploy applications. |
| 63 | Deployment Engineer | Prepares delivery pipelines and remote infrastructure, then executes authorized rollouts; not standalone quality-gate setup or local container packaging. |
| 64 | Community Announcer | Drafts or publishes authorized, fact-checked GitHub Discussions announcements; does not create releases. |
Turn incidents and product signals into evidence for the next recovery or product decision.
| Index | Skill | Purpose |
|---|---|---|
| 71 | Operations Investigator | Diagnoses incidents from operational evidence and proposes recovery; does not change live systems. |
| 72 | Product Outcome Evaluator | Evaluates observed product outcomes against a prior hypothesis; does not run experiments or change user treatment. |
Make skills easier to invoke correctly, follow consistently, and verify before distribution.
| Index | Skill | Purpose |
|---|---|---|
| 81 | Skill Reviewer | Reviews skill instructions, trigger boundaries and distribution contracts; not product code. |
Establish and verify project technical foundations using native stack mechanisms, explicit contracts and safe recovery.
| Index | Skill | Purpose |
|---|---|---|
| 91 | Engineering Baseline Builder | Creates project technical rules and recurring local procedures from the actual stack; edits guidance only, not architecture targets or application code. |
| 92 | Container Engineer | Builds, hardens or reviews container images and local runtime packaging with startup and
Nur der Anfang wird gezeigt; den Rest findest du im Repo