菜单
Pick a task from docs/backlog, implement it using dev-skill, and verify with a QA subagent. Use when you want to autonomously complete a backlog task end-to-end for team michele-luca's Exercise One.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | task-orchestrator |
| description | Pick a task from docs/backlog, implement it using dev-skill, and verify with a QA subagent. Use when you want to autonomously complete a backlog task end-to-end for team michele-luca's Exercise One. |
Autonomous task-completion agent for team michele-luca's budgeting app. Reads a
pending task from docs/backlog/, implements it via dev-skill, then spawns a
QA subagent with qa-skill to verify the result.
Read task: Scan teams/michele-luca/excercise_one/docs/backlog/ for pending
tasks. Pick one (or the user specifies which). Task files should be markdown
with frontmatter containing at least status: pending or similar.
Implement: Use the dev-skill skill to write code, start the dev server,
drive the app with Playwright, and screenshot the result. Follow the domain
model and architecture in CLAUDE.md.
QA handoff: Spawn an Agent with subagent_type qa-agent (or similar) that
invokes the qa-skill skill. The QA agent runs all gates (lint, typecheck,
build), reviews the diff against the checklist, and reports pass/fail.
Update task: If QA passes, mark the task completed (e.g., update
frontmatter to status: completed and add a completion timestamp). If QA
fails, report the issue and optionally iterate.
docs/backlog/ as markdown files with frontmatter
(status, title, etc.).dev-skill and qa-skill must be available (they are).npm install from
teams/michele-luca/excercise_one/).# From Claude Code CLI or chat:
/task-orchestrator
# or with a specific task file:
/task-orchestrator task-001-add-transaction-form.md
The skill is designed to be invoked by Claude Code's Skill tool — it does not run as a standalone script.
---
id: task-001
title: Add transaction input form
status: pending
priority: high
created: 2026-05-26
---
# Task: Add transaction input form
Allow users to input a new transaction (amount, category, date). Store in
localStorage via the storage layer. Display in a transaction list below the form.
## Acceptance criteria
- Form has fields: amount (cents), category, date
- Submit button adds transaction to storage
- Transaction list re-renders showing the new entry
- Type-safe: Transaction type from src/types/
The orchestrator reads the task description, implements it, and updates the
frontmatter status field when done.
The orchestrator spawns an Agent with a prompt like:
Run QA on the current diff for task-001. Use the qa-skill to run lint, typecheck, and build. Review the diff against the money-correctness checklist (integer cents, no floats, storage layer abstraction). Report pass/fail.
The subagent has access to qa-skill and reports back. If it fails, the
orchestrator decides whether to fix and retry or escalate to the user.
dev-skill starts the server in the background
(npm run dev &). The orchestrator should ensure it's running before
implementing and optionally kill it after QA (or leave it running for the
next task).status field in
frontmatter. If your tasks use a different tracking system (e.g., GitHub
issues, Linear), adapt the read/update logic.Facilitate a structured feature brainstorming session for the personal finance app. Use this skill when the user wants to explore a new feature idea, plan what to build next, or think through a product direction. Triggers on phrases like "brainstorm", "let's think about", "what should we build", "plan a feature", or "I have an idea".
Fetch ALL pending [Feature] Asana tasks and drive them through implementation with maximum safe parallelism. Use this when the user wants to drain the entire feature backlog in one command rather than processing tasks one at a time. Triggers on "process the backlog", "drain the backlog", "build everything in Asana", or explicit /process-backlog invocation.
Drive new Java feature development using red-green-refactor TDD. Use when asked to "add a feature TDD", "write the test first", "do TDD for X", or "red-green-refactor X". Takes a feature description and iterates: failing test → minimal implementation → refactor.
Build and run the team-tom Java Maven app. Use when asked to "run the app", "start the budget tracker", "demo the app", or "run java". Compiles with Maven, then launches the jar.
This skill should be used when the user or an agent asks to "implement a task", "execute a dev task", "code the task", "write the code for a task", "pick up a task from the orchestrator", or when a task file needs to be implemented. Reads a structured task specification file written by an orchestrator agent and produces working code in the target programming language.
Stage and commit the current working tree changes with a well-formed commit message. Use when the user says "commit", "git commit", "commit my changes", or invokes /git-commit.