smith-specify

Creates formal feature specifications from natural language descriptions.

50|8|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/ATTCKDigital/smith --skill smith-specify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: smith-specify
Source: https://github.com/ATTCKDigital/smith/tree/main/skills/smith-specify
Command: npx skills add https://github.com/ATTCKDigital/smith --skill smith-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating and maintaining detailed feature specifications is error-prone and time-consuming. This skill automates turning natural language feature descriptions into structured specs that can be directly planned and executed.

Core Features & Use Cases

  • Generates a complete feature specification from a natural language description, including YAML frontmatter and a templated spec body.
  • Automatically detects scope, identifies the primary system, and routes the spec to the correct system folder for collaboration.
  • Produces a built-in quality checklist, records assumptions, and flags clarifications to ensure the spec is verifiable and ready for planning.

Quick Start

Provide a natural-language feature description to smith-specify to generate a ready-to-run spec draft.

Frequently Asked Questions about smith-specify

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

FAQPage Schema
How do I create a feature specification from a natural language description?

To create a feature specification from a natural language description, input your text to automatically determine scope, identify the primary system, and generate a structured spec with YAML frontmatter and checklists.

What is the best way to structure product requirements for planning and validation?

Structuring product requirements for planning is best handled by generating a formal specification that includes a built-in quality checklist, records assumptions, and flags necessary clarifications to ensure verifiable tracking.

Does this feature specification tool automatically detect project scope and primary systems?

Yes, this feature specification tool automatically detects project scope and identifies the primary system, routing the generated specification to the correct system folder for team collaboration and structured handoffs.

Can I generate ready-to-track specs with built-in validation checklists?

Yes, you can generate ready-to-track specs that include built-in quality validation checklists, record working assumptions, and flag open clarifications to ensure the specification is fully ready for execution.

How do I prepare a feature description for automated spec generation?

To prepare a feature description for automated spec generation, provide a clear natural language summary of your intended feature, and the system will automatically structure it into a templated spec body with formal metadata.

What limitations exist when converting natural language feature descriptions into formal specs?

When converting natural language feature descriptions into formal specs, limitations include the system relying entirely on your initial text clarity, requiring flagged clarifications to resolve ambiguous scope or missing validation criteria before planning.