spec

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

Updated May 22, 2026
One-click install
npx skills add https://github.com/kitfunso/claude-config --skill spec-kitfunso
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/kitfunso/claude-config/tree/main/skills/spec
Command: npx skills add https://github.com/kitfunso/claude-config --skill spec-kitfunso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough idea or verbal request into a well-structured, backlog-ready specification is slow and inconsistent. This Skill guides you through a five-phase process that transforms vague intent into a precise, executable spec and files it as a GitHub issue. ## Core Features & Use Cases - Five-phase spec workflow: Progressively refines raw intent into a complete, actionable specification with structured decision points. - GitHub issue filing: Files the finished spec as an issue and can optionally spawn a Claude Code agent in a fresh worktree to implement it. - Structured decision briefs: Uses AskUserQuestion decision briefs with recommendations, completeness scores, and trade-off analysis at each key choice. - Use Case: You say "spec this out" for a new onboarding flow. The Skill interviews you through structured decisions, writes the spec, files it as a GitHub issue, and hands it off so /ship can close the issue on merge. ## Quick Start Ask the AI to spec out your feature idea and file it as a GitHub issue by saying "spec this out" or "turn this into a backlog item".

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?▼

Invoke the spec skill with a phrase like "spec this out" or "make this a GitHub issue". It walks you through a five-phase refinement workflow, then files the resulting specification as a GitHub issue ready for implementation.

What is a backlog-ready spec and how do I write one?▼

A backlog-ready spec is a precise, executable description of work that an engineer or agent can implement without further clarification. This skill produces one by guiding you through structured decision briefs with recommendations and trade-off analysis.

Can the spec skill spawn an agent to implement the issue?▼

Yes. After filing the issue, the skill can optionally spawn a Claude Code agent in a fresh git worktree to work on it, and the /ship skill can close the source issue automatically when the change merges.

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

Yes, but behavior changes by session kind. In headless sessions it blocks when interactive questions are unavailable; in spawned sessions it auto-chooses recommended options and reports results as prose instead of prompting.

What happens when AskUserQuestion is unavailable during spec?▼

The skill follows a documented fallback: spawned sessions auto-choose the recommended option, headless sessions stop as BLOCKED, and interactive sessions render the decision brief as prose and wait for a typed reply.