Does it provide naming conventions for different components?

Yes, it provides specific string formats for various types, such as '[EPIC]: Strategic outcome' or 'Component: What's broken' for bugs.

Can it help link related work together?

Absolutely. It defines specific relationship patterns, such as linking Stories to parent Epics using 'Towards #XXX' and ensuring Tasks are connected to Stories.

What specific issue types are supported by this skill?

The skill supports 13 unique types including Epic, Story, Task, Bug, Postmortem, Discovery, Request, Feature, Rock, Recurring, Operational, Note, and Experiment.

How does this skill improve issue quality?

It enforces the '3 C's' standard (Clear, Complete, Connected) and requires specific sections like Motivation, Outcome, and Acceptance Criteria depending on the issue type.

Giant Swarm Issue Standards

Name: Giant Swarm Issue Standards
Author: giantswarm

bygiantswarm

0•

コラボレーションツール

Standardizes the creation and management of GitHub issues according to Giant Swarm's proven project management patterns.

This skill equips Claude with the specific structural and naming conventions used by Giant Swarm for professional project management. It provides comprehensive guidance on 13 distinct issue types—ranging from strategic Epics and Rocks to tactical Tasks and Bugs—ensuring all tickets are clear, complete, and properly connected within the team's workflow. By following these patterns derived from real-world data, users can eliminate vague documentation, maintain consistent naming across components, and ensure every issue includes necessary acceptance criteria and team context.

主な機能

01Defines 13 specific issue types with required structural sections and durations

02Identifies and prevents common anti-patterns like vague titles or missing labels

03Outlines specific relationship mapping between Epics, Stories, and Tasks

04Enforces standardized naming patterns for Epics, Bugs, and Discoveries

05Provides guidelines for maintaining the '3 C's' (Clear, Complete, Connected) quality standards

060 GitHub stars

ユースケース

01Drafting new strategic Epics or Rocks with correct structural sections

02Reviewing existing issue backlogs for compliance with Giant Swarm conventions

03Converting technical debt notes into well-formatted Bugs or Tasks

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add giantswarm/claude-code issue-patterns

For use in Claude.ai and ChatGPT

Download Skill