Split run_plan_pipeline.py into individual stage files#491
Merged
Conversation
…plit Design spec and 11-task implementation plan for splitting the 4,257-line run_plan_pipeline.py into ~66 individual stage files under stages/. Optimized for parallel agent work, self_improve/ integration, and conflict-free DAG insertion. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Extract StartTimeTask, SetupTask, RedlineGateTask, PremiseAttackTask, IdentifyPurposeTask, PlanTypeTask into stages/ directory. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ance) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ort) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…ipeline from stages Remove all ~66 task class definitions from run_plan_pipeline.py (3761 lines deleted) and create stages/full_plan_pipeline.py as the pipeline orchestrator that imports all task classes from individual stage files. ExecutePipeline.setup() now uses a deferred import of FullPlanPipeline to avoid circular dependencies. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
run_plan_pipeline.py(4,257 lines) into ~64 individual stage files understages/, each containing one Luigi task classrun_plan_pipeline.pyto 562 lines (framework only:PlanTask,ExecutePipeline, utilities)stages/full_plan_pipeline.pyas the DAG orchestrator importing all stagesAGENTS.mdwith convention for new stagesThis enables:
self_improve/targeting individual step filesrequires())What does NOT change
worker_plan_database/app.pyor any external consumerTest plan
run_plan_pipeline_task_class_to_step_labeltest still passes🤖 Generated with Claude Code