/ الدليل / الملعب / Spec Workflow
← كل الخوادم ↗ GitHub
● مجتمع Pimzino ⚡ فوري

Spec Workflow

بواسطة Pimzino · Pimzino/spec-workflow-mcp

Structured Requirements → Design → Tasks workflow with a live dashboard and human approval gates — stop Claude YOLO-coding features.

Spec Workflow turns feature development into a three-stage pipeline: Requirements doc, Design doc, Task list. Each stage requires approval (via web dashboard or VSCode sidebar) before moving on. Claude can't skip ahead, writes implementation logs, and tracks progress bar state on every task. Feels like Jira-for-Claude.

▶ شاهد العرض 📦 التثبيت 💡 حالات الاستخدام

لماذا تستخدمه

الميزات الأساسية

عرض مباشر

كيف يبدو في الممارسة

spec-workflow-mcp.replay ▶ جاهز
0/0

التثبيت

اختر العميل

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "spec-workflow-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pimzino/spec-workflow-mcp@latest",
        "/path/to/project"
      ]
    }
  }
}

افتح Claude Desktop → Settings → Developer → Edit Config. أعد التشغيل بعد الحفظ.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "spec-workflow-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pimzino/spec-workflow-mcp@latest",
        "/path/to/project"
      ]
    }
  }
}

يستخدم Cursor نفس مخطط mcpServers مثل Claude Desktop. إعدادات المشروع أولى من الإعدادات العامة.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "spec-workflow-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pimzino/spec-workflow-mcp@latest",
        "/path/to/project"
      ]
    }
  }
}

انقر على أيقونة MCP Servers في شريط Cline الجانبي، ثم "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "spec-workflow-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@pimzino/spec-workflow-mcp@latest",
        "/path/to/project"
      ]
    }
  }
}

نفس الصيغة مثل Claude Desktop. أعد تشغيل Windsurf لتطبيق التغييرات.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "spec-workflow-mcp",
      "command": "npx",
      "args": [
        "-y",
        "@pimzino/spec-workflow-mcp@latest",
        "/path/to/project"
      ]
    }
  ]
}

يستخدم Continue مصفوفة من كائنات الخادم بدلاً من خريطة.

~/.config/zed/settings.json
{
  "context_servers": {
    "spec-workflow-mcp": {
      "command": {
        "path": "npx",
        "args": [
          "-y",
          "@pimzino/spec-workflow-mcp@latest",
          "/path/to/project"
        ]
      }
    }
  }
}

أضف إلى context_servers. يعيد Zed التحميل تلقائيًا عند الحفظ.

claude mcp add spec-workflow-mcp -- npx -y @pimzino/spec-workflow-mcp@latest /path/to/project

أمر من سطر واحد. تحقق باستخدام claude mcp list. احذف باستخدام claude mcp remove.

حالات الاستخدام

استخدامات عملية: Spec Workflow

Build a feature with a spec, not a vibe prompt

👤 Devs shipping medium-complexity features ⏱ ~90 min intermediate

متى تستخدمه: You're about to ask Claude to "add OAuth" and dread the 500-line diff that will land in one go.

المتطلبات الأساسية
  • Project path known — MCP is launched with /path/to/project as arg
الخطوات
  1. Requirements
    Use spec-workflow. Create a spec named oauth-login. Start with requirements — what are we adding, who is it for, what are the non-goals?✓ تم النسخ
    → Requirements doc drafted, link to dashboard for approval
  2. Approve + Design
    I approved in the dashboard. Now write the design: components, data model, sequence diagram, error cases.✓ تم النسخ
    → Design doc with concrete architecture
  3. Tasks + Execute
    I approved. Break into tasks. Then execute task 1.1 — just that one, stop after.✓ تم النسخ
    → Task list created; only task 1.1 implemented with log entry

النتيجة: A feature shipped with reviewable intermediate artifacts — not a mystery diff.

المزالق
  • Claude tries to skip straight to code — The MCP blocks it — but be explicit in prompts anyway: "do not implement yet"
اجمعها مع: github · filesystem

Get a non-engineer stakeholder to approve a spec before code happens

👤 Teams with PM/design sign-off loops ⏱ ~60 min intermediate

متى تستخدمه: You need PM approval before implementation and the PM doesn't read GitHub PRs.

المتطلبات الأساسية
  • Dashboard URL shareable — Port-forward or expose localhost:5000 via ngrok for remote PMs
الخطوات
  1. Spec
    Draft the requirements doc for checkout-v2 and share the dashboard URL.✓ تم النسخ
    → Doc + shareable link
  2. Iterate via feedback
    PM left 3 revision comments in the dashboard. Fetch them and revise the doc.✓ تم النسخ
    → Doc updated with revision history visible
  3. Execute post-approval
    Approval just went through — proceed to design.✓ تم النسخ
    → Next stage starts; approval timestamp logged

النتيجة: Traceable approval chain from non-engineer stakeholders.

المزالق
  • Dashboard not reachable for remote users — Use Tailscale or ngrok with auth
اجمعها مع: github

التركيبات

اجمعها مع خوادم MCP أخرى لتحقيق نتائج x10

spec-workflow-mcp + github

Open a PR per approved task

After executing task 2.1, open a GitHub PR titled "feat(oauth): task 2.1" with the diff.✓ تم النسخ
spec-workflow-mcp + filesystem

Store specs in-repo alongside code

Save the approved spec to /docs/specs/oauth-login.md and commit.✓ تم النسخ

الأدوات

ما يوفره هذا الـ MCP

الأداةالمدخلاتمتى تستدعيهاالتكلفة
create_spec name: str Start a new feature free
write_requirements spec_id, content: markdown First phase of any spec free
write_design spec_id, content: markdown After requirements approved free
create_tasks spec_id, tasks: [] After design approved free
execute_task spec_id, task_id Implement one task at a time free
get_approval_status spec_id, stage Gate next stage free

التكلفة والحدود

تكلفة التشغيل

حصة API
Local
الرموز لكل استدعاء
Proportional to doc/task size
التكلفة المالية
Free
نصيحة
Keep requirements concise — the approval cost is human time, not tokens

الأمان

الصلاحيات والأسرار ونطاق الأثر

الحد الأدنى من الصلاحيات: filesystem-write (for spec docs)
تخزين بيانات الاعتماد: None
نقل البيانات الخارجي: None — localhost dashboard

استكشاف الأخطاء

الأخطاء الشائعة وحلولها

Dashboard won't load

Start it explicitly: npx -y @pimzino/spec-workflow-mcp@latest --dashboard

تحقق: Visit localhost:5000
Port 5000 already in use (macOS AirPlay)

Pass --port 5050 or disable AirPlay Receiver in System Settings

تحقق: Check with `lsof -i :5000`
Tasks stay in pending after approval

MCP client may be caching old tool results — restart the client

البدائل

Spec Workflow مقابل البدائل

البديلمتى تستخدمهاالمقايضة
Plain Markdown in /docsSolo dev with no approval loop neededNo structure enforcement, no dashboard
Linear MCPYou already use Linear for tasks and want Claude to touch issues directlyNo spec-doc layer

المزيد

الموارد

📖 اقرأ ملف README الرسمي على GitHub

🐙 تصفح القضايا المفتوحة

🔍 تصفح أكثر من 400 خادم MCP و Skills