droids-workflow-orchestration
[DROIDS-INTERNAL] Multi-agent workflow orchestration patterns. Only activate when invoked by /droids:start command. Do NOT auto-activate in regular conversations.
What this skill does
# Droids Workflow Orchestration
This skill provides patterns for orchestrating multiple specialized agents in a coordinated workflow.
## Core Principle: NEVER STOP UNTIL PERFECT
**There is NO iteration limit.** Continue fixing and re-testing until:
- ALL tests pass (100%)
- Code review is APPROVED
- No security vulnerabilities
- No bugs
- User requirement is fully met
- Supervisor approves (no context drift or regression)
## Critical: Context Preservation
**The #1 cause of workflow failure is losing sight of the original requirement.**
To prevent this:
1. **ALWAYS copy the original requirement** at the start of the workflow
2. **ALWAYS quote it exactly** when invoking any agent
3. **NEVER paraphrase or summarize** the user's words
4. **Use supervisor** to detect when context has drifted
## Agent Roles
| Agent | Role | When to Invoke |
|-------|------|----------------|
| **test-engineer** | Write and run tests | After code implementation |
| **code-reviewer** | Review code quality and security | After tests pass |
| **supervisor** | Prevent context drift and regression | Every 3 iterations, when issues increase, before completion |
| **doc-writer** | Generate documentation | When docs needed (optional) |
## Delegation Protocol
When delegating to an agent, provide:
1. **Original Requirement**: EXACT quote from user (never paraphrase)
2. **Context**: What was done before this step
3. **Scope**: Specific files or features to work on
4. **Requirements**: What the agent must deliver
5. **Iteration Info**: Current iteration number and history
### Delegation Template
```
Use the **{agent-name}** agent to {task description}.
**Original Requirement (EXACT QUOTE):**
"{user's original words}"
**Context:**
- Previous step: {what was done}
- Files modified: {list of files}
- Current iteration: {N}
**Scope:**
- {specific files or modules}
**Requirements:**
- {deliverable 1}
- {deliverable 2}
**Constraints:**
- Follow CLAUDE.md standards
- {other constraints}
**Wait for agent completion before proceeding.**
```
## Workflow Pattern: Infinite Iteration with Supervision
```
+-------------------------------------------------------------------+
| INFINITE ITERATION LOOP |
| (Continue until PERFECT completion) |
+-------------------------------------------------------------------+
| |
| Implement --> test-engineer --> Tests pass? |
| ^ | |
| | +----------+----------+ |
| | Yes No |
| | | | |
| | v +--> Fix ---------+
| | code-reviewer |
| | | |
| | Approved? |
| | +-------+-------+ |
| | Yes No |
| | | | |
| | v +--> Fix --> test-engineer -----+
| | (Every 3 iterations) |
| | | |
| | v |
| | supervisor --> CONTINUE? |
| | | |
| | +-------+-------+-------+ |
| | Yes PAUSE RESET |
| | | | | |
| | v v v |
| | ALL MET? Ask User Revert and restart |
| | | |
| +----+ No |
| | |
| Yes |
| | |
| v |
| COMPLETE |
| |
| SAFEGUARD: supervisor PREVENTS CONTEXT DRIFT AND REGRESSION |
| |
+-------------------------------------------------------------------+
```
## Success Criteria (ALL must be met)
Before completing, verify ALL of the following:
```
[ ] User requirement fully implemented? (check against ORIGINAL REQUIREMENT)
[ ] ALL tests passing (100%)?
[ ] Code review APPROVED?
[ ] No security vulnerabilities?
[ ] No bugs or regressions?
[ ] Follows project standards (CLAUDE.md)?
[ ] Supervisor APPROVED?
```
**If ANY checkbox is NOT checked, continue iterating. DO NOT STOP.**
## Supervisor Triggers
Invoke the supervisor agent when:
1. **Periodic Check**: After every 3 fix-test-review cycles
2. **Regression Signal**: Test pass rate decreases
3. **Issue Escalation**: Code-reviewer finds more issues than before
4. **Uncertainty**: When unsure about direction
5. **Final Gate**: Before reporting completion
## Error Handling
### Test Failures
1. Analyze failure reason
2. Fix implementation (reference ORIGINAL REQUIREMENT)
3. Re-invoke test-engineer
4. **REPEAT UNTIL ALL TESTS PASS - NO LIMIT**
### Review Issues
1. Categorize by severity (Critical/Important/Suggestion)
2. Critical issues: MUST fix before proceeding
3. Important issues: MUST fix before proceeding
4. Suggestions: Fix if time permits
5. **REPEAT UNTIL FULLY APPROVED - NO LIMIT**
### Supervisor Recommendations
**If CONTINUE:**
- Apply guardrails provided
- Continue with next iteration
**If PAUSE:**
- Stop immediately
- Ask user for clarification
- Do NOT guess or assume
**If RESET:**
- Revert problematic changes
- Start fresh with simpler approach
- Reference ORIGINAL REQUIREMENT
## Communication Templates
### Starting Workflow
```
Starting Droids workflow for: {requirement}
ORIGINAL REQUIREMENT (PRESERVED):
"{exact user words}"
Workflow steps:
1. [PENDING] Analyze and implement
2. [PENDING] Test with test-engineer
3. [PENDING] Review with code-reviewer
4. [PENDING] Verify with supervisor
5. [PENDING] Document (if needed)
Note: Will iterate until ALL criteria are met. No iteration limit.
Safeguard: supervisor will prevent context drift and regression.
```
### Progress Updates
```
Iteration {N} Complete
Test Results: {X/Y passed}
Review Status: {APPROVED/NEEDS CHANGES}
Issues Found: {count}
Trend: {IMPROVING/STABLE/DEGRADING}
Next Action: {what will be done}
Original Requirement (reminder):
"{exact user words}"
```
### Completion Report
```
## Workflow Complete
### Original Requirement
"{exact user words}"
### Summary
- Implemented: {features}
- Total iterations: {count}
- Tests: ALL PASSED ({coverage}%)
- Review: APPROVED
- Supervisor: APPROVED
- Documentation: {status}
### Verification Checklist
[x] User requirement fully implemented
[x] All tests passing
[x] Code review approved
[x] No security vulnerabilities
[x] No bugs
[x] Follows project standards
[x] Supervisor approved
### Files Modified
- {file list}
```
## Agent Invocation Examples
### Invoke test-engineer
```
Use the **test-engineer** agent to create and run comprehensive tests.
**Original Requirement:**
"{exact user words}"
**Context:**
- Implemented user authentication feature
- Files: src/auth/login.ts, src/auth/register.ts
- Current iteration: 1
**Requirements:*Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.