ln-404-test-executor

Execute Story Finalizer tests labeled 'tests' from Todo to To Review.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/0xtaoist/taogate --skill ln-404-test-executor-0xtaoist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ln-404-test-executor
Source: https://github.com/0xtaoist/taogate/tree/main/ln-404-test-executor
Command: npx skills add https://github.com/0xtaoist/taogate --skill ln-404-test-executor-0xtaoist

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes Story Finalizer test tasks (label "tests") from Todo -> To Review, enforcing risk-based limits and priority to ensure consistent, auditable test execution within development workflows.

Core Features & Use Cases

  • Automates the end-to-end execution of Story Finalizer tests labeled "tests" from Todo to To Review.
  • Enforces risk-based constraints and priority checks to gate test execution.
  • Updates task status in kanban systems and records test outcomes for traceability.
  • Reads linked guides/manuals and reviews parent stories to align test scope with business goals.
  • Supports integration with Linear/kanban-style workflows for single-task focus.

Quick Start

Instruct the system to execute one Story Finalizer test task labeled 'tests' from Todo to To Review following the defined plan.

Frequently Asked Questions about ln-404-test-executor

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

FAQPage Schema
How do I automate test execution for kanban tasks moving from Todo to To Review?

Automating test execution for kanban tasks from Todo to To Review requires loading task details, consulting linked guides, running tests, and updating task status. This process enforces risk-based limits and priority checks to gate execution while recording outcomes for traceability.

What is a Story Finalizer test workflow in Linear?

A Story Finalizer test workflow in Linear executes test tasks labeled 'tests' to validate parent stories against business goals. It reads linked manuals, runs risk-prioritized tests, records results, and transitions task status from Todo to To Review for auditable validation.

How do I enforce risk-based priority checks before running automated tests?

Enforcing risk-based priority checks before running automated tests involves gating execution based on risk constraints and priority levels. The system loads task details, reviews parent stories to align scope, and validates risk factors before transitioning tasks from Todo to To Review.

Does this test execution approach support bulk status updates for kanban boards?

No, this test execution approach explicitly avoids bulk updates to maintain single-task focus and auditable traceability. It processes individual Story Finalizer test tasks labeled 'tests', ensuring controlled status transitions from Todo to To Review within kanban workflows.

What are the limitations of automating Story Finalizer test tasks?

Limitations include single-task focus without bulk updates, strict adherence to risk-based priority gating, and dependency on linked guides and parent stories for scope alignment. Test execution is restricted to tasks labeled 'tests' transitioning from Todo to To Review.