spec

Convert vague feature intent into a precise, executable specification and GitHub issue.

Updated Aug 9, 2026
One-click install
npx skills add https://github.com/raghavbadhwar/rstack --skill spec-raghavbadhwar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/raghavbadhwar/rstack/tree/main/spec
Command: npx skills add https://github.com/raghavbadhwar/rstack --skill spec-raghavbadhwar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough idea or verbal request into a well-structured, backlog-ready specification is time-consuming and often produces ambiguous tickets. This Skill guides an AI agent through a five-phase process that transforms vague intent into a precise, executable spec, files it as a GitHub issue, and optionally spawns a coding agent in a fresh worktree to implement it. ## Core Features & Use Cases - Five-phase spec authoring: Walks the user from raw intent through structured decision briefs (via AskUserQuestion) to a complete, unambiguous specification. - GitHub issue filing: Files the finished spec as an issue and integrates with the /ship workflow so the source issue closes automatically on merge. - Agent handoff: Optionally spawns a Claude Code agent in a fresh git worktree to execute the spec, with session-kind detection for interactive, headless, and spawned runs. - Use Case: A product manager says "spec this out" for a new onboarding flow. The Skill asks clarifying decisions, writes the spec, files the GitHub issue, and hands it off for implementation. ## Quick Start Ask the agent to spec out your feature idea, for example by saying "spec this out: add team invite links to the settings page".

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn a feature idea into a GitHub issue with an AI agent?▼

Invoke the spec skill with a phrase like "spec this out" or "make this a GitHub issue". It walks you through structured decision questions, writes a complete specification, and files it as a GitHub issue ready for implementation.

What triggers the spec skill in gstack?▼

The skill activates on phrases such as "spec this out", "file an issue", "write up a ticket", "turn this into an issue", "make this a GitHub issue", or "turn this into a backlog item".

Can the spec skill hand off work to a coding agent automatically?▼

Yes. After filing the issue, the skill can optionally spawn a Claude Code agent in a fresh git worktree to implement the spec. The /ship workflow then closes the source issue automatically when the change merges.

Does the spec skill work in headless or CI environments?▼

It detects the session kind (interactive, headless, or spawned) from the preamble. In headless sessions where AskUserQuestion is unavailable, the workflow blocks rather than guessing; in spawned sessions it auto-chooses recommended options.

What happens if the interactive question tool is unavailable during spec authoring?▼

The skill falls back based on session type: interactive sessions render the decision brief as prose and wait for a typed reply, headless sessions stop with a BLOCKED status, and spawned sessions auto-select the recommended option.