Strategy Pivot Designer is the feedback step of a strategy research pipeline. It reads an iteration history built from backtest evaluations, checks for stagnation triggers such as a score plateau, overfitting, transaction costs defeating a thin edge, a weak profit factor or tail risk, and then generates pivot proposals.
Proposals come from three techniques: assumption inversion, archetype switch and objective reframe. They are scored for quality potential and novelty, and written as strategy draft YAML that the next backtest cycle can pick up. The skill describes research drafts and does not give investment advice.
What You Get
- A stagnation diagnosis JSON that names which triggers fired: plateau, overfitting, cost defeat, insufficient profit factor or tail risk
- Ranked pivot drafts split into research-only YAML and exportable YAML with a ticket for the candidate pipeline
- A Markdown pivot report and a manifest JSON listing every generated file
- A review-required stop that tells you to repair broken metrics before any pivot is generated
Common Use Cases
- Backtest scores keep flattening after several refinement rounds and you want a different architecture to try
- A strategy looks strong in-sample but weak on robustness checks and needs a redesign
- Trading costs wipe out a thin edge and the same hypothesis needs a lower-turnover form
What Makes It Unique
Most strategy tools tune parameters. This one starts from evidence that tuning has stopped helping, refuses to generate pivots when the underlying metrics need repair, and then changes the strategy structure with three named techniques. It plugs into the Edge pipeline of sibling skills, so its output feeds straight back into the backtest step.
Under The Hood
The skill is driven by two local Python scripts that need PyYAML. One appends backtest evaluation results to a history file and detects stagnation; the other generates pivot drafts from the diagnosis and a source strategy draft. Both run as shell commands and write JSON, YAML and Markdown files into a reports folder. The skill does not call any web service and needs no API key. Its reference files describe the stagnation triggers, strategy archetypes, pivot techniques and the proposal schema.