ln-310-story-validator

Validate Stories and Tasks against quality criteria with penalty points and auto-fixing.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-310-story-validator-cbbkrd-tech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-310-story-validator
Source: https://github.com/cbbkrd-tech/jl-finishes/tree/main/.claude/skills/ln-310-story-validator
Command: npx skills add https://github.com/cbbkrd-tech/jl-finishes --skill ln-310-story-validator-cbbkrd-tech

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the rigorous validation of software development Stories and Tasks, ensuring they meet quality standards, are free of critical issues, and are ready for execution. It quantizes quality through a penalty point system and provides an automated fix plan.

Core Features & Use Cases

  • Automated Audit: Evaluates Stories/Tasks against 22 criteria, including structure, standards compliance, dependencies, and risk.
  • Penalty Point System: Assigns points for violations, aiming for zero points after auto-fixing.
  • Auto-Fixing: Automatically corrects common violations to improve Story/Task quality.
  • Readiness Scoring: Provides a GO/NO-GO verdict and a Readiness Score (1-10).
  • Use Case: Before a Story is moved to the 'To Do' state, use this Skill to perform a comprehensive quality check, identify potential issues, automatically fix them, and get a final approval score.

Quick Start

Use the ln-310-story-validator skill to validate the current Story and its associated Tasks.

Frequently Asked Questions about ln-310-story-validator

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

FAQPage Schema
How do I validate software development stories before moving them to To Do?

To validate software development stories before moving them to To Do, you can run an automated audit against 22 quality criteria to assign penalty points, auto-fix violations, and generate a GO/NO-GO verdict with a Readiness Score.

What is a readiness score in story validation?

A readiness score in story validation is a 1-10 rating generated after evaluating structural integrity, standards compliance, and risk analysis, providing a final GO or NO-GO verdict based on accumulated penalty points.

Can I automatically fix quality violations in development tasks?

You can automatically fix quality violations in development tasks by running an automated review that identifies issues against predefined criteria and applies an auto-fixing plan to achieve zero penalty points.

Does story validation check for OWASP and RFC standards compliance?

Story validation checks for OWASP and RFC standards compliance as part of its automated audit, evaluating tasks against these specific standards to ensure security and protocol requirements are met before execution.

What are the limitations of automated story readiness scoring?

A limitation of automated story readiness scoring is that it delegates documentation creation to external processes and performs agent reviews separately, meaning it focuses strictly on penalty points and auto-fixing rather than generating comprehensive project documentation.

How do I perform a quality assurance check on a task's dependencies and workflow logic?

To perform a quality assurance check on a task's dependencies and workflow logic, use an automated task validation tool that audits these elements against predefined criteria, assigns penalty points for violations, and outputs an auto-fix plan.