scoobydrew83 Next Step
Use this as the calm on-ramp into a project. Read available state before asking
the user to repeat it. Run scripts/route_next.py when the project has a loop
queue; it is read-only and returns the first legal transition.
Respond in this order:
- Status — one sentence: what is known, current queue state, and whether work is safe to start.
- One next action — concrete, bounded, and sized to the available evidence.
- Why this action — only the material constraint or dependency.
- Decision needed — only when a human gate or missing criterion blocks it; state the smallest decision that unblocks work.
Never turn an unknown into a confident plan. Missing criteria, contradictory
state, or a required gate is a useful answer, not a failure. If the person is
overwhelmed, hand off before presenting a long route. If a consequential
assumption blocks planning, create a decision card with assumption-grill.
Next steps: When a known queue item is ready, suggest conductor-router to
advance its lifecycle. When an unresolved material assumption exists, suggest
assumption-grill. If the task is large and emotionally hard to enter, suggest
overwhelm-breakdown; if it is settled and multi-stage, suggest
agent-orchestration.