spec

Convert vague product ideas into executable specs via a five-phase workflow.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands --skill spec-cloudofgeorge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/cloudofgeorge/AI-hands/tree/main/skills/gstack/spec
Command: npx skills add https://github.com/cloudofgeorge/AI-hands --skill spec-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Turn vague requirements or ideas into precise, executable specifications using a structured five-phase workflow, reducing ambiguity and rework in product and engineering planning.

Core Features & Use Cases

  • Five-phase spec-generation process that transforms user stories, PRDs, or ideas into concrete specs suitable for tickets and sprints.
  • Deterministic, replicable outputs that align engineering tasks with business goals.
  • Use Case: when a proposal lacks detail, run the spec workflow to produce a ready-to-work specification and GitHub backlog items.

Quick Start

Run /spec on a vague product idea to generate a precise implementation 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 executable engineering specs?

To turn vague product ideas into executable engineering specs, use a structured five-phase workflow that processes user stories and PRDs to produce deterministic, ready-to-work specifications aligned with business goals.

What is the best way to generate sprint-ready tickets from a rough PRD?

The best way to generate sprint-ready tickets from a rough PRD is to run a spec-generation process that transforms proposals lacking detail into concrete specifications suitable for GitHub backlog items.

How does the five-phase spec workflow handle product management requirements?

The five-phase spec workflow handles product management requirements by enforcing deterministic formatting and integrating planning with ticketing, ensuring replicable outputs that align engineering tasks with business goals.

Can I use this spec workflow for both user stories and engineering tasks?

Yes, you can use this spec workflow for both user stories and engineering tasks, as it is specifically applicable to product ideas, PRDs, and engineering tasks to produce concrete, executable specifications.

Does the generated spec integrate with existing planning and ticketing systems?

Yes, the generated spec integrates with planning and ticketing systems through its built-in support for gstack, allowing you to automatically produce GitHub backlog items from the finalized specifications.

When do I need to use a deterministic formatting process for software engineering planning?

You need a deterministic formatting process for software engineering planning when a proposal lacks detail, helping to reduce ambiguity and rework by producing replicable outputs from vague intents.