Skip to main content
Glama

speckit_implement

Execute implementation tasks for project specifications and workflows through guided prompts covering planning, tasks, and implementation phases.

Instructions

Execute implementation

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler function that executes the 'speckit_implement' tool. It returns a standardized message prompting the language model to read and adhere to the 'commands/speckit.implement' guidelines file for implementation tasks.
    // 处理 Implement (实施) 相关的逻辑
    private async handleImplement(commandsPath: string) {
        return {
            messages: [
                {
                    role: "user",
                    content: {
                        type: "text",
                        text: `Please read the implementation guidelines at 'commands/speckit.implement'[Note that if this file exists, it is generally in the current directory's commands/ directory,Scan this folder directly to obtain it,And the suffixes of each project are not consistent: speckit.implement.xxx] [It's important. You must read it]. Follow these guidelines to execute the implementation tasks.`,
                    },
                },
            ],
        };
    }
  • src/index.ts:178-185 (registration)
    Registration of the 'speckit_implement' tool in the ListToolsRequestSchema handler, including name, description, and empty input schema (no arguments required).
    {
        name: "speckit_implement",
        description: "Execute implementation",
        inputSchema: {
            type: "object",
            properties: {},
        },
    },
  • Input schema definition for the 'speckit_implement' tool: an empty object, indicating no input parameters are required.
    inputSchema: {
        type: "object",
        properties: {},
    },
  • Dispatch logic in the CallToolRequestSchema handler's switch statement that routes 'speckit_implement' calls to the handleImplement method.
    case "speckit_implement":
        result = await this.handleImplement(commandsPath);
        break;
Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Execute implementation' suggests a potentially destructive or state-changing action, but the description provides no information about what gets executed, whether it requires specific permissions, what side effects occur, or what the expected outcome is. This leaves critical behavioral aspects completely undocumented.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

While 'Execute implementation' is extremely brief, this represents under-specification rather than effective conciseness. The two-word description fails to provide necessary context and doesn't earn its place by adding meaningful value. True conciseness balances brevity with information density, which this description lacks.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with no annotations, no output schema, and sibling tools suggesting a workflow context, the description is completely inadequate. It doesn't explain what 'implementation' means in this context, what gets executed, what the expected outcome is, or how this fits with the other speckit tools. The description fails to provide the minimal context needed for effective tool selection.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, and the schema description coverage is 100% (though there are no parameters to describe). In this specific case, the description doesn't need to compensate for missing parameter documentation since there are no parameters. The baseline for zero parameters with full schema coverage is 4, as there's no parameter semantics burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Execute implementation' is tautological - it essentially restates the tool name 'speckit_implement' without providing meaningful clarification. While 'execute' is a verb, it doesn't specify what is being implemented, for whom, or what resources are involved. Compared to sibling tools like 'speckit_plan' and 'speckit_specify', this description fails to distinguish what makes this tool unique.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides absolutely no guidance about when to use this tool versus the sibling tools (speckit_constitution, speckit_plan, speckit_specify, speckit_tasks). There's no indication of the workflow sequence, prerequisites, or appropriate contexts for implementation versus planning or specification. Users must guess when this tool is appropriate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/anyiba/spec-kit-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server