spec-kit-expert

Generate RFC 2119-compliant specifications with Gherkin scenarios and user stories.

156|21|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/anton-abyzov/specweave --skill spec-kit-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-kit-expert
Source: https://github.com/anton-abyzov/specweave/tree/main/.claude/skills/spec-kit-expert
Command: npx skills add https://github.com/anton-abyzov/specweave --skill spec-kit-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides clarity when evaluating development frameworks by offering deep expertise in spec-kit and performing dynamic comparisons against your current SpecWeave project, eliminating guesswork and ensuring informed decisions.

Core Features & Use Cases

  • On-Demand Gap Analysis: Compares your current SpecWeave implementation with spec-kit, identifying strengths, weaknesses, and unique features of each.
  • spec-kit Expertise: Explains any spec-kit concept, command, or workflow, answering "how does spec-kit handle X?" with detailed examples.
  • Strategic Recommendations: Advises which framework is best suited for specific use cases (e.g., greenfield SaaS, brownfield enhancement).
  • Use Case: Ask "Compare SpecWeave to spec-kit - what are the gaps?" and receive a fresh, detailed report highlighting differences in workflow, agent support, and documentation, tailored to your project's context.

Quick Start

Compare SpecWeave to spec-kit - what are the gaps?

Frequently Asked Questions about spec-kit-expert

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

FAQPage Schema
How do I compare spec-kit and SpecWeave to identify framework gaps?

Gap analysis between spec-kit and SpecWeave reveals differences in workflow, agent support, and documentation capabilities. This Skill performs dynamic comparison, highlighting which framework aligns with your project's requirements for specification writing, BDD adoption, and testable requirements documentation.

What is RFC 2119 keyword enforcement and why does it matter for specifications?

RFC 2119 keywords (MUST, SHOULD, MAY) enforce semantic precision in requirement documentation. This Skill applies RFC 2119 semantics to ensure unambiguous, testable specifications across spec-kit and SpecWeave implementations.

How do I write INVEST-compliant user stories with acceptance criteria?

INVEST criteria ensure user stories are Independent, Negotiable, Valuable, Estimable, Small, and Testable. This Skill generates INVEST-compliant user stories and delivers standard acceptance-criteria templates that pair with Gherkin-style scenario syntax for executable, specification-driven development.

What's the difference between Gherkin syntax and traditional acceptance criteria?

Gherkin syntax structures specifications as executable Given-When-Then scenarios, enabling BDD automation. This Skill generates both Gherkin-style scenarios and acceptance-criteria patterns, supporting teams transitioning from descriptive requirements to executable specifications.

When should I adopt spec-kit over SpecWeave for a new project?

Framework choice depends on greenfield vs. brownfield context, team BDD maturity, and documentation workflow needs. This Skill provides strategic recommendations on which framework suits specific use cases by comparing feature sets, agent support, and specification template capabilities.

What specification templates and patterns does this Skill provide?

Standard specification templates cover user stories, acceptance criteria patterns, RFC 2119-compliant requirements, and Gherkin scenario structures. Templates enforce testability and clarity across spec-kit and SpecWeave projects for consistent specification-driven development.