ln-500-story-quality-gate

Orchestrate multi-stage quality assurance for software development stories.

1|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-500-story-quality-gate-mcauduro0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-500-story-quality-gate
Source: https://github.com/mcauduro0/Macro_Trading/tree/main/.claude/skills/ln-500-story-quality-gate
Command: npx skills add https://github.com/mcauduro0/Macro_Trading --skill ln-500-story-quality-gate-mcauduro0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the crucial step of validating the quality of implemented stories, ensuring they meet defined standards before proceeding, thereby reducing technical debt and improving overall product reliability.

Core Features & Use Cases

  • Automated Quality Checks: Orchestrates code quality, test coverage, and NFR validation.
  • 4-Level Verdict System: Assigns a PASS, CONCERNS, FAIL, or WAIVED verdict based on predefined criteria.
  • Use Case: After a developer completes a new feature, this Skill can be invoked to automatically assess the code's quality, ensure adequate test coverage, and verify non-functional requirements like security and performance, providing a clear go/no-go decision.

Quick Start

Use the ln-500-story-quality-gate skill to run the quality gate for story ID 'STORY-123'.

Frequently Asked Questions about ln-500-story-quality-gate

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

FAQPage Schema
How do I automate story validation and code quality checks before merging a feature?

Automated story validation orchestrates code quality assessment, test planning, and NFR validation to assign a final PASS, CONCERNS, FAIL, or WAIVED verdict. This reduces technical debt by ensuring implemented stories meet predefined quality standards before proceeding.

What is a 4-level quality gate and how does it assess non-functional requirements?

A 4-level quality gate evaluates story compliance by calculating quality scores and validating non-functional requirements (NFRs). It outputs a final verdict—PASS, CONCERNS, FAIL, or WAIVED—based on predefined criteria to provide a clear go/no-go decision for feature completion.

How do I run a quality gate assessment for a specific story ID?

Run the quality gate assessment by invoking the orchestration skill with your specific story identifier. The process delegates tasks to specialized skills for code quality and test planning, calculating scores and NFR compliance to return a final verdict.

Does automated story validation require specialized skills for test planning and code review?

Automated story validation delegates tasks to specialized skills for code quality assessment and test planning. This multi-stage orchestration ensures comprehensive coverage of both functional implementation and non-functional requirements before determining the final quality verdict.

Can I waive a failed story quality gate verdict when non-functional requirements are not met?

Yes, the story quality gate supports a WAIVED verdict alongside PASS, CONCERNS, and FAIL. When non-functional requirements are evaluated, the system can assign WAIVED based on predefined criteria, allowing development to proceed under specific conditions.

Why does my story quality gate return a CONCERNS verdict instead of a PASS?

A story quality gate returns a CONCERNS verdict when calculated quality scores or non-functional requirement compliance do not fully meet the criteria for a PASS. This indicates potential issues in code quality or test coverage that require review before proceeding.