Onboarding should feel smoother.
Hermes clarifies the target user, pain, success signal, and non-goals before planning.
Flagship lane
Intent to plan
Use this lane when a user gives Hermes a fuzzy product, technical, or goal-shaped request. Hermes should not jump straight to coding. It should clarify, plan, lock acceptance criteria, and then create a durable goal or handoff only when the shape is ready.
Plain request
"Make onboarding feel smoother" is not yet a coding task. It needs intent, non-goals, user value, acceptance criteria, and a plan that can survive review.
vague request
deep-interview
ralplan
ultragoal
status
Use cases
This refactor feels risky.
Hermes names scope, rollback, tests, and review gates before an executor sees the work.
Improve the whole repo quality.
Hermes turns ambition into checkpoints, acceptance criteria, and observed evidence requirements.