sdd-mcp-server 1.1.22 → 1.3.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -6,7 +6,7 @@
6
6
 
7
7
  A Model Context Protocol (MCP) server implementing Spec-Driven Development (SDD) workflows for AI-agent CLIs and IDEs like Claude Code, Cursor, and others.
8
8
 
9
- > **✅ v1.1.21 Update**: Resolved MCP server connection issues. Use global installation (`npm install -g`) instead of npx for reliable Claude Code integration.
9
+ > **✅ v1.3.0 Update**: Enhanced steering document generation with automatic static document creation and AI agent support. Includes Linus Torvalds code review guidelines, commit message standards, and universal AGENTS.md for cross-platform AI compatibility.
10
10
 
11
11
  ## 🚀 Quick Start
12
12
 
@@ -110,47 +110,58 @@ Once connected to your AI client, you can use these MCP tools:
110
110
 
111
111
  | Tool | Description | Usage |
112
112
  |------|-------------|--------|
113
- | `sdd-init` | Initialize new SDD project | Creates .kiro directory structure |
114
- | `sdd-requirements` | Generate requirements doc | Creates requirements.md from project analysis |
115
- | `sdd-design` | Create design specifications | Generates design.md with architecture |
116
- | `sdd-tasks` | Generate task breakdown | Creates tasks.md with implementation plan |
113
+ | `sdd-init` | Initialize new SDD project | Creates .kiro directory structure + AGENTS.md for cross-platform AI support |
114
+ | `sdd-requirements` | Generate context-aware requirements | Analyzes package.json and structure to create EARS-formatted requirements |
115
+ | `sdd-design` | Create project-specific design | Generates architecture docs based on actual tech stack and dependencies |
116
+ | `sdd-tasks` | Generate implementation breakdown | Creates tasks derived from real project structure and technology choices |
117
117
  | `sdd-implement` | Implementation guidelines | Provides implementation steering |
118
118
  | `sdd-status` | Check workflow progress | Shows current phase and approvals |
119
119
  | `sdd-approve` | Approve workflow phases | Mark phases as approved for progression |
120
120
  | `sdd-quality-check` | Code quality analysis | Linus-style 5-layer code review |
121
121
  | `sdd-context-load` | Load project context | Restore project memory and state |
122
122
  | `sdd-template-render` | Render templates | Generate files from templates |
123
+ | `sdd-steering` | Create/update steering docs | Analyzes project to generate product.md, tech.md, structure.md with real content + static linus-review.md, commit.md |
124
+ | `sdd-steering-custom` | Create custom steering docs | Add specialized guidance documents |
125
+ | `sdd-validate-design` | Design quality validation | Interactive GO/NO-GO design review |
126
+ | `sdd-validate-gap` | Implementation gap analysis | Analyze requirements vs codebase |
127
+ | `sdd-spec-impl` | Execute tasks with TDD | Kent Beck's Red-Green-Refactor methodology |
123
128
 
124
129
  ## 💡 Basic Workflow
125
130
 
126
- 1. **Initialize Project**
131
+ 1. **Initialize Project & Steering**
127
132
  ```
128
133
  Use sdd-init to create a new SDD project
134
+ Use sdd-steering to generate core steering documents
129
135
  ```
130
136
 
131
137
  2. **Generate Requirements**
132
138
  ```
133
- Use sdd-requirements to analyze and document requirements
139
+ Use sdd-requirements to analyze package.json and create context-aware requirements
140
+ Use sdd-validate-gap to analyze implementation feasibility
134
141
  ```
135
142
 
136
143
  3. **Create Design**
137
144
  ```
138
- Use sdd-design to generate technical architecture
145
+ Use sdd-design to generate architecture based on actual dependencies
146
+ Use sdd-validate-design for GO/NO-GO design review
139
147
  ```
140
148
 
141
149
  4. **Plan Tasks**
142
150
  ```
143
- Use sdd-tasks to break down implementation work
151
+ Use sdd-tasks to create implementation breakdown from real project structure
144
152
  ```
145
153
 
