From enterprise-team
Provides Markdown templates for agent-to-agent handoffs, QA verdicts, escalations, and phase gates. Use when coordinating multi-agent workflows to prevent context loss.
npx claudepluginhub chipagosfinest/enterprise-team --plugin enterprise-teamThis skill uses the workspace's default tool permissions.
Standardized templates for agent-to-agent handoffs. Use these to prevent context loss — the #1 cause of multi-agent coordination failure.
Use when dispatching subagents, composing prompts for teammates, structuring handoff reports, or managing context boundaries between agents. Covers both subagent prompts and team-level messaging.
Provides protocols, templates, and rules for constructing subagent delegation prompts with context chains, protocol injection, and downstream declarations in agent orchestration.
Defines Markdown artifact handoff protocol for two-pipeline (code/test/simulation) architecture in multi-agent workflows, enforcing naming, paths, and isolation via leader mediation.
Share bugs, ideas, or general feedback.
Standardized templates for agent-to-agent handoffs. Use these to prevent context loss — the #1 cause of multi-agent coordination failure.
## Handoff
| From | [Agent/Department] |
| To | [Agent/Department] |
| Priority | [Critical / High / Medium / Low] |
## Context
**Current State**: [What's been completed]
**Relevant Files**: [file paths and what they contain]
**Dependencies**: [What this depends on]
**Constraints**: [Technical, timeline, resource]
## Deliverable Request
**What's needed**: [Specific, measurable deliverable]
**Acceptance criteria**:
- [ ] [Measurable criterion 1]
- [ ] [Measurable criterion 2]
## Quality Expectations
**Must pass**: [Specific quality bar]
**Evidence required**: [What proof looks like]
## QA Verdict: PASS
| Task | [Description] |
| Attempt | [N] of 3 |
**Verified**:
- [x] [Criterion 1] — verified via [evidence]
- [x] [Criterion 2] — verified via [evidence]
**Next**: Mark complete, advance to next task.
## QA Verdict: FAIL
| Task | [Description] |
| Attempt | [N] of 3 |
### Issues Found
**Issue 1**: [Severity: Critical/High/Medium]
- Expected: [What should happen]
- Actual: [What actually happens]
- Fix: [Specific instruction]
- File: [Exact path]
**Retry Instructions**:
1. Fix ONLY the issues listed above
2. Do NOT introduce new features
3. This is attempt [N] of 3 maximum
4. If attempt 3 fails → escalation
## Escalation Report
| Task | [Description] |
| Attempts Exhausted | 3/3 |
### Failure History
- Attempt 1: [Issue] → [Fix applied] → [Why it still failed]
- Attempt 2: [Issue] → [Fix applied] → [Why it still failed]
- Attempt 3: [Issue] → [Fix applied] → [Why it still failed]
### Root Cause
[Why the task keeps failing]
### Recommended Resolution
- [ ] Reassign to different specialist
- [ ] Decompose into smaller sub-tasks
- [ ] Revise approach (architecture change needed)
- [ ] Accept current state with documented limitations
## Phase Gate
| From | Phase [N] — [Name] |
| To | Phase [N+1] — [Name] |
| Result | PASSED / FAILED |
### Gate Criteria
| Criterion | Threshold | Result | Evidence |
|-----------|-----------|--------|----------|
| [Criterion] | [Threshold] | PASS/FAIL | [Evidence] |
### Carried Forward
- [Key constraint from this phase]
- [Risk identified]
### Next Phase Agents
| Agent | Role | Priority |
|-------|------|----------|
| [Agent] | [Role] | Immediate/Day 2 |
Defined in enterprise-orchestrator. Uses templates #2 (PASS), #3 (FAIL), and #4 (Escalation) above.