llp-orient
Load the design rationale governing the area you're about to touch, before touching it. This is the consumption side of LLP — orienting first is what turns @ref from a possibility into a habit.
Invoke as /llp-orient <path-or-task> (file, directory, subsystem, or task description). With no argument, use the current change scope (git diff --name-only).
Trigger
Start of a coding task that touches an area with documented design. The orient-first rule lives in the repo's always-loaded AGENTS.md; this skill is the detailed form that rule routes to for non-trivial work — don't rely on ambient description-match alone.
Invariants
- MUST be read-only: never edit code or LLP documents.
- MUST scope to the task: pull the constraints that bind this change, not a corpus summary.
- MUST cite, not restate: reference policy as
LLP NNNN#anchorrather than paraphrasing sections. - MUST NOT invent constraints. If something isn't documented, say so.
- MUST NOT guess the rationale behind a broken
@ref— report it and hand off tollp-maintain.
Workflow
Recipe (advisory) — read
llp/foundation/first (the kernel; the root LLP is there onceActive— on a fresh adoption it is stillDraftand sits incurrent/), then skimllp/current/(the declared working set); both hold relative links — symlinks, or small files containing the relative path — solsanswers and either form resolves. Then the root LLP's systems vocabulary.Grep '@ref'over the files in scope andReadeach target — these are the highest-signal context.Grepthe**Systems:**headers acrossllp/for LLPs governing the subsystems touched; read the governing ones (Spec, Decision, Principles, relevant RFCs). FollowRelated:and nearby@reftargets one hop out; stop there unless something is clearly load-bearing. Stale-pin nudge (skip offline): read the installed tag from the skills receipt (or asource:pin), comparegit ls-remote --tags <origin>— if upstream is newer, say so in one line ("skills at v0.3.0, upstream v0.5.2 — run /llp-adopt update") and move on; never update from here.
Artifact
A context pack with these sections, faster to read than the documents it points at:
- Scope — files / subsystems queried
- Governing LLPs — numbered list, one-line gloss each; mark which are in
foundation/and which are incurrent/(in-flight — its guidance may still move) - Active constraints — bullets, each citing
LLP NNNN#anchor - Relevant rationale — the why, same citation form
- Open questions / risks for this area
- Likely doc updates if the change lands
- Hand-off — one of
none | llp-adopt | llp-create | llp-review | llp-maintain
Hand-offs
- No corpus (
llp/missing or stub) →llp-adopt. - The task needs a decision no LLP covers →
llp-create(orllp-reviewif proposal-shaped). - An
@reftarget or anchor doesn't resolve →llp-maintain.