mcp-server-spec-driven-development — Prompt Files
Excerpt 1: generate-requirements Prompt (verbatim from src/server.ts)
server.registerPrompt(
"generate-requirements",
{
title: "Generate Requirements Document",
description: "Generate requirements.md using EARS format",
argsSchema: {
requirements: z.string().describe(
"High-level requirements of the application. Example: 'A Vue.js todo application with task creation, completion tracking, and local storage persistence'"
)
}
},
({ requirements }) => ({
messages: [{
role: "user",
content: {
type: "text",
text: `Based on below requirements, generate requirements.md using EARS format in 'specs' folder:\n\n${requirements}`
}
}]
})
);
Technique: MCP Prompt as wrapper — the framework wraps a simple string interpolation (requirements.md using EARS format) as a formal MCP prompt. This is the minimal viable implementation of prompt-as-protocol: the prompt itself contains one sentence plus the user's input, no more. No persona assignment, no chain-of-thought instruction, no output schema.
Excerpt 2: generate-design-from-requirements Prompt (verbatim)
server.registerPrompt(
"generate-design-from-requirements",
{
title: "Generate Design Document from Requirements Document",
description: "Generate design.md from requirements.md",
},
() => ({
messages: [{
role: "user",
content: {
type: "text",
text: `Based on specs/requirements.md, generate specs/design.md`
}
}]
})
);
Technique: Zero-shot file reference — the prompt contains only a file path reference. All intelligence is delegated to the connected AI tool (VS Code Copilot, Claude Code) to read the file, understand the format, and generate the next artifact. This is the most minimal possible prompt engineering.
Excerpt 3: generate-code-from-design Prompt (verbatim)
server.registerPrompt(
"generate-code-from-design",
{
title: "Generate Code from Design Document",
description: "Generate code from design.md"
},
() => ({
messages: [{
role: "user",
content: {
type: "text",
text: `Based on specs/design.md, generate code on the root folder`
}
}]
})
);
Technique: Implicit convention reliance — "generate code on the root folder" assumes the AI understands conventional project layout. No language specification, no framework hint, no output validation. Maximum simplicity, minimum guardrails.
Prompting Techniques Summary
- MCP Prompt as protocol wrapper — structured way to deliver pre-formatted user messages via MCP
- File reference chaining — each prompt references the output file of the previous stage
- Zero-shot with format hint — only "EARS format" in requirements prompt; rest is fully delegated
- Minimal intervention design — the framework intentionally does nothing except trigger the AI to work on a specific artifact