spec

Transform user intent into a technical specification across five phases.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/greencm/gstuck --skill spec-greencm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/greencm/gstuck/tree/main/output/gstack/spec
Command: npx skills add https://github.com/greencm/gstuck --skill spec-greencm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of turning abstract requirements into a detailed, executable specification, simplifying the transition from intent to implementation.

Core Features & Use Cases

  • Phase-Based Workflow: Breaks down the specification process into five distinct phases for clarity and thoroughness.
  • Trigger Keywords: Recognizes a variety of keywords (e.g., 'spec this out', 'file an issue') to initiate the specification process.
  • Use Case: Ideal for project managers or developers who need to clarify project requirements and create actionable issue tickets.

Quick Start

Trigger the spec skill with the command "spec this out".

Frequently Asked Questions about spec

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

FAQPage Schema
How do I transform a vague project intent into a precise technical specification?

To transform vague intent into a precise technical specification, you can trigger a five-phase workflow using the command 'spec this out'. This process breaks down abstract requirements into a detailed, executable specification for issue tracking.

What is the best way to write specifications for issue tracking workflows?

Writing specifications for issue tracking workflows is best handled by a phase-based process that clarifies project requirements. It simplifies the transition from abstract intent to detailed, actionable issue tickets.

How do I file an issue from a rough project idea?

To file an issue from a rough project idea, initiate the specification process using trigger keywords like 'file an issue'. The workflow then converts your abstract requirements into a structured, actionable ticket.

Does the specification workflow support spawning Claude Code agents in a worktree?

Yes, the specification workflow supports spawning Claude Code agents within a worktree. It utilizes standard tools like Bash, Read, Grep, Glob, and AskUserQuestion to process user input and generate the final specification.

Can I use this phase-based specification process for project management tasks?

Yes, you can use this phase-based specification process for project management tasks. It operates within the context of project management workflows to help project managers clarify requirements and create actionable issues.

What are the limitations of using a five-phase approach for specification writing?

The five-phase approach for specification writing requires user input at each stage to proceed and relies on standard shell and file operations. It is designed for refining abstract requirements rather than generating code directly.