Agent skill · Frontend

t-run

Execute phased task plans for backend, frontend, miniapp, Flutter, Web Demo, or Flutter Demo.

timzaak55★ · 1 repos on radarProfile →
claude-coderead-onlyApache-2.0
Install
npx skills add timzaak/web-dev-skills --skill t-run --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 5 KB
Bundled scripts: none
Allowed tools: -AskUserQuestion-Read-Glob-Grep-Task-TaskCreate
Path: skills/t-run/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 55
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 任务执行 运行时边界统一参考：`${CLAUDE_PLUGIN_ROOT}/protocols/runtime-boundaries.md` 执行时以当前 item 的成功标准和最小必要验证为目标；遇到冲突、缺失上下文或无法判断的语义问题时停止并说明。 ## Input Contract 上游输入（来自 `/t-task` 产出）： - `.ai/task/[feature]/.state.json` — 任务状态文件（必须存在且可解析） - 目标阶段必须已规划（`phases[phase]`、`tasks[phase]` 和对应阶段目录存在） - `.ai/task/[feature]/<phase>/index.md` — 阶段总览 - `.ai/task/[feature]/<phase>/<slot>.md` — Slot manifest - `.ai/task/[feature]/<phase>/<slot>/<ITEM-ID>-*.md` — Item 文件 ## Output Contract 下游产出： - 更新的 `.state.json` — item/slot/phase 状态变更 - item 失败后写入 `last_error` - item agent 执行产生的代码文件变更（由各 agent 自行产出） ## Purpose - 读取 `.ai/task/[feature]/.state.json`。 - 按当前 phase 的 slot 和 manifest 顺序选择可执行 item，并始终串行调度单个 sub agent。 - `/t-run` 的执行单元、slot 顺序、失败处理、所需上下文统一参考 `${CLAUDE_PLUGIN_ROOT}/protocols/task-phase-execution.md`。 - `index.md` 和 slot manifest 不作为直接执行单元；slot manifest 同时是 slot 内 item 执行顺序的真源。 - backend 的 OpenAPI 导出与前端 API 生成验收由 `backend-accept` 负责。 ## Args | 参数 | 说明 | |---|---| | `[feature]` | 功能名 | | `--phase <backend\|frontend\|miniapp\|flutter\|web-demo\|flutter-demo>` | 仅执行指定阶段；未指定时执行 `.state.json` 的当前阶段 | ## Preconditions - `.ai/task/[feature]/.state.json` 必须存在且可解析。 - 目标阶段必须是 supported phase，且存在于当前任务 active phas

What's inside
Steps it walks through
  1. Input Contract
  2. Output Contract
  3. Purpose
  4. Args
  5. Preconditions
  6. Shared Contracts
  7. Item Selection
  8. Sub Agent Context Contract
  9. State Transition
  10. Forbidden
  11. Failure
More from web-dev-skills
All skills →
t-demo-run-allDiscover all non-live Demo E2E tests and run them one file at a time in the main session…Testing & QAt-demo-runRun a single demo E2E test file, diagnose failures, dispatch fixes to agents, and re-run until pass.Testing & QAt-decisionDecide whether a feature should enter the t-tools workflow before tech research or PRD.Workflow & Productivityt-docGenerate project tutorial documentation that reads like a human wrote it, not like AI output. Scans…Backend & APIt-design-checkEvaluate technical design documents for implementability, completeness, and consistency with a…Design & Presentationt-demo-acceptValidate demo tests cover user stories, compile and pass, and output structured acceptance reports.Other
About this skill
What does the t-run skill do?

Execute phased task plans for backend, frontend, miniapp, Flutter, Web Demo, or Flutter Demo.

How do I install it?

Run `npx skills add timzaak/web-dev-skills --skill t-run --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From timzaak/web-dev-skills, a repository with 55 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.