@troylar/sightline 1.182.0 → 1.183.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@troylar/sightline",
-  "version": "1.182.0",
+  "version": "1.183.0",
   "description": "Your team's work, in plain sight. One HTML delivery planner, Jira context, and human-reviewed AI planning.",
   "license": "MIT",
   "keywords": [

package/skills/sightline-plan/SKILL.md

@@ -40,7 +40,21 @@ Answer from the context only, and say what it doesn't cover.
 
 - **What should I work on?** Go by the team's work order, then each outcome's class (rock = committed, pebble = supports a commitment, sand = if there's room) and its "why it matters". Name the next ready item for that person and what it serves. If the order is empty, say so instead of inventing one.
 - **Can we take this on? / How are we against capacity?** Use Sightline's forecast and capacity figures, never your own schedule. Missing effort means "can't tell yet: it has no estimate", and name what estimate would answer it. Say what would wait.
-- **Why is X above Y?** Quote the recorded reasons, who set them and when. If there's no recorded reason, say so.
+- **Why is X above Y?** Quote the recorded reasons, who set them and when. If there's no recorded reason, say so. Then, separately, say what today's guidance would suggest (see "What matters now").
+
+## What matters now
+
+`planning.guidance` holds what the team is weighing this period: a statement, why, scope (`lanes`; none = whole plan), `from`, `through`, `reviewOn`, who set it, its state and the decisions that cited it (`citedBy`). Name the entry and its dates when it shapes an answer.
+
+- **Keep two things apart:** what a decision recorded at the time (its text and the guidance it cites), and what today's guidance would suggest. Never explain an old decision with guidance it didn't cite.
+- **"Next quarter we focus on cost":** ask the one thing missing (dates, or what "cost" means here). Propose `guidance.add` with why, dates and a review date; any reorder is a separate `initiative.order`. Both wait for review.
+- **It changed:** new wording, reason, end or review date is `guidance.set`. A new meaning, scope or start is `guidance.add` with `supersedes`, which ends the old entry. Ending (`through`) is normal; `guidance.del` is for mistakes.
+- **A decision made because of it:** add the entry's ID to the decision's `guidance` list.
+- **Conflicts:** if entries pull different ways, say so and ask who decides; never settle it by which is newer, narrower or more senior.
+- **People:** guidance says whose input to seek and who decides, naming people in the plan or a role. Never count one person's requests for more or anyone's for less.
+- **When it ends,** nothing moves. Name the decisions that cited it and ask whether they still hold.
+
+Give no score; explain with facts a person can check.
 
 ## Prep our grooming