|
1 | | -# spec-coding-mcp |
| 1 | + **[简体中文](./README_zh-cn.md)** |
| 2 | + |
| 3 | +# Spec Coding MCP Server |
| 4 | + |
| 5 | +Transform feature ideas into production-ready code through systematic **Spec-Driven Development** |
| 6 | + |
| 7 | +## 🎯 Spec-Driven Development Workflow |
| 8 | + |
| 9 | +### Phase 1: Feature Definition |
| 10 | + |
| 11 | +- Learn details about feature by interacting with user |
| 12 | + |
| 13 | +### Phase 2: Requirements Gathering |
| 14 | + |
| 15 | +- Transform feature idea into formal requirement using EARS format |
| 16 | + |
| 17 | +### Phase 3: Design Documentation |
| 18 | + |
| 19 | +- Develop technical architecture based on approved requirements |
| 20 | + |
| 21 | +### Phase 4: Task Planning |
| 22 | + |
| 23 | +- Break down design into discrete, actionable coding tasks |
| 24 | + |
| 25 | +### Phase 5: Task Execution |
| 26 | + |
| 27 | +- Implement the code following the plan |
| 28 | + |
| 29 | +## 🚀 Quick Start |
| 30 | + |
| 31 | +### Config MCP Server |
| 32 | + |
| 33 | +#### Using code |
| 34 | + |
| 35 | +```json |
| 36 | +{ |
| 37 | + "servers": { |
| 38 | + "SpecCodingMcpServer": { |
| 39 | + "type": "stdio", |
| 40 | + "command": "<PATH TO SpecCodingMcpServer.exe DIRECTORY>", |
| 41 | + "args": [] |
| 42 | + } |
| 43 | + } |
| 44 | +} |
| 45 | +``` |
| 46 | + |
| 47 | +#### Using exe |
| 48 | + |
| 49 | +```json |
| 50 | +{ |
| 51 | + "servers": { |
| 52 | + "SpecCodingMcpServer": { |
| 53 | + "type": "stdio", |
| 54 | + "command": "dotnet", |
| 55 | + "args": [ |
| 56 | + "run", |
| 57 | + "--project", |
| 58 | + "<PATH TO spec-coding-mcp\src\SpecCodingMcpServer DIRECTORY>" |
| 59 | + ] |
| 60 | + } |
| 61 | + } |
| 62 | +} |
| 63 | +``` |
| 64 | + |
| 65 | +#### Using NuGet |
| 66 | + |
| 67 | +- Visit `NuGet.org` and filter by mcpserver package type |
| 68 | +- Search `SpecCodingMcpServer` and copy the configuration from the “MCP Server” tab |
| 69 | + |
| 70 | +### Start the Workflow |
| 71 | + |
| 72 | +Here's a complete example of using the Spec Coding workflow: |
| 73 | + |
| 74 | +#### 1. Feature Definition |
| 75 | +``` |
| 76 | +Me: Start Spec Coding |
| 77 | +
|
| 78 | +AI: [call SpecCodingMcpServer/spec_coding_workflow_start] |
| 79 | +Welcome to Spec Coding! Let's start by defining your feature. |
| 80 | +
|
| 81 | +Me: create a Vue todo app |
| 82 | +
|
| 83 | +AI:Let me clarify a few more details to ensure we build exactly what you need |
| 84 | +
|
| 85 | +Me: [enter more details for the feature] |
| 86 | +
|
| 87 | +AI:Does this look good to proceed? Please confirm with "yes" |
| 88 | +
|
| 89 | +Me: yes |
| 90 | +
|
| 91 | +AI:[call SpecCodingMcpServer/spec_coding_feature_confirmed] |
| 92 | +[Create the feature documentation directory and README file as required by the spec coding workflow] |
| 93 | +``` |
| 94 | +#### 2. Requirements Gathering |
| 95 | +``` |
| 96 | +AI: Starting the requirements gathering phase for the Vue todo app |
| 97 | +[call SpecCodingMcpServer/spec_coding_requirements_start] |
| 98 | +[Create the requirements document for the Vue todo app with detailed EARS format requirements] |
| 99 | +Do the requirements look good? If so, we can move on to the design phase. |
| 100 | +
|
| 101 | +Me: yes |
| 102 | +
|
| 103 | +AI: [call SpecCodingMcpServer/spec_coding_requirements_confirmed] |
| 104 | +``` |
| 105 | + |
| 106 | +#### 3. Design Documentation |
| 107 | +``` |
| 108 | +AI: Starting the design phase for the Vue todo app |
| 109 | +[call SpecCodingMcpServer/spec_coding_design_start] |
| 110 | +[Create a comprehensive design document for the Vue todo app based on the requirements] |
| 111 | +Does the design look good? If so, we can move on to the implementation plan. |
| 112 | +
|
| 113 | +Me: yes |
| 114 | +
|
| 115 | +AI: [call SpecCodingMcpServer/spec_coding_design_confirmed] |
| 116 | +``` |
| 117 | + |
| 118 | +#### 4. Task Planning |
| 119 | +``` |
| 120 | +AI: Starting the task creation phase for the Vue todo app implementation |
| 121 | +[call SpecCodingMcpServer/spec_coding_tasks_start] |
| 122 | +[Create a comprehensive task list for implementing the Vue todo app based on the design and requirements] |
| 123 | +Do the tasks look good? Please review the task list and let me know if you'd like any adjustments before we proceed to the implementation phase. |
| 124 | +
|
| 125 | +User: yes |
| 126 | +
|
| 127 | +AI: [call SpecCodingMcpServer/spec_coding_tasks_confirmed] |
| 128 | +``` |
| 129 | + |
| 130 | +#### 5. Task Execution |
| 131 | +``` |
| 132 | +AI: Starting the actual implementation phase for the Vue todo app |
| 133 | +[call SpecCodingMcpServer/spec_coding_execute_start] |
| 134 | +[Execute tasks one by one] |
| 135 | +``` |
| 136 | + |
| 137 | +#### Generated Folder Structure |
| 138 | +``` |
| 139 | +.spec-coding/features/vue-todo-app/ |
| 140 | +├── requirements.md # EARS-format requirements |
| 141 | +├── README.md # Feature Description |
| 142 | +├── design.md # Technical architecture |
| 143 | +└── tasks.md # Implementation checklist |
| 144 | +``` |
0 commit comments