J-stock

Use when: generating worker-ready JSON manifests for J-stock evaluation, pos-evaluation, walk-forward-evaluate, or replay-evaluation batch execution. Resolve WebUI-equivalent defaults, split jobs by worker during generation, and stop before execution.

Use when: orchestrating an end-to-end J-stock batch evaluation workflow, or when the user explicitly names evaluation-batch-runner. Schedule evaluation-batch-generator, evaluation-batch-executor, and evaluation-result-summary in order, preserving the manifest approval boundary and allowing subagent delegation only during approved execution.

Use when: aggregating completed J-stock evaluation output directories into markdown summary reports under G:/My Drive/AI-Stock-Sync/summary without rerunning backtests, including global MDD-Win re-scoring via tools/score_evaluation_outputs.py when worker-local PRS is not comparable.

Use when generating training-window entry-signal-analysis datasets for a J-stock stock-pool experiment, especially scanning a broad/full universe with a fixed entry strategy before ticker-level pool selection.

Use when orchestrating a J-stock custom stock-pool experiment where a fixed entry condition is applied to a broad/full universe during a training window, good tickers are selected into one or more test universes, and those universes are evaluated out-of-sample against current and full-pool controls.

Use when generating approval-ready J-stock out-of-sample evaluation commands or batch manifests that compare trained selected stock pools against current production and broad/full universe controls.

Use when reviewing completed J-stock custom stock-pool out-of-sample evaluations, comparing selected pools with current and full-pool controls, and auditing leakage or survivorship-bias risks.

Use when designing leakage-safe train/test windows, universe controls, and pool-size variants for J-stock experiments that select tickers from historical entry-signal performance before out-of-sample evaluation.

Use when aggregating J-stock training-period entry-signal-analysis or entry-exit-validation CSV artifacts by ticker, scoring ticker robustness, and exporting selected stock-pool universe JSON files for out-of-sample evaluation.

Use when: generating worker-ready JSON manifests for J-stock evaluation, pos-evaluation, walk-forward-evaluate, or replay-evaluation batch execution. Resolve WebUI-equivalent defaults, split jobs by worker during generation, and stop before execution.

Use when: orchestrating an end-to-end J-stock batch evaluation workflow, or when the user explicitly names evaluation-batch-runner. Schedule evaluation-batch-generator, evaluation-batch-executor, and evaluation-result-summary in order, preserving the manifest approval boundary and allowing subagent delegation only during approved execution.

Use when designing or refactoring J-stock Python architecture, introducing new services/classes, separating business logic from I/O, or reviewing object-oriented code for hidden state and testability.

Use when adding or updating Python dependencies, writing standalone Python scripts, documenting local setup, or choosing Python execution commands in the J-stock repository where uv is the preferred workflow.

Use when editing or reviewing J-stock Python code where type clarity, boundary validation, error context, or reduction of unsafe dynamic values materially affects correctness or maintainability.

Use when: executing an already-approved worker-ready J-stock batch manifest. Launch one parent runner command from the current agent session, keep the manifest unchanged, and own bounded monitoring until completion or an explicit leave-running handoff.

Use when: aggregating completed J-stock evaluation output directories into markdown summary reports under G:/My Drive/AI-Stock-Sync/summary without rerunning backtests.