Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
제작자가 쓴 설명(영어 원문)
Deterministic layered code graph MCP server with framework overlays and SCIP interop.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
Claude Desktop → Settings → Developer → Edit Config를 열고 claude_desktop_config.json에 이 내용을 붙여 넣으세요
{
"mcpServers": {
"hex-graph": {
"command": "npx",
"args": [
"-y",
"@levnikolaevich/hex-graph-mcp"
]
}
}
}터미널에서 이 명령어를 실행하세요
claude mcp add hex-graph -- npx -y @levnikolaevich/hex-graph-mcp프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"hex-graph": {
"command": "npx",
"args": [
"-y",
"@levnikolaevich/hex-graph-mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"hex-graph": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@levnikolaevich/hex-graph-mcp"
]
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 서버는 내 컴퓨터에서 실행되는데, ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요. 다른 앱을 고르세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
내 컴퓨터에서 실행돼요. 설치하면 AI 앱에 도구 목록이 나타나요.
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검
레지스트리 이름이 GitHub 계정 levnikolaevich 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
내 컴퓨터에서 실행되는 서버라 인터넷 엔드포인트가 없어요
내 컴퓨터에서 실행되며, 대신 로컬 설정을 사용해요
내 컴퓨터에서 실행돼요. 도구 목록은 인터넷 엔드포인트가 있는 서버에서만 읽을 수 있어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 1개 중 1개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.
내 컴퓨터에서 실행돼요. AI 앱이 필요할 때 실행하고, 데이터는 제작자의 서버를 거치지 않아요(서버 자체가 온라인 서비스를 호출하는 경우는 제외).
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(0.21.1)은 5개월 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. 내 컴퓨터에 Node.js도 있어야 해요.
같은 카테고리에는: Spec Driven Development, Remote Desktop Commander, Zendesk
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도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.
Zendesk MCP Pack — tickets, users, organizations via OAuth.
제작자의 저장소에서 쓰인 그대로 가져왔어요. 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
앞부분만 보여 드려요. 나머지는 저장소에서 읽어 보세요