Edge Strategy Designer
Overview
Translate concept-level hypotheses into concrete strategy draft specs. This skill sits after concept synthesis and before pipeline export validation.
When to Use
- You have
edge_concepts.yamland need strategy candidates. - You want multiple variants (core/conservative/research-probe) per concept.
- You want optional exportable ticket files for interface v1 families.
Prerequisites
- Python 3.9+
PyYAMLedge_concepts.yamlproduced by concept synthesis
Output
strategy_drafts/*.yamlstrategy_drafts/run_manifest.json- Optional
exportable_tickets/*.yamlfor downstreamexport_candidate.py
Workflow
- Load
edge_concepts.yaml. - Choose risk profile (
conservative,balanced,aggressive). - Generate per-concept variants with hypothesis-type exit calibration.
- Apply
HYPOTHESIS_EXIT_OVERRIDESto adjust stop-loss, reward-to-risk, time-stop, and trailing-stop per hypothesis type (breakout, earnings_drift, panic_reversal, etc.). - Clamp reward-to-risk at
RR_FLOOR=1.5to prevent C5 review failures. - Export v1-ready ticket YAML when applicable.
- Hand off exportable tickets to
skills/edge-candidate-agent/scripts/export_candidate.py.
Quick Commands
Generate drafts only:
python3 skills/edge-strategy-designer/scripts/design_strategy_drafts.py \
--concepts /tmp/edge-concepts/edge_concepts.yaml \
--output-dir /tmp/strategy-drafts \
--risk-profile balanced
Generate drafts + exportable tickets:
python3 skills/edge-strategy-designer/scripts/design_strategy_drafts.py \
--concepts /tmp/edge-concepts/edge_concepts.yaml \
--output-dir /tmp/strategy-drafts \
--exportable-tickets-dir /tmp/exportable-tickets \
--risk-profile conservative
Resources
skills/edge-strategy-designer/scripts/design_strategy_drafts.pyreferences/strategy_draft_schema.mdskills/edge-candidate-agent/scripts/export_candidate.py