shipkit-directionlisted

# shipkit-direction — Define the Foundation **Purpose**: The consumer-facing **DIRECTION** entry point. Takes a project (a repo, a one-line goal, or nothing) and drives the definitional foundation — vision → stage → users → product → engineering → goals — to a coherent bar, **autonomously**: it proposes everything it can ground in a cited signal and asks only the few high-leverage decisions. **shipkit-direction is a thin caller.** It does not implement its own loop — it states the *what* (steps + bar + which steps are elicitive) and hands off to the engine (`shipkit-orchestrate`), which owns the *how* (dispatch → reconcile → re-dispatch → stop-at-bar, with elicitation bubbled to the main session). This replaces the previous forked direction loop. **Read first**: `install/shared/references/ground-or-ask-calibration.md` (the propose-vs-ask rule), `install/shared/references/elicitation-protocol.md` (the marker/resume mechanics the elicitive steps use), and `install/shared/references/core-automation.md` (the engine contract). --- ## What it does Invoke **`shipkit-orchestrate` in `autonomous` mode** (propose variant) over the Direction steps. The engine runs inline in the main session, dispatches each step, reconciles its artifact against the bar, bubbles any elicitation marker to the user, and stops when the foundation is coherent. Pass the engine the four inputs (calling interface in `shipkit-orchestrate/SKILL.md`): | Input | For Direction | |-------|---------------| | *