feature-spec

Guide structured interviews to document feature specs with Gherkin scenarios.

Updated Nov 1, 2025
One-click install
npx skills add https://github.com/nschneble/rails-superstack --skill feature-spec-nschneble
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-spec
Source: https://github.com/nschneble/rails-superstack/tree/main/.agents/skills/feature-spec
Command: npx skills add https://github.com/nschneble/rails-superstack --skill feature-spec-nschneble

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Guides users through a structured interview process to create complete feature specifications with Gherkin scenarios, edge cases, and PR breakdown.

Core Features & Use Cases

  • Discovery interview workflow that asks core questions before drafting specs
  • Generates a feature spec template and acceptance criteria aligned with the provided template
  • Helps convert requirements into user stories and PR-ready plans for handoff

Quick Start

Start the discovery interview by answering the questions to generate a complete feature specification.

Frequently Asked Questions about feature-spec

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

FAQPage Schema
How do I write a feature spec with Gherkin scenarios for a Rails application?

To write a feature spec with Gherkin scenarios for a Rails application, you can use a guided interview process that helps identify requirements, document edge cases, and generate a structured specification aligned to a feature template.

What is the best way to turn feature requirements into a PR breakdown?

Turning feature requirements into a PR breakdown is best handled through a discovery workflow that asks core questions, drafts user stories, and outputs a structured plan ready for review and handoff.

How do I document edge cases and acceptance criteria when defining a new feature?

You can document edge cases and acceptance criteria by running a clarification loop during a discovery interview, which systematically identifies gaps and produces a comprehensive specification with Gherkin scenarios.

Can I use a guided interview to generate user stories for my development team?

Yes, you can use a guided interview to generate user stories for your development team, as the process converts your answers into structured requirements and a PR-ready plan for direct handoff.

Do I need to prepare anything before starting the feature specification process?

Before starting the feature specification process, you only need a basic understanding of your intended feature; the guided interview will handle the requirements gathering, clarification loops, and final template generation.

Why should I use a structured discovery workflow instead of writing user stories directly?

A structured discovery workflow is preferable to writing user stories directly because it uses clarification loops to uncover missing edge cases and ensures the final specification is complete and PR-ready for handoff.