Skip to main content
Glama

speckit_plan

Create technical plans for project specifications and implementation using guided prompts to structure development workflows.

Instructions

Create a technical plan

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNoAdditional context or requirement

Implementation Reference

  • The core handler function that executes the logic for the 'speckit_plan' tool. It builds a prompt message directing the LLM to use a template file and generate a technical plan.
    private async handlePlan(commandsPath: string, context?: string) {
        const extraContext = context ? `\nContext: '${context}'` : "";
        return {
            messages: [
                {
                    role: "user",
                    content: {
                        type: "text",
                        text: `Please read the planning template at 'commands/speckit.plan'[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.plan.xxx] [It's important. You must read it]. Analyze the current project to identify the technology stack. Then, using the template and the Context: '${extraContext}', create a technical plan.`,
                    },
                },
            ],
        };
    }
  • src/index.ts:206-207 (registration)
    The dispatch/registration case in the CallToolRequestSchema handler that routes 'speckit_plan' calls to the handlePlan function.
    case "speckit_plan":
        result = await this.handlePlan(commandsPath, args.context as string);
  • The tool definition in ListToolsRequestSchema response, including name, description, and input schema for 'speckit_plan'.
    {
        name: "speckit_plan",
        description: "Create a technical plan",
        inputSchema: {
            type: "object",
            properties: {
                context: {
                    type: "string",
                    description: "Additional context or requirement",
                },
            },
        },
    },
  • src/index.ts:107-108 (registration)
    Related dispatch for the prompt version 'speckit.plan' which also uses handlePlan (note the dot vs underscore).
    case "speckit.plan":
        return await this.handlePlan(commandsPath, args.context as string);
  • The prompt definition in ListPromptsRequestSchema, similar schema for 'speckit.plan'.
        name: "speckit.plan",
        description: "Create a technical plan",
        arguments: [
            {
                name: "context",
                description: "Additional context or requirement",
                required: false,
            },
        ],
    },
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Create' implies a write/mutation operation, but the description doesn't mention permissions needed, whether the plan is saved or temporary, what happens on failure, or any rate limits. It lacks essential behavioral context for a creation tool.

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

Conciseness5/5

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

The description is extremely concise at just three words with zero waste. It's front-loaded with the core action and resource, making it easy to parse quickly despite its brevity.

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

Completeness2/5

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

For a creation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what a 'technical plan' entails, what format it returns, whether it's stored or transient, or how it relates to sibling tools. The minimal description leaves too many contextual gaps.

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

Parameters3/5

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

Schema description coverage is 100% with one parameter ('context') fully documented in the schema. The description doesn't add any parameter-specific information beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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

Purpose3/5

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

The description 'Create a technical plan' clearly states the action (create) and the resource (technical plan), but it's vague about what constitutes a technical plan and doesn't differentiate from sibling tools like speckit_specify or speckit_tasks that might also involve planning-related activities. It provides basic purpose but lacks specificity.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like speckit_specify or speckit_implement. The description implies it's for creating plans, but doesn't specify context, prerequisites, or exclusions, leaving the agent to guess about appropriate usage scenarios.

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