strategy-pivot-designer

Name: strategy-pivot-designer
Availability: InStock
Author: fabio29t

Detect backtest stagnation and generate strategy pivot proposals from iteration history JSON files.

2|Updated Mar 4, 2026

Search Tags:#backtesting #trading strategy #stagnation detection #algorithmic trading #strategy design #pivot generation

Ready to run

npx skills add https://github.com/Fabio29T/Trading-Skills --skill strategy-pivot-designer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: strategy-pivot-designer
Source: https://github.com/Fabio29T/Trading-Skills/tree/main/skills/strategy-pivot-designer
Command: npx skills add https://github.com/Fabio29T/Trading-Skills --skill strategy-pivot-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill helps overcome strategy development stagnation by automatically detecting when backtest results have plateaued and generating fundamentally different strategy designs.

Core Features & Use Cases

Stagnation Detection: Identifies plateaus, overfitting, cost defeat, and tail risk using deterministic triggers.
Pivot Generation: Proposes new strategy architectures via assumption inversion, archetype switching, and objective reframing.
Use Case: When your trading strategy's performance metrics stop improving despite parameter tuning, this Skill can suggest entirely new approaches to break through the local optimum.

Quick Start

Use the strategy-pivot-designer skill to generate new pivot proposals based on the provided iteration history file.

Frequently Asked Questions about strategy-pivot-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I break through a trading strategy plateau when parameter tuning stops improving backtest results?▼

To break through a trading strategy plateau, you can detect backtest iteration stagnation and generate structurally different strategy pivot proposals. This approach analyzes iteration history files to identify local optima and suggests new architectures using assumption inversion and archetype switching.

What causes backtest stagnation in algorithmic trading strategies?▼

Backtest stagnation in algorithmic trading is caused by deterministic triggers like performance plateaus, overfitting, cost defeat, or tail risk. Detecting these conditions in iteration history files helps identify when a strategy has reached a local optimum and needs structural changes.

How do I generate new trading strategy designs when my current architecture overfits the data?▼

To generate new trading strategy designs when overfitting occurs, you can apply objective reframing and assumption inversion techniques. These methods propose fundamentally different strategy architectures instead of continuing ineffective parameter tuning on the current model.

Can I detect tail risk and overfitting in my backtest iteration history JSON files?▼

Yes, you can detect tail risk and overfitting by analyzing backtest iteration history JSON files. The analysis uses deterministic triggers to evaluate iteration history and automatically identify when strategy performance metrics degrade or plateau.

What is the best way to pivot an algorithmic trading strategy that has reached a local optimum?▼

The best way to pivot an algorithmic trading strategy from a local optimum is using archetype switching and objective reframing. This generates structurally different strategy designs rather than making incremental parameter adjustments to the existing architecture.

Do I need specific iteration history formats to detect strategy stagnation?▼

Yes, you need iteration history JSON files to detect strategy stagnation. The analysis reads these files to evaluate parameter tuning iterations and identify deterministic triggers like plateaus, cost defeat, and tail risk for pivot generation.