tool-spec-generator

Convert vague tool concepts into actionable specifications with a frontmatter-driven template.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cautiouskurns/Blood-and-Gold --skill tool-spec-generator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tool-spec-generator
Source: https://github.com/cautiouskurns/Blood-and-Gold/tree/main/.claude/skills/tool-spec-generator
Command: npx skills add https://github.com/cautiouskurns/Blood-and-Gold --skill tool-spec-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams quickly convert vague tool ideas into precise, actionable specifications, ensuring alignment before development.

Core Features & Use Cases

  • Generate concise tool specs for editor plugins, standalone utilities, and CLI tools.
  • Provide structured templates, MVP definitions, and clear success criteria.
  • Use cases include planning a new tool, documenting a utility, or scoping an editor plugin.

Quick Start

Say "I need a tool spec for [tool name]" and follow the guided prompts to fill in the template, then save the final spec to docs/tools/[tool-name]-spec.md.

Frequently Asked Questions about tool-spec-generator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a tool specification for an editor plugin?▼

A tool specification for an editor plugin is generated by guiding you through discovery and scoping to create a concise, frontmatter-driven template that defines MVP features and success criteria.

What is the best way to document a CLI tool idea before development?▼

Documenting a CLI tool idea requires generating a precise specification that enforces a structured template, capturing requirements and MVP definitions to ensure team alignment before coding.

How do I scope an MVP for a standalone utility?▼

Scoping an MVP for a standalone utility involves defining clear success criteria and actionable specifications through a guided discovery process, ensuring the core features are precise and concise.

Does this spec generator save files to a specific documentation directory?▼

Yes, the spec generator saves the final specification directly to the documentation directory, outputting a frontmatter-driven markdown file at docs/tools/[tool-name]-spec.md.

Can I use this to create documentation templates for multiple tool types?▼

Yes, you can create documentation templates for multiple tool types, as the guided prompts and structured specification process explicitly supports editor plugins, standalone utilities, and CLI tools.