github:story-quality

What problem does it solve?

This Skill automates the tedious process of checking GitHub stories for essential quality attributes like SMART acceptance criteria and Non-Functional Requirement (NFR) coverage, ensuring stories are well-defined before development begins.

Core Features & Use Cases

• Automated Quality Checks: Evaluates stories for specific, measurable, achievable, relevant, and time-bound (SMART) acceptance criteria.
• NFR Compliance: Verifies that relevant system-wide Non-Functional Requirements are addressed in story definitions.
• Automated Labeling: Applies labels like needs-acs, needs-nfrs, needs-refinement, or ready-for-development based on the quality assessment.
• Feedback Comments: Posts structured comments on issues that require refinement, detailing the gaps found.
• NFR Registry Updates: Automatically proposes new NFR entries based on observed patterns in stories (scheduled runs only).
• Use Case: A Product Manager can use this skill to automatically flag stories that lack clear acceptance criteria or fail to address critical NFRs, streamlining the refinement process and improving development efficiency.

Quick Start

Run the /check-story-quality command to analyze the current story for quality gaps and apply appropriate labels.