resil-replay
Domain: resil · Model class: cheap
Description
Section titled “Description”Use when a user wants their orchestrator to learn from past runs and improve routing strategy over time without retraining a model. Triggers: “learn from past runs”, “workflow memory”, “consolidate experience”, “reflection loop”, “meta-learning for orchestrator”, “hippocampal replay”, “improve routing from history”, “make the orchestrator smarter over time”, orchestrator “keeps making the same mistakes”. Also trigger when someone wants a scheduled review of their workflow performance logs.
Purpose
Section titled “Purpose”Buffer N ExecutionTrace objects (FIFO or quality-weighted eviction). At trigger, run reflection agent over buffer+current strategy. Agent outputs routing_strategy_update; inject into orchestrator system prompt.
Trigger Phrases
Section titled “Trigger Phrases”- “learn from past runs”
- “workflow memory”
- “consolidate experience”
- “reflection loop”
- “meta-learning for orchestrator”
- “hippocampal replay”
- “improve routing from history”
- “make the orchestrator smarter over time”
- “keeps making the same mistakes”
- “scheduled review of workflow performance logs”
Anti-Triggers
Section titled “Anti-Triggers”- the user wants a one-off improvement without ongoing adaptation or structural change
Intake Questions
Section titled “Intake Questions”- What traces or run logs should be replayed?
- How many traces and what mix of successes/failures should consolidation use?
- What strategy update or injection mode can modify the orchestrator safely?
- How often should replay consolidation run and what metrics define improvement?
Output Contract
Section titled “Output Contract”- failure mode analysis
- recovery strategy
- operational checks
- validation notes
Related Skills
Section titled “Related Skills”flow-orchestrator · orch-agent-orchestrator · prompt-chaining