skills.rest
ArvorCo
ArvorCoCOMMUNITY
Explore all skills by this author →
GitHub

specify

Convert natural language feature descriptions into structured SpecKit-style specifications.

96|5|Updated Jan 10, 2026
Search Tags:#documentation#TDD#specification#feature#user-stories#acceptance-criteria
One-click install
npx skills add https://github.com/ArvorCo/Relentless --skill specify-arvorco
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specify
Source: https://github.com/ArvorCo/Relentless/tree/main/.claude/skills/specify
Command: npx skills add https://github.com/ArvorCo/Relentless --skill specify-arvorco

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The specify skill converts a natural language feature description into a structured, testable feature specification, eliminating ambiguity and accelerating the design phase.

Core Features & Use Cases

  • Create complete feature specifications including title, description, routing preferences, acceptance criteria, and a generated spec file.
  • Follow SpecKit-style workflow (specify → plan → tasks → analyze → implement) to deliver incremental, verifiable features.
  • Produce ready-to-edit spec files in relentless/features/NNN-feature-name/spec.md ready for review and implementation.

Quick Start

Use the specify skill to generate a new feature specification from a natural language description. The tool will create the feature directory, produce spec.md, and prepare the next steps in the Relentless workflow.

Frequently Asked Questions about specify

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

FAQPage Schema
How do I turn natural language into testable feature specifications?▼

To turn natural language into testable feature specifications, you provide a plain text feature description and the tool generates a structured spec file containing user stories, Given/When/Then acceptance criteria, and TDD test strategy details.

What are acceptance criteria and how do they fit into TDD workflows?▼

Acceptance criteria define specific Given/When/Then conditions that a feature must satisfy. In TDD workflows, they establish the testable boundaries required to guide implementation and verify that the generated specification behaves as intended.

How do I generate a spec file from user stories for my development workflow?▼

You generate a spec file by inputting user stories as natural language. The system creates a ready-to-edit spec.md file in the relentless/features/NNN-feature-name/ directory, prepared for the next implementation phases.

Can I use natural language descriptions to define routing preferences and dependencies?▼

Yes, you can use natural language descriptions to define routing preferences and dependencies. The specification generation process captures these technical details alongside user stories to ensure full TDD readiness.

What is the best way to structure feature specifications for incremental delivery?▼

The best way to structure feature specifications for incremental delivery is to follow a SpecKit-style workflow that produces clearly named features, routing preferences, and testable acceptance criteria to guide verifiable implementation steps.

Related Skills

Explore More Software Engineering Skills→
asm0deyasm0dey
1

iikit-01-specify

Generate feature specifications from natural language descriptions with Git branching.

Community
Advanced
lofidonut3lofidonut3
2

speckit.tasks

Generate a dependency-ordered tasks document from Speckit design artifacts.

Community
Advanced
AsiaOstrichAsiaOstrich
70

forward-derivation

Generate BDD scenarios, TDD skeletons, and ATDD tables from SDD specifications.

Community
Intermediate
ImaginerLabsImaginerLabs

bmad-create-story

Generate structured dev-story Markdown files with guardrails and references.

Official
Advanced