Specky

Generate Operational Runbook

sdd_generate_runbook

Generates an operational runbook covering deployment, monitoring, troubleshooting, and rollback procedures from specifications.

Instructions

Generates an operational runbook with deployment, monitoring, troubleshooting, and rollback procedures. Writes to docs/runbook-{feature}.md.

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": {
      "feature_number": "<feature_number>"
    },
    "name": "sdd_generate_runbook"
  }
}

Input Schema

Name	Required	Description	Default
`spec_dir`	No	Spec directory.	.specs
`feature_number`	Yes	Zero-padded feature number.

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.4/5.0

Behavior2/5

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

Annotations are all false, so description carries full burden. It mentions generating and writing a file but lacks details on idempotency (overwrite vs. append), side effects, or prerequisites. Minimal behavioral disclosure.

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 a single sentence that efficiently conveys purpose and output. No unnecessary words or redundancy.

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?

No output schema exists, but the description does not clarify what the tool returns (e.g., confirmation, file path). It also omits behavior when the target file already exists. Incomplete for a file-generating tool.

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% and both parameters are described in the schema. The description adds no extra semantic information beyond what is already in the schema.

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 generates an operational runbook with specific sections (deployment, monitoring, troubleshooting, rollback) and specifies the output file pattern. This distinguishes it from sibling generation tools like sdd_generate_docs.

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

Usage Guidelines3/5

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

The description implies usage for creating runbooks for features but provides no explicit guidance on when to use this tool versus alternatives like sdd_generate_docs or sdd_generate_api_docs. No when-not or alternative examples.

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

Deploy Server