epic-runner-script

Generate and validate Trello-SSOT epic runner scripts with Epic UID tracking.

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/almazom/agents_slash_skills --skill epic-runner-script
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-runner-script
Source: https://github.com/almazom/agents_slash_skills/tree/main/epic-runner-script
Command: npx skills add https://github.com/almazom/agents_slash_skills --skill epic-runner-script

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Coordinates and automates the creation, validation, and synchronization of Trello-SSOT epic launcher scripts, runner cards, and contracts, reducing manual orchestration overhead.

Core Features & Use Cases

  • End-to-end epic launcher orchestration for Trello-SSOT, including headless runners, observer coordination, and Epic UID tracking
  • Canonical launcher management under automation/headless and runner-card disclosures with explicit HOOK_TIMES
  • JSONL audit streams and compliance verification to ensure real command execution matches board activity

Quick Start

Launch the dedicated headless epic runner with the canonical launcher path to begin processing an epic.

Frequently Asked Questions about epic-runner-script

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

FAQPage Schema
How do I automate Trello epic launches with headless runner scripts?

Automate Trello epic launches by generating and validating headless runner scripts via a canonical launcher path. This coordinates observer coordination and syncs artifacts while enforcing strict Epic UID tracking across local and pet servers.

What is an Epic UID and why does it matter for Trello automation?

An Epic UID is a stable tracking identifier required by the official epic runner contract. It ensures correct artifact synchronization and strict audit compliance across headless runners and manager-led Trello workflows.

How do I verify Trello board activity matches real command execution?

Verify board activity matches execution using JSONL audit streams and compliance verification workflows. This validates that runner scripts and artifacts generated by the launcher accurately reflect real commands.

Do I need explicit HOOK_TIMES in my epic runner descriptions?

Yes, explicit HOOK_TIMES are required in runner card descriptions to meet the official automation contract. The canonical launcher management enforces this to maintain stable headless execution and audit compliance.

What's the best way to coordinate manager-led epic workflows across local and pet servers?

Coordinate manager-led epic workflows by orchestrating launcher scripts that sync runner cards and contracts across local and pet servers. This approach applies headless runners and observer coordination for strict Epic UID tracking.