spec

Convert vague product intent into executable specification documents and GitHub issues.

Updated Jul 21, 2025
One-click install
npx skills add https://github.com/robertzengcn/aiFetchly --skill spec-robertzengcn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/robertzengcn/aiFetchly/tree/main/.claude/skills/gstack/spec
Command: npx skills add https://github.com/robertzengcn/aiFetchly --skill spec-robertzengcn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the ambiguity of rough, unstructured product or feature ideas by turning them into clear, actionable specification documents that development teams can execute without confusion or repeated clarification.

Core Features & Use Cases

  • 5-Phase Spec Workflow: Follows a structured 5-step process to refine vague intent into detailed, executable specs with clear requirements, acceptance criteria, and implementation guidance.
  • Automated Issue Creation: Files the finished spec directly as a GitHub issue, backlog item, or ticket, integrated with your existing project tracking workflow.
  • Implementation Handoff: Optionally spawns a Claude Code agent in a fresh worktree to start building the feature, and integrates with /ship to automatically close the source issue once the work is merged.
  • Use Case: If your team has a rough idea for a new bulk email personalization feature for aiFetchly, use this Skill to turn that one-sentence thought into a fully scoped, ready-to-build spec and GitHub issue in minutes.

Quick Start

Use the spec skill to turn my rough idea for adding Yandex Maps lead export to the local business finder into a detailed GitHub issue with clear acceptance criteria and implementation steps.

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 development specs?

To turn vague ideas into executable specs, you apply a structured five-phase drafting process that refines unstructured product intent into detailed specification documents with clear requirements and acceptance criteria. This eliminates implementation ambiguity and aligns cross-functional teams before coding begins.

Can I automatically create GitHub issues from my project planning specs?

Yes, you can automatically file finished specification documents directly as GitHub issues. This integrates your spec generation workflow with backlog management, populating your issue tracking system with fully scoped, ready-to-build project tickets without manual data entry.

What is the best way to structure backlog grooming for new feature requests?

The best way to structure backlog grooming is using a multi-phase refinement workflow that transforms rough feature requests into standardized project artifacts. This ensures every backlog item contains clear implementation guidance and actionable requirements for the development team.

Does spec generation work directly with my existing GitHub issues workflow?

Yes, spec generation works directly with your existing GitHub issues workflow by automatically creating tickets from finalized documents. It bridges product planning and issue tracking, seamlessly feeding scoped requirements into your current backlog management environment.

How do I draft requirement documents that eliminate implementation ambiguity for developers?

You draft unambiguous requirement documents by passing rough feature intent through a structured scoping workflow. This generates executable specification documents containing precise acceptance criteria and implementation guidance, ensuring developers know exactly what to build.