Specs Workflow MCP — Prompts
Source: src/tools/specWorkflowTool.ts
Technique: Tool description as instruction — the MCP tool's description field serves as the primary prompt, guiding the AI on when and how to invoke the tool.
{
title: 'Intelligent Specification Workflow Tool',
description: 'Manage intelligent writing workflow for software project requirements,
design, and task documents. Supports initialization, checking, skipping,
confirmation, and task completion operations (single or batch).',
annotations: {
progressReportingHint: true,
longRunningHint: true,
readOnlyHint: false,
idempotentHint: false
}
}
Notable technique: MCP annotations (progressReportingHint, longRunningHint) serve as behavioral hints to the AI client, setting expectations for tool execution characteristics.
Prompt 2: CLAUDE.md Integration Block (Recommended System Prompt)
Source: README.md
Technique: System prompt injection via CLAUDE.md — the README recommends this block be added to the AI's context, turning the MCP tool into a proactive workflow manager.
# Spec Workflow Usage Guidelines
## 1. Check Project Progress
When user mentions continuing previous project or is unsure about current progress,
proactively use: specs-workflow tool with action.type="check" and path="./specs"
## 2. Documentation Language
All spec workflow documents should be written in English consistently.
## 3. Documentation Directory
All spec workflow documents should be placed in ./specs directory.
## 4. Task Management
Always use the following to manage task progress:
specs-workflow tool with action.type="complete_task" and taskNumber="current task number"
Follow the workflow guidance to continue working until all tasks are completed.
## 5. Best Practices
- Proactive progress check: When user says "continue from last time", first use
check to see current status
- Language consistency: Use the same language throughout all project documents
Notable technique: The README provides a complete, copy-pasteable CLAUDE.md configuration block — the framework ships its own AI context injection recipe, not just a tool.
Prompt 3: User Invocation Examples
Source: README.md
Technique: Natural language invocation — the AI recognizes spec workflow intent from freeform user messages.
"Help me use spec workflow to create a user authentication system"
# → AI calls specs-workflow with action.type="init"
"Use spec workflow to check ./my-project"
# → AI calls specs-workflow with action.type="check" and path="./my-project"