| name | eve-planning |
| description | Use for multi-step EVE tasks that require planning, dependency tracking, or replanning after failures. |
When to use
When a user request requires multiple data fetches, cross-referencing, or sequential logic. Examples:
- "What's the profit margin on building a Rifter?"
- "Show my wallet history and correlate with market prices"
- "What ships can I fly with my current skills?"
Workflow
- Break the task into short steps (max 6-8 steps).
- Separate data fetching from analysis.
- Mark dependencies between steps using
depends_on.
- Call
update_plan to persist the plan.
- Execute steps in dependency order.
- Update step status after each execution.
- Replan on failure instead of retrying blindly.
Step statuses
pending -- not started
running -- in progress
done -- completed successfully
blocked -- waiting on dependency or missing scope
failed -- failed, needs replanning
Replanning rules
- If a step fails due to missing scope, mark it
blocked and suggest auth.
- If a step fails due to ESI error, try an alternative approach.
- If no alternative exists, mark the step
failed and inform the user.
- Never retry the exact same call more than once.