Does it work for bug reports and postmortems?

Yes, it includes specific requirements for bugs (reproduction steps, logs) and postmortems (timelines, root causes, and prevention measures).

What is required for an 'Excellent' Epic?

An Excellent Epic must include strategic context (motivation), clear scope, measurable outcomes, verifiable acceptance criteria, and no missing links.

How does this skill score GitHub issues?

It uses three levels: Minimum Viable (50-69%), Good (70-89%), and Excellent (90-100%) based on metadata, formatting, and content depth.

What are the 3 C's of issue quality?

The 3 C's stand for Clear (specific language and context), Complete (all sections and no placeholders), and Connected (linked to epics and team ownership).

Giant Swarm Issue Quality Standards

Name: Giant Swarm Issue Quality Standards
Author: giantswarm

bygiantswarm

Collaboration Tools

Enforces high-quality standards and validation criteria for GitHub issues, epics, and user stories.

About

The Quality Standards skill provides a robust framework for auditing and improving Giant Swarm GitHub issues using a data-driven scoring system. It evaluates issues against the '3 C's' (Clear, Complete, Connected) and ensures adherence to specific requirements for different issue types like Epics, Stories, and Bugs. By identifying common failure patterns such as vague titles or missing team labels, this skill helps teams elevate their project management from 'Minimum Viable' to 'Excellent,' ensuring every task has clear context, measurable outcomes, and proper strategic alignment.

Key Features

Type-specific checklists for Epics, Stories, Tasks, Bugs, and Postmortems
Three-tier quality scoring system (Minimum Viable, Good, Excellent)
Detection of common failure patterns like vague titles and orphaned stories
0 GitHub stars
Validation based on the '3 C's' (Clear, Complete, Connected) framework
Structured feedback generation with prioritized critical fixes

Use Cases

Auditing backlogs to ensure all upcoming stories meet 'Excellent' quality criteria
Drafting complex Epics with strategic context and verifiable acceptance criteria
Standardizing bug reports to include mandatory reproduction steps and logs

About

Key Features

Type-specific checklists for Epics, Stories, Tasks, Bugs, and Postmortems
Three-tier quality scoring system (Minimum Viable, Good, Excellent)
Detection of common failure patterns like vague titles and orphaned stories
0 GitHub stars
Validation based on the '3 C's' (Clear, Complete, Connected) framework
Structured feedback generation with prioritized critical fixes

Use Cases

Auditing backlogs to ensure all upcoming stories meet 'Excellent' quality criteria
Drafting complex Epics with strategic context and verifiable acceptance criteria
Standardizing bug reports to include mandatory reproduction steps and logs