ln-310-story-validator

Validate and auto-fix Stories and Tasks against 2025 standards.

534|73|Updated Oct 24, 2025
One-click install
npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-310-story-validator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-310-story-validator
Source: https://github.com/levnikolaevich/claude-code-skills/tree/main/ln-310-story-validator
Command: npx skills add https://github.com/levnikolaevich/claude-code-skills --skill ln-310-story-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Critically reviews Stories and Tasks against 2025 standards, auto-fixes structure, and generates documentation as needed.

Core Features & Use Cases

  • Phase 1: Upstream validation for ln-220 origins
  • Phase 2: Critical solution review and auto-fix
  • Phase 3: Output tabular validation and approvals

Quick Start

Validate a Story before execution; auto-fix if needed.

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 Stories and Tasks against 2025 standards?

Story validation against 2025 standards automates structural review of Story narratives and Tasks, checking 8-section and 7-section templates respectively, then auto-fixes deviations and generates approval documentation before execution.

Can this Skill auto-fix Stories that don't meet standards?

Auto-fix corrects Story and Task structure to comply with 2025 standards templates, applies standards references (RFC/OWASP), and updates cross-tool records across ln-321, ln-002, and Linear in one pass.

What does Story validation check for before execution?

Validation enforces 8-section Story templates, 7-section Task templates, architectural integrity constraints, standards references (RFC/OWASP), and critical-path coverage including CRUD fast-paths to ensure backlog readiness.

How does this Skill handle Stories with child Tasks?

Story validation applies constraints across parent Stories and child Tasks simultaneously, validating structure, cross-tool consistency, and standards compliance, then outputs tabular approval status for entire hierarchies.

What output does validation produce?

Validation generates tabular reports showing approval status, auto-fix summaries, updated documentation, and backlog transition records, with cross-tool updates to ln-321, ln-002, and Linear.

When should I run Story validation in my workflow?

Run validation as upstream review before ln-220 execution, during critical solution review phases, and before final backlog approval to catch structural and standards gaps early.