skills.rest
burgebj
burgebjCOMMUNITY
Explore all skills by this author →
GitHub

spec

Transform user intent into executable specifications using a five-step method.

Updated Jun 4, 2026
Search Tags:#specification#issue tracking#git integration#backlog management#requirement engineering
One-click install
npx skills add https://github.com/burgebj/gstack --skill spec-burgebj
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/burgebj/gstack/tree/main/spec
Command: npx skills add https://github.com/burgebj/gstack --skill spec-burgebj

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, CLAUDE, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the challenge of turning broad intent into detailed, executable specifications quickly and accurately, through a structured, five-phase process.

Core Features & Use Cases

  • Requirement Specifying: Streamline the process of writing clear, actionable requirements.
  • Integration with Git: Automates the issue creation and merge processes.
  • Use Case: Ideal for developers who need to convert vague feature requests into detailed issue tickets that can be directly implemented.

Quick Start

Run the /spec command to create a new specification from your current work context.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn vague feature requests into executable specifications?▼

Executable specifications are created from loose user intent via a structured five-phase method, transforming broad feature requests into detailed, actionable requirement tickets for direct implementation.

Can I automate GitHub issue creation from my requirement engineering process?▼

GitHub issue creation is automated during the requirement engineering process by integrating Git workflows, converting finalized executable specifications directly into tracked issue tickets.

How does the five-phase specification method work with Claude Code agents?▼

The five-phase specification method leverages Claude Code agents and repository context, utilizing Bash, Read, Grep, Glob, and AskUserQuestion tools to systematically process and refine user intent into precise requirements.

Do I need Git and a gstack repository context to specify requirements?▼

Git and a gstack repository context are required dependencies to specify requirements efficiently, providing the necessary version control integration and environmental framework for the five-phase process.

What's the best way to manage backlog items from loose development ideas?▼

Backlog management from loose development ideas is handled by running a single command to initiate the five-step method, which processes current work context and outputs structured, executable specifications.

Are there limitations when converting broad intent into detailed issue tickets?▼

Converting broad intent into detailed issue tickets requires Claude Code agents and gstack repository context, meaning it cannot operate outside this specific environment or without proper Git integration.

Related Skills

Explore More Software Engineering Skills→
d0whc3rd0whc3r
2

speckit-git-initialize

Initialize a Git repository and create an initial commit.

Community
Intermediate
CapplequoppeCapplequoppe

create-github-pr

Create GitHub pull requests with synchronized branches via the GitHub CLI.

Community
Intermediate
reomgitreomgit

codex

Review code with pass/fail gates using Git repository context.

Community
Advanced
smarmen86smarmen86

spec

Generate executable GitHub issues from vague intent through a five-phase workflow.

Community
Advanced