t-run

Coordinate multi-phase software development by dispatching tasks to specialized sub-agents.

64|6|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/timzaak/web-dev-skills --skill t-run
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: t-run
Source: https://github.com/timzaak/web-dev-skills/tree/main/skills/t-run
Command: npx skills add https://github.com/timzaak/web-dev-skills --skill t-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multi-phase engineering work across backend, frontend, miniapp, and demo cycles is complex and error-prone. This Skill centralizes orchestration by dispatching work to specialized sub-agents, enforcing phase-order constraints, and surfacing progress and handoff information for reliable delivery.

Core Features & Use Cases

  • Orchestrates phased work by routing tasks to the appropriate sub-agent based on phase.
  • Enforces dependency rules and phase completion checks to prevent out-of-sequence execution.
  • Centralizes state and handoff summaries to simplify monitoring, reporting, and auditing across teams.
  • Use Case: For a feature with backend, frontend, and demo work, the Skill choreographs task creation, progress tracking, and final handoffs with clear status updates.

Quick Start

Issue the t-run workflow for a feature by calling /t-run <feature-name> --phase backend to begin the backend phase.

Frequently Asked Questions about t-run

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

FAQPage Schema
How do I coordinate multi-phase software development across backend and frontend?▼

Multi-phase software development can be coordinated by dispatching tasks to specialized sub-agents for each phase, enforcing phase-order constraints, and centralizing state and handoff summaries for reliable delivery.

What is the best way to orchestrate task dispatch for features spanning miniapp and demo phases?▼

Orchestrating phased work for miniapp and demo phases is best handled by routing tasks to appropriate sub-agents based on phase, which enforces dependency rules and completion checks to prevent out-of-sequence execution.

How do I start a backend phase workflow for a new feature?▼

To start a backend phase workflow, issue the command `/t-run <feature-name> --phase backend` to begin choreographing task creation, progress tracking, and handoffs with clear status updates.

Can I prevent out-of-sequence execution when managing phased engineering work?▼

Yes, out-of-sequence execution is prevented by enforcing dependency rules and phase completion checks, ensuring that tasks are only routed to specialized sub-agents when their preceding phases are complete.

Does multi-phase task management work without manual handoff reporting across teams?▼

Yes, multi-phase task management centralizes state and handoff summaries automatically, simplifying monitoring, reporting, and auditing across teams without requiring manual handoff reporting for each phase.