gti-spec

Set up Git worktrees and generate Gherkin feature files and spec.md documents.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/CodeMachine0121/gti-agent-cycle-skill --skill gti-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gti-spec
Source: https://github.com/CodeMachine0121/gti-agent-cycle-skill/tree/main/skills/gti-spec
Command: npx skills add https://github.com/CodeMachine0121/gti-agent-cycle-skill --skill gti-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the initial setup and specification phase of a BDD/TDD workflow, ensuring features are clearly defined before implementation begins.

Core Features & Use Cases

  • Environment Setup: Creates isolated Git worktrees and feature branches.
  • Requirement Elicitation: Guides users through defining happy paths, alternative flows, and failure conditions.
  • Spec Generation: Produces Gherkin .feature files and spec.md documents.
  • Use Case: When starting a new feature like "user profile update," this Skill will set up a dedicated branch, help you brainstorm all possible scenarios (successful update, invalid data, etc.), and generate the corresponding Gherkin and spec files for review.

Quick Start

Use the gti-spec skill to start defining a new feature.

Frequently Asked Questions about gti-spec

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

FAQPage Schema
How do I generate Gherkin feature files for TDD workflows?

To generate Gherkin feature files for TDD workflows, you use a specification tool that elicits requirements and outputs structured `.feature` files. This ensures features are clearly defined before implementation begins.

What is the best way to set up isolated Git environments for feature branches?

Setting up isolated Git environments for feature branches is best handled using Git worktrees. This creates an isolated workspace for your feature, ensuring parallel development without interfering with the main branch.

How do I elicit BDD requirements for happy paths and failure conditions?

Eliciting BDD requirements for happy paths and failure conditions requires structured questioning. A guided specification process helps you brainstorm scenarios like successful updates and invalid data collaboratively.

Can I use Git worktrees to automate BDD specification generation?

Yes, you can use Git worktrees to automate BDD specification generation by combining environment setup with requirement elicitation. This yields Gherkin `.feature` files and `spec.md` documents ready for review.

Does this specification approach work without existing dependencies?

Yes, this specification approach works without existing dependencies. The environment setup is self-contained, requiring only Git to create the worktrees and branches needed for isolated feature development.