orient

Invoke the orient skill before starting nontrivial work. It walks the main flow from intent to ship and points you to grilling, ticketing, dispatch, or standalone skills based on whether the work needs a design round, a brief, or neither.

Use a standalone ticket when one worker can build the change from a single what-to-build plus acceptance criteria. Use a spec when the builder would need to ask the user about behavior, interfaces, or data shapes, or when the work spans several slices.

A phase boundary is the gap between two chunks of work in a session, such as grilling and implementation. At each boundary you decide in order: continue, clear the context, delegate to a subagent, or hand off to a fresh session via a portable markdown file.

Use handoff when the context is still relevant but the session cannot continue, because it produces an inspectable markdown file you can proofread before seeding a fresh session. Compact summaries are black boxes that can flatten decisions, so they are excluded from the decision ladder.

It is designed for projects with an agent/ directory containing tickets, research, and prototypes, and should be called before nontrivial work there. Parts of its guidance, such as bare grilling, also apply when no repository is involved.