story-quality-gate

Evaluate user stories against INVEST criteria and flag quality gaps.

15|2|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/kousukef/forge --skill story-quality-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-quality-gate
Source: https://github.com/kousukef/forge/tree/main/skills/story-quality-gate
Command: npx skills add https://github.com/kousukef/forge --skill story-quality-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Lightweight gate to assess the structural quality of user stories against INVEST criteria, preventing low-quality stories from entering the specification stage and prompting improvements before proposal generation.

Core Features & Use Cases

  • I - Independent: checks whether each story stands alone without implicit dependencies.
  • N - Negotiable: ensures goals are stated without enforcing specific implementation.
  • V - Valuable: validates clear business or user value behind each story.
  • E - Estimatable: assesses if scope is estimate-friendly and bounded.
  • S - Small: ensures each story has a single, focused objective.
  • T - Testable: confirms there are observable criteria to validate outcomes.

Quick Start

After brainstorming outputs, run the story-quality-gate to obtain an INVEST-based assessment before generating proposal.md.

Frequently Asked Questions about story-quality-gate

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

FAQPage Schema
How do I check user stories against INVEST criteria before creating a proposal?

You can check user stories against INVEST criteria by running a quality gate after brainstorming, which evaluates Independence, Negotiability, Value, Estimability, Size, and Testability before generating proposal.md.

What is an INVEST quality gate for user stories?

An INVEST quality gate is a lightweight checkpoint that assesses structural story quality, preventing low-quality requirements from entering the specification stage by flagging issues for dialogue.

When should I validate user story quality in the requirements workflow?

You should validate user story quality after brainstorm outputs are generated and before proposal creation, ensuring requirements are assessed and improved before entering the specification stage.

Does the story quality gate block requirements with warnings or just flag issues?

The story quality gate uses a lightweight Pass/Warn signal system to flag issues for dialogue and records unresolved points, rather than hard-blocking requirements from proceeding downstream.

Can I use the quality gate for brainstormed stories without external dependencies?

Yes, you can apply the quality gate to brainstormed stories without external dependencies, as it operates independently to assess INVEST criteria and supports automated extension to the proposal workflow.

What happens to unresolved story quality points after the gate assessment?

Unresolved story quality points are recorded by the gate, allowing teams to track outstanding INVEST issues while still supporting automated extension to the proposal workflow.