skills.rest
dmae97
dmae97COMMUNITY
Explore all skills by this author →
GitHub

speckit-specify

Generate feature specifications from natural language descriptions for spec-kit projects.

130|14|Updated Apr 30, 2026
Search Tags:#requirements#feature specification#product planning#quality validation#extension hooks#testable criteria#specification templates
One-click install
npx skills add https://github.com/dmae97/oh-my-kimi --skill speckit-specify-dmae97
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: speckit-specify
Source: https://github.com/dmae97/oh-my-kimi/tree/main/templates/skills/kimi/speckit-specify
Command: npx skills add https://github.com/dmae97/oh-my-kimi --skill speckit-specify-dmae97

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the ambiguity and back-and-forth of turning a natural-language feature idea into a structured, testable product specification that teams can plan and deliver.

Core Features & Use Cases

  • Feature specification generation: Converts a user’s feature description into a complete spec ready for planning.
  • Validation and readiness checks: Runs a structured quality checklist and iterates (up to 3 times) to improve spec completeness and testability.
  • Optional extensibility hooks: Supports before/after extension hooks defined in .specify/extensions.yml to integrate git branching or other project-specific automation.

Quick Start

Run the /speckit-specify command with your feature description to create a new spec directory and a ready-to-review spec file.

Frequently Asked Questions about speckit-specify

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

FAQPage Schema
How do I turn a feature idea into a testable specification?▼

To turn a feature idea into a testable specification, provide a natural language feature description to generate a structured spec with required template sections, stakeholder-friendly details, and validation checklist criteria.

What is the best way to structure feature specifications for product planning?▼

The best way to structure feature specifications for product planning is using required template sections within a specs/ directory, ensuring the final document is testable and ready for delivery team review.

Can I automate git branching when generating feature specifications?▼

Yes, you can automate git branching during feature specification generation by configuring before/after extension hooks in the .specify/extensions.yml file to trigger project-specific automation.

How does quality validation work for feature specifications?▼

Quality validation works by applying a structured checklist to the feature specification, iterating up to three times to automatically fix completeness issues and ensure all testable criteria are met.

Do I need a specific project structure to generate feature specifications?▼

Yes, you need a spec-kit style project structure where specifications live under a specs/ directory, allowing the tool to persist the resolved feature directory path to .specify/feature.json.

What happens to the feature directory path after specification generation?▼

After specification generation, the resolved feature directory path is persisted to the .specify/feature.json file, enabling subsequent post-hook automation and downstream project tracking.

Related Skills

Explore More Product & Management Skills→
intent-integrity-chainintent-integrity-chain
47

iikit-01-specify

Create structured feature specifications from natural language descriptions.

Official
Basic
jmanhypejmanhype
24

spec-kit-workflow

Implement Spec Kit workflow phases and generate project artifacts.

Community
Basic
lync-cyberlync-cyber
133

task-decomp

Decompose architecture and UI specifications into implementation tasks with testable acceptance criteria.

Community
Advanced
nsheapsnsheaps
3

Spec Writing

Produce iterative product specifications and prioritized user stories from seed inputs.

Community
Intermediate