agentleFS
eyeixeyeix/skills/run-ticket/SKILL.md

run-ticket

Skill1 starsChanged 30 days agoMITView on GitHub

执行 .agentdocs/workflow/<task>/tickets/ 下的单张工单:测试先行构建,收尾走 code-review,提交并更新工单状态。/team-dev 的轻量对应物,多张工单就绪时移交组队模式。

The file

Files
SKILL.md

执行工单

单张工单、单会话的轻量执行入口;多张工单就绪时移交组队模式。

前置:工单存在于 .agentdocs/workflow/<task>/tickets/。没有时告诉用户先运行 /task-tickets。

流程

  1. 读工单全文:理解构建内容与验收标准。工单是唯一任务源,验收标准逐条对照实现;
  2. 读相关文档:遵循 agent-docs 的读纪律,任务涉及的领域文档按 index.md 定位阅读;
  3. 测试先行构建:调 Skill 工具执行 tdd,在任务文档"测试决策"约定的接缝上红绿循环,一次一片;
  4. 检查节奏:定期跑类型检查与单个测试文件,结束时跑完整测试套件;
  5. 收尾审查:调 Skill 工具执行 code-review,固定点为开工前的分支状态,并告知规格为工单文件路径;
  6. 修复与提交:修复审查发现后提交到当前分支(Conventional Commits);
  7. 收口工单:勾选工单验收标准,状态改为 done。盘点剩余工单:就绪(阻塞边清空)的只有一张时提醒用户可继续;多张同时就绪时,告知用户并调 Skill 工具执行 team-dev,由组队模式并行派发。

边界

  • 工单存在拆分缺陷(粒度不对、遗漏依赖)时,先修订工单再继续,与 team-dev 同规则;
  • 实现中出现方案分歧,回任务文档(task.md)找答案;文档没有答案时问用户,不擅自定稿。

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.