spec-issues-create

Generate GitHub issue drafts from spec files with Jinja2 templates.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/srnnkls/tropos --skill spec-issues-create
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-issues-create
Source: https://github.com/srnnkls/tropos/tree/main/skills/spec-issues-create
Command: npx skills add https://github.com/srnnkls/tropos --skill spec-issues-create

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

Generate structured GitHub issue drafts directly from spec documents to streamline tracking and execution.

Core Features & Use Cases

  • Automated generation of Initiative, Feature, and Task drafts from specs located under ./specs.
  • Template-based YAML frontmatter for gh CLI-based issue creation and easy cross-linking.
  • Drafts organized under drafts/issues and ready for review and publishing.

Quick Start

Place your spec documents under ./specs, then run the skill to generate drafts and use the generated create-issue script to publish them.

Frequently Asked Questions about spec-issues-create

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

FAQPage Schema
How do I generate GitHub issues from spec documents?

To generate GitHub issues from spec documents, place your files under the ./specs directory. The skill reads YAML frontmatter to automatically create Initiative, Feature, and Task drafts organized under drafts/issues for subsequent publishing.

Can I use gh CLI to automate cross-linking sub-issues from drafts?

Yes, you can use the gh CLI to automate cross-linking sub-issues. The skill generates a creation script (scripts/create-issue.sh) that uses gh to publish issue drafts and links sub-issues accordingly based on YAML frontmatter.

What is the best way to structure spec directories for automated issue creation?

The best way to structure spec directories for automated issue creation is placing files under ./specs. The skill processes these spec documents to generate structured initiative, feature, and task drafts ready for review and publishing.

Do I need YAML frontmatter to create initiative and feature drafts?

Yes, you need YAML frontmatter to create initiative and feature drafts. The skill reads this YAML frontmatter from spec documents to populate templates for gh CLI-based issue creation and easy cross-linking of sub-issues.

How does template-based issue generation work with spec files?

Template-based issue generation works by reading YAML frontmatter from spec files under ./specs to populate templates. It then generates a creation script that uses the gh CLI to publish the organized drafts as structured GitHub issues.

What are the limitations of using generated scripts to publish GitHub issue drafts?

The generated script for publishing GitHub issue drafts relies entirely on the gh CLI and requires a metadata checklist for GitHub configuration. Drafts are organized under drafts/issues and need subsequent GH CLI processing to publish.