spec

Transform vague ideas into backlog-ready specs with GitHub issues.

5|Updated Apr 24, 2026
One-click install
npx skills add https://github.com/timurgaleev/vibestack --skill spec-timurgaleev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/timurgaleev/vibestack/tree/main/skills/spec
Command: npx skills add https://github.com/timurgaleev/vibestack --skill spec-timurgaleev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague product ideas into backlog-ready, precise specifications that can be acted on.

Core Features & Use Cases

  • Phase-based interrogation to clarify goals, requirements, acceptance criteria, and risks.
  • Automatic creation of a GitHub issue and an archival record for traceability.
  • Optional agent spawn to drive implementation in a dedicated worktree.

Quick Start

Provide your initial request and let the spec tool guide you through interrogation to a concrete backlog-ready spec.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I turn vague product ideas into backlog-ready engineering specs?

Creating precise engineering specs from vague requests involves a phase-based interrogation workflow that extracts goals, acceptance criteria, and risks, then outputs a structured specification ready for immediate backlog integration.

How do I automate GitHub issue creation from product specifications?

Automating GitHub issue creation from product specifications is achieved through a workflow that generates the issue automatically once the interrogation phases finalize the requirements, ensuring full traceability via an archival record.

What is the best way to ensure traceability for software engineering backlog issues?

The best way to ensure traceability for backlog issues is to generate an archival record alongside the GitHub issue during spec finalization, linking the original vague intent directly to the actionable engineering requirements.

Can I spawn an agent to drive implementation directly from a generated spec?

Yes, you can optionally spawn an agent to drive implementation directly from the generated spec, which operates within a dedicated worktree to execute the actionable requirements defined during the interrogation phase.

What are the limitations of using automated spec generation for software planning?

Automated spec generation requires active participation during the phase-based interrogation to accurately define goals and risks, meaning it cannot fabricate missing context and relies on user input to produce a precise, backlog-ready output.