Orchestration Skills
Orchestration skills focus on coordinating work between personas and managing workflows.
Available Skills
Section titled “Available Skills”| Skill | Purpose | Common Personas |
|---|---|---|
| Task Decomposition | Break complex tasks into subtasks | Bernstein, Hopper, Lovell |
| Handoff | Transfer work between personas | Bernstein |
| Summarization | Condense information for handoffs | All personas |
| Progress Tracking | Monitor and report task progress | Lovell, Drucker |
| Constraint Gathering | Elicit requirements and constraints | Hopper, Bernstein |
Task Decomposition
Section titled “Task Decomposition”Break complex tasks into manageable subtasks.
When to Use:
- Project planning
- Sprint planning
- Complex problem solving
- Delegation
Inputs Required:
- Main task or goal
- Constraints (time, resources)
- Dependencies
Outputs Produced:
- Subtask list
- Dependency graph
- Persona assignments
- Sequencing
Handoff
Section titled “Handoff”Transfer work between personas with full context.
When to Use:
- Phase transitions (planning → execution → QA)
- Persona changes
- Escalation
- Parallel workstreams
Inputs Required:
- Work completed so far
- Receiving persona
- Context and constraints
- Success criteria
Outputs Produced:
- Handoff document
- Context summary
- Open questions
- Next steps
Summarization
Section titled “Summarization”Condense information for handoffs and communication.
When to Use:
- Long document processing
- Cross-persona communication
- Status updates
- Executive summaries
Inputs Required:
- Content to summarize
- Target audience
- Length constraints
- Key focus areas
Outputs Produced:
- Executive summary
- Key points
- Action items
- Full reference (if needed)
Progress Tracking
Section titled “Progress Tracking”Monitor and report task progress against plans.
When to Use:
- During execution phases
- Status meetings
- Milestone reviews
- Risk monitoring
Inputs Required:
- Original plan
- Current status
- Blockers or issues
Outputs Produced:
- Progress report
- Variance analysis
- Risk updates
- Recommendations
Constraint Gathering
Section titled “Constraint Gathering”Elicit requirements and constraints from stakeholders.
When to Use:
- Project kickoff
- Requirement gathering
- Scope clarification
- Risk identification
Inputs Required:
- Project context
- Stakeholder access
- Known constraints
Outputs Produced:
- Requirements list
- Constraints matrix
- Assumptions
- Open questions