github:story-quality

Analyze GitHub project stories for SMART acceptance criteria and NFR coverage.

2|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/amdmax/claude_marketplace --skill github-story-quality
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github:story-quality
Source: https://github.com/amdmax/claude_marketplace/tree/main/.claude/skills/github%3Astory-quality
Command: npx skills add https://github.com/amdmax/claude_marketplace --skill github-story-quality

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

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.

Frequently Asked Questions about github:story-quality

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

FAQPage Schema
How do I automate checking GitHub stories for SMART acceptance criteria and NFR coverage?

You can automate GitHub story quality checks by running scheduled background workflows or the /check-story-quality command to evaluate SMART acceptance criteria and NFR coverage, then apply labels like ready-for-development or needs-refinement.

What is the best way to ensure GitHub project stories meet quality standards before development?

Ensuring GitHub story quality standards involves analyzing issues for SMART acceptance criteria and Non-Functional Requirements, then posting structured feedback comments and applying quality-related labels to flag stories needing refinement.

Do I need the gh CLI to analyze GitHub issues for acceptance criteria?

Yes, you need the gh CLI installed for GitHub API interactions, as it provides the required access to read project stories, apply labels, and post structured feedback comments on issues.

How does automated NFR compliance checking work for GitHub project stories?

Automated NFR compliance checking works by evaluating story definitions against a defined NFR registry, identifying gaps in Non-Functional Requirements coverage, and proposing new NFR entries based on observed patterns during scheduled runs.

Can I manually invoke a quality check on a specific GitHub story?

Yes, you can manually invoke a quality check on a specific GitHub story by using the /check-story-quality command, which processes the active story context to identify quality gaps and apply appropriate labels.

What labels are applied to GitHub stories that lack clear acceptance criteria?

GitHub stories lacking clear acceptance criteria receive labels like needs-acs for missing acceptance criteria, needs-nfrs for missing Non-Functional Requirements, and needs-refinement for general quality gaps.