Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Token-efficient SSH MCP with hash-verified files and persistent tmux sessions. 14 tools.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
Claude Desktop → Settings → Developer → Edit Config を開き、claude_desktop_config.json にこれを貼り付けます
{
"mcpServers": {
"hex-ssh": {
"command": "npx",
"args": [
"-y",
"@levnikolaevich/hex-ssh-mcp"
]
}
}
}ターミナルでこれを実行します
claude mcp add hex-ssh -- npx -y @levnikolaevich/hex-ssh-mcpプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"hex-ssh": {
"command": "npx",
"args": [
"-y",
"@levnikolaevich/hex-ssh-mcp"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"hex-ssh": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@levnikolaevich/hex-ssh-mcp"
]
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
これはパソコンで動くサーバーですが、ChatGPTがつなげるのはインターネット上のサーバーだけです。ほかのアプリを選んでください。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント levnikolaevich で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(1.9.2)がレジストリに届いたのは6 か月前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにNode.jsも必要です。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, Python MCP
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
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.
Local-only Python MCP server for the Files.com API.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
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
冒頭だけを表示しています。続きはリポジトリで読めます