Back to Prompt Library
planning
Define LangGraph State and Nodes for Scheduling
Inspect the original prompt language first, then copy or adapt it once you know how it fits your workflow.
Linked challenge: Agentic Sports Scheduler
Format
Code-aware
Lines
1
Sections
1
Linked challenge
Agentic Sports Scheduler
Prompt source
Original prompt text with formatting preserved for inspection.
1 lines
1 sections
No variables
0 checklist items
Design the `State` object for your LangGraph workflow, including parameters like `current_schedule`, `constraints`, `teams`, `venues`, `budget_remaining`, `conflict_history`. Define at least 4 key `nodes` (e.g., 'Initial Draft', 'Constraint Checker', 'Refinement', 'Tool Executor') and describe their function within the scheduling process.
Adaptation plan
Keep the source stable, then change the prompt in a predictable order so the next run is easier to evaluate.
Keep stable
Preserve the role framing, objective, and reporting structure so comparison runs stay coherent.
Tune next
Swap in your own domain constraints, anomaly thresholds, and examples before you branch variants.
Verify after
Check whether the prompt asks for the right evidence, confidence signal, and escalation path.