146
- 5. **Implement**
154
+ 5. **Implement with TDD**
147
155
  ```
148
- Use sdd-implement for implementation guidance
156
+ Use sdd-spec-impl to execute tasks with TDD methodology
157
+ Use sdd-quality-check for code review and analysis
149
158
  ```
150
159
 
151
- 6. **Quality Check**
160
+ 6. **Monitor & Manage**
152
161
  ```
153
- Use sdd-quality-check for code review and analysis
162
+ Use sdd-status to check workflow progress
163
+ Use sdd-approve to approve workflow phases
164
+ Use sdd-context-load to restore project memory
154
165
  ```
155
166
 
156
167
  ## ⚙️ Configuration
@@ -195,9 +206,12 @@ claude mcp add sdd "sdd-mcp-server"
195
206
  ## 🏗️ Key Features
196
207
 
197
208
  - **5-Phase SDD Workflow**: INIT → REQUIREMENTS → DESIGN → TASKS → IMPLEMENTATION
209
+ - **Context-Aware Generation**: Analyzes package.json, dependencies, and project structure for real content
210
+ - **EARS-Formatted Requirements**: Generate acceptance criteria based on actual npm scripts and dependencies
211
+ - **Architecture Analysis**: Technology stack detection and pattern recognition from real codebase
198
212
  - **Quality Enforcement**: Linus-style 5-layer code review system
199
213
  - **Multi-Language Support**: 10 languages with cultural adaptation
200
- - **Template Engine**: Handlebars-based file generation
214
+ - **Template Engine**: Handlebars-based file generation with project-specific data
201
215
  - **Plugin System**: Extensible architecture for custom workflows
202
216
  - **MCP Protocol**: Full compatibility with AI-agent CLIs and IDEs
203
217
 
@@ -3,6 +3,8 @@ import { ProjectService } from '../../application/services/ProjectService.js';
3
3
  import { WorkflowService } from '../../application/services/WorkflowService.js';
4
4
  import { TemplateService } from '../../application/services/TemplateService.js';
5
5
  import { QualityService } from '../../application/services/QualityService.js';
6
+ import { SteeringDocumentService } from '../../application/services/SteeringDocumentService.js';
7
+ import { CodebaseAnalysisService } from '../../application/services/CodebaseAnalysisService.js';
6
8
  import { LoggerPort } from '../../domain/ports.js';
7
9
  export interface SDDToolHandler {
8
10
  name: string;
@@ -14,8 +16,10 @@ export declare class SDDToolAdapter {
14
16
  private readonly workflowService;
15
17
  private readonly templateService;
16
18
  private readonly qualityService;
19
+ private readonly steeringService;
20
+ private readonly codebaseAnalysisService;
17
21
  private readonly logger;
18
- constructor(projectService: ProjectService, workflowService: WorkflowService, templateService: TemplateService, qualityService: QualityService, logger: LoggerPort);
22
+ constructor(projectService: ProjectService, workflowService: WorkflowService, templateService: TemplateService, qualityService: QualityService, steeringService: SteeringDocumentService, codebaseAnalysisService: CodebaseAnalysisService, logger: LoggerPort);
19
23
  getSDDTools(): SDDToolHandler[];
20
24
  private handleProjectInit;
21
25
  private handleProjectStatus;
@@ -23,4 +27,23 @@ export declare class SDDToolAdapter {
23
27
  private handleDesign;
24
28
  private handleTasks;
25
29
  private handleQualityCheck;
30
+ private handleSteering;
31
+ private handleSteeringCustom;
32
+ private generateProductSteering;
33
+ private generateTechSteering;
34
+ private generateStructureSteering;
35
+ private extractFeatures;
36
+ private generateTargetUseCase;
37
+ private generateValueProposition;
38
+ private generateTargetUsers;
39
+ private generateTechStack;
40
+ private generateDependencyList;
41
+ private generateArchitecturePatterns;
42
+ private generateQualityStandards;
43
+ private generateDirectoryStructure;
44
+ private generateNamingConventions;
45
+ private generateModuleOrganization;
46
+ private generateWorkflow;
47
+ private createStaticSteeringDocuments;
48
+ private createAgentsFile;
26
49
  }