Specky

Initialize SDD Pipeline

sdd_init

Initializes a project for spec-driven development by creating the .specs directory, writing a CONSTITUTION.md skeleton, and setting up the state machine. Use as the first step in the SDD pipeline.

Instructions

Creates .specs/ directory, writes CONSTITUTION.md skeleton, and initializes the state machine. Call this first before any other SDD tool.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_name": "<project_name>"
    },
    "name": "sdd_init"
  }
}

Input Schema

Name	Required	Description	Default
`spec_dir`	No	Spec directory path (relative to workspace root)	.specs
`principles`	No	Project guiding principles
`constraints`	No	Project constraints
`project_name`	Yes	Project name in kebab-case

Schema Changelog

Changes observed during successful MCP inspections.

First observedv3.4.0-rc.14May 3, 2026

TDQS

A4/5.0

Behavior3/5

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

Annotations only indicate readOnlyHint=false, so description carries burden. It discloses creation/writes but does not specify if overwriting occurs, idempotency, or required permissions. This is adequate but not thorough.

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?

A single sentence for action plus a short usage note. No unnecessary words. Every part earns its place.

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

Completeness4/5

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

Given no output schema and simple init operation, the description covers core actions. Missing return value info, but not critical for comprehension. Adequate for the tool's simplicity.

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 coverage is 100% with adequate descriptions for all 4 parameters. The tool description does not add additional parameter meaning beyond the schema, so baseline 3 applies.

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

Purpose5/5

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

The description clearly states it creates .specs/ directory, writes CONSTITUTION.md skeleton, and initializes state machine. It distinguishes from 50+ sibling tools by being the only init tool, and explicitly says 'Call this first before any other SDD tool.'

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

Usage Guidelines4/5

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

Explicitly states 'Call this first before any other SDD tool,' providing clear usage context. It does not mention when not to use or alternatives, but the instruction is sufficient for an init tool.

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

Deploy Server