Skip to main content
Glama

speckit_tasks

Generate structured task lists for project specifications and implementation phases using guided prompts.

Instructions

Generate task list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The core handler function for the 'speckit_tasks' tool. It returns a structured prompt message that instructs the LLM to read a task template file and generate a list of actionable tasks based on the technical plan.
    private async handleTasks(commandsPath: string) {
        return {
            messages: [
                {
                    role: "user",
                    content: {
                        type: "text",
                        text: `Please read the task breakdown template at 'commands/speckit.tasks'[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.tasks.xxx] [It's important. You must read it]. Use this template to break down the technical plan into a list of actionable tasks.`,
                    },
                },
            ],
        };
    }
  • src/index.ts:171-177 (registration)
    Registration of the 'speckit_tasks' tool in the MCP server's tools list, including name, description, and empty input schema.
        name: "speckit_tasks",
        description: "Generate task list",
        inputSchema: {
            type: "object",
            properties: {},
        },
    },
  • Input schema definition for the 'speckit_tasks' tool, which accepts an empty object (no parameters).
    inputSchema: {
        type: "object",
        properties: {},
    },
  • src/index.ts:209-211 (registration)
    Dispatch/registration case in the tool request handler switch statement that routes 'speckit_tasks' calls to the handleTasks method.
    case "speckit_tasks":
        result = await this.handleTasks(commandsPath);
        break;
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Generate task list' implies a creation or output operation but offers no details on what the tool does beyond that—no information on permissions, side effects, rate limits, or output format. This is inadequate for a tool with zero annotation coverage.

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

Conciseness3/5

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

The description is a single phrase, 'Generate task list', which is concise but under-specified. While it avoids unnecessary words, it fails to provide essential context, making it inefficient in conveying useful information rather than being appropriately sized.

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?

Given the lack of annotations, no output schema, and a vague description, the description is incomplete. It does not compensate for the missing structured data, leaving the agent with insufficient information to understand the tool's behavior, purpose, or usage in the context of its siblings.

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 input schema has 0 parameters with 100% coverage, meaning no parameters are documented in the schema. The description does not add parameter details, which is appropriate since there are none. A baseline score of 4 is applied for zero parameters, as no compensation is needed for missing parameter semantics.

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 'Generate task list' restates the tool name 'speckit_tasks' in slightly different words, making it tautological. It lacks specificity about what kind of tasks are generated, for what purpose, or what resources are involved, failing to distinguish it from potential sibling tools like speckit_plan or speckit_implement.

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 no guidance on when to use this tool versus alternatives. There is no mention of context, prerequisites, or exclusions, and it does not reference any sibling tools, leaving the agent with no basis for selecting this tool appropriately.

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