Skip to main content

team-issue

Unified team skill for issue resolution. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team issue".

معلومات المصدر

المستودع
catlog22/maestro-flow
آخر نشاط في المصدر
١٥ أكتوبر ٢٠٢٦ في ١٤:٣٥
لغة SKILL.md المكتشفة
الإنجليزية
النجوم
٥٦٦
التفرعات
٦٨

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

مستكشف الملفات
12 ملفات

عرض SKILL.md

SKILL.md
تعليمات المصدر · معاينة للقراءة فقط
name
team-issue
disable-model-invocation
true
description
Unified team skill for issue resolution. Uses team-worker agent architecture with role directories for domain logic. Coordinator orchestrates pipeline, workers are team-worker agents. Triggers on "team issue".
allowed-tools
["Bash","Edit","Glob","Grep","Read","Write","followup_task","interrupt_agent","list_agents","mcp__maestro__team_msg","request_user_input","send_message","spawn_agent","spawn_agents_on_csv","update_plan","wait_agent"]
session-mode
run
version
0.5.92
contract
{"discovery":"self-described","consumes":[],"produces":[],"gates":{"entry":[],"exit":[]}}
> **Agent timeout**: `spawn_agent` 异步执行且无内置超时 — 除明确短任务外一律 `spawn_agent` 后立即 `wait_agent({ timeout_ms: 3600000 })`(上限 1 小时)阻塞等待,绝不依赖 30000 默认值;`timed_out: true` 且 Agent 未完成时再次 `wait_agent` 续等,不丢弃。批量场景使用 `spawn_agents_on_csv({ max_runtime_seconds: 3600, ... })`。 <required_reading> @~/.maestro/workflows/run-mode-lite.md </required_reading> # Team Issue Resolution Orchestrate issue resolution pipeline: explore context -> plan solution -> review (optional) -> marshal queue -> implement. Supports Quick, Full, and Batch pipelines with review-fix cycle. ## Architecture ``` spawn_agent({ task_name: "team_issue", message: "Execute skill team-issue, args: <issue-ids> [--mode=<mode>]" }) | SKILL.md (this file) = Router | +--------------+--------------+ | | no --role flag --role <name> | | Coordinator Worker roles/coordinator/role.md roles/<name>/role.md | +-- clarify -> dispatch -> spawn workers -> STOP | +-------+-------+-------+-------+ v v v v v [explor] [plann] [review] [integ] [imple] ``` ## Role Registry | Role | Path | Prefix | Inner Loop | |------|------|--------|------------| | coordinator | [roles/coordinator/role.md](roles/coordinator/role.md) | — | — | | explorer | [roles/explorer/role.md](roles/explorer/role.md) | EXPLORE-* | false | | planner | [roles/planner/role.md](roles/planner/role.md) | SOLVE-* | false | | reviewer | [roles/reviewer/role.md](roles/reviewer/role.md) | AUDIT-* | false | | integrator | [roles/integrator/role.md](roles/integrator/role.md) | MARSHAL-* | false | | implementer | [roles/implementer/role.md](roles/implementer/role.md) | BUILD-* | false | ## Pre-load (coordinator, before dispatch) 1. **Codebase docs**: If `.workflow/codebase/ARCHITECTURE.md` exists, read for module boundaries 2. **Specs (coding)**: `maestro load --type spec --category coding` — load coding constraints as shared context 3. **Specs (debug)**: `maestro load --type spec --category debug` — load debug constraints as shared context 4. **Wiki knowledge**: `maestro search "issue resolution fix" --json` — top 5 entries as prior context 5. All optional — proceed without if unavailable ## Role Router Parse `$ARGUMENTS`: - Has `--role <name>` → Read `roles/<name>/role.md`, execute Phase 2-4 - No `--role` → `@roles/coordinator/role.md`, execute entry router ## Shared Constants - **Session prefix**: `TISL` - **Session path**: `{run_dir}/work/team/` - **Team name**: `issue` - **CLI tools**: `maestro delegate --mode analysis` (read-only), `maestro delegate --mode write` (modifications) - **Message bus**: `mcp__maestro__team_msg(session_id=<run-id>, ...)` ## Worker Spawn Template Coordinator spawns workers using this template: ``` spawn_agent({ subagent_type: "team-worker", description: "Spawn <role> worker", team_name: "issue", name: "<role>", run_in_background: true, prompt: `## Role Assignment role: <role> role_spec: <skill_root>/roles/<role>/role.md session: {run_dir}/work/team session_id: <run-id> team_name: issue requirement: <task-description> inner_loop: false ## Progress Milestones session_id: <run-id> Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification). Report blockers immediately via team_msg type="blocker". Report completion via team_msg type="task_complete" after final send_message. Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions. Execute built-in Phase 1 (task discovery) -> role Phase 2-4 -> built-in Phase 5 (report).` }) ``` **Parallel spawn** (Batch mode, N explorer or M implementer instances): ``` spawn_agent({ subagent_type: "team-worker", name: "<role>-<N>", team_name: "issue", run_in_background: true, prompt: `## Role Assignment role: <role> role_spec: <skill_root>/roles/<role>/role.md session: {run_dir}/work/team session_id: <run-id> team_name: issue requirement: <task-description> agent_name: <role>-<N> inner_loop: false ## Progress Milestones session_id: <run-id> Report progress via team_msg at natural phase boundaries (context loaded -> core work done -> verification). Report blockers immediately via team_msg type="blocker". Report completion via team_msg type="task_complete" after final send_message. Read role_spec file (@<skill_root>/roles/<role>/role.md) to load Phase 2-4 domain instructions. Execute built-in Phase 1 (task discovery, owner=<role>-<N>) -> role Phase 2-4 -> built-in Phase 5 (report).` }) ``` ## User Commands | Command | Action | |---------|--------| | `check` / `status` | View execution status graph, no advancement | | `resume` / `continue` | Check worker states, advance next step | ## Session Directory ``` {run_dir}/work/team/ ├── team-session.json # Session metadata + pipeline + fix_cycles ├── task-analysis.json # Coordinator analyze output ├── .msg/ │ ├── messages.jsonl # Message bus log │ └── meta.json # Session state + cross-role state ├── wisdom/ # Cross-task knowledge │ ├── learnings.md │ ├── decisions.md │ ├── conventions.md │ └── issues.md ├── explorations/ # Explorer output │ └── context-<issueId>.json ├── {run_dir}/outputs/solutions/ # Planner output │ └── solution-<issueId>.json ├── {run_dir}/outputs/audits/ # Reviewer output │ └── audit-report.json ├── {run_dir}/outputs/queue/ # Integrator output └── {run_dir}/outputs/builds/ # Implementer output ``` ## Specs Reference - [specs/pipelines.md](specs/pipelines.md) — Pipeline definitions and task registry ## Error Handling | Scenario | Resolution | |----------|------------| | Unknown command | Error with available command list | | Role not found | Error with role registry | | CLI tool fails | Worker fallback to direct implementation | | Fast-advance conflict | Coordinator reconciles on next callback | | Completion action fails | Default to Keep Active | | Review rejection exceeds 2 rounds | Force convergence to integrator | | No issues found for given IDs | Coordinator reports error to user | | Deferred BUILD count unknown | Defer to MARSHAL callback |
عرض على GitHub