create-spec

Convert accepted reports into implementation-ready GitHub spec issues.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill create-spec-gittower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-spec
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/create-spec
Command: npx skills add https://github.com/gittower/git-flow-next --skill create-spec-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires Read, Grep, Glob, Write, Bash, Agent, mcp__github__get_issue, mcp__github__search_issues, mcp__github__create_issue, mcp__github__update_issue, mcp__github__add_issue_comment.

What problem does it solve?

This Skill helps you convert an accepted bug report, feature request, concept, or idea into a clear, implementation-ready spec issue without jumping straight into coding.

Core Features & Use Cases

  • Issue-to-spec conversion: Drafts a structured spec from an existing GitHub issue or triaged report.
  • Concept-to-spec creation: Turns a user’s idea into a reviewable specification from scratch when no issue exists yet.
  • Research and validation workflow: Guides the drafting process with repository research, Codex review, and acceptance gating before posting to GitHub.
  • Use case: A maintainer receives a vague feature request and uses this Skill to produce a detailed spec with goals, expected behavior, test scenarios, and scope boundaries.

Quick Start

Ask the assistant to create a spec issue from a triaged report, concept, or GitHub issue number.

Frequently Asked Questions about create-spec

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

FAQPage Schema
How do I convert a vague GitHub issue into an implementation-ready spec?

To convert a vague GitHub issue into an implementation-ready spec, the Skill researches the local repository and drafts a structured specification with goals, expected behavior, test scenarios, and scope limits before posting it back to GitHub.

What is the best way to create a feature request spec from scratch?

Creating a feature request spec from scratch involves turning a user's concept into a reviewable specification through repository research, Codex review, and acceptance gating to ensure the spec is clear, testable, and ready for acceptance.

Can I use GitHub issue triage to generate detailed test scenarios for bug reports?

Yes, GitHub issue triage can generate detailed test scenarios for bug reports by inspecting the local repository context and applying a Codex-gated review to produce a structured, implementation-ready spec issue.

Does this workflow require a GitHub issue number to start drafting a specification?

No, this workflow does not require a GitHub issue number to start drafting a specification, as it can turn a user's idea or concept into a reviewable specification from scratch even when no issue exists yet.

Why should I generate a spec issue before starting actual code implementation?

Generating a spec issue before code implementation ensures the report is clear, testable, and ready for acceptance by establishing scope boundaries and expected behavior, which prevents jumping straight into unstructured coding.

What limitations exist when converting accepted reports into structured spec issues?

A key limitation is that the conversion requires GitHub issue context and local repository inspection, meaning it cannot draft accurate scope boundaries or test scenarios without access to the relevant codebase and issue data.