ln-414-test-executor

Execute a single Story Finalizer test task labeled 'tests' through implementation to To Review.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Executes the Story finalizer test tasks (label "tests") from Todo to To Review, enforcing risk-based limits.

Core Features & Use Cases

  • Executes one final test task per run
  • Applies the risk-based caps: E2E 2-5, Integration 0-8, Unit 0-15, total 10-28
  • Delegates test creation and validation using the test templates

Quick Start

Execute the final test task for US005 via ln-414-test-executor.

Frequently Asked Questions about ln-414-test-executor

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

FAQPage Schema
How do I execute a final test plan with risk-based constraints?

Risk-based test execution enforces caps on test types—E2E 2-5, Integration 0-8, Unit 0-15, total 10-28—to balance coverage against implementation risk. This Skill moves a single Story's final test task from Todo to To Review while applying those constraints and updating Linear/kanban boards.

What does it mean to enforce a test plan across E2E, Integration, and Unit tests?

A test plan allocates test effort across three layers: E2E tests validate end-to-end workflows, Integration tests verify component interactions, Unit tests check isolated functions. This Skill validates your plan conforms to risk-based limits, then executes and summarizes coverage across all three.

How do I move a story's test task to review-ready status?

Test execution produces a To Review-ready summary with test coverage and any deviations from the plan. This Skill implements and runs tests labeled 'tests', captures results, and updates the task status and kanban board so reviewers can assess the work.

What happens to test tasks that don't follow the risk-based limits?

Tasks exceeding risk-based caps—Priority > 15 or test counts outside the allowed ranges—fail validation. This Skill rejects non-conforming plans and routes misrouted tasks to ln-411, ensuring only compliant work reaches To Review.

Can I execute multiple test tasks in a single run?

No, this Skill executes one final test task per run. It processes a single Story's 'tests'-labeled task through the 11-section test plan (E2E, Integration, Unit, plus infrastructure, documentation, and cleanup sections) in one cycle.

What's the difference between a test task labeled 'tests' and other task types?

Only tasks labeled 'tests' are processed by this Skill; other labels are routed to ln-411. This enforces clean separation between test execution and other Story finalizer work, keeping the workflow organized and predictable.