@forwardimpact/outpost 3.11.0 → 3.12.1

package/templates/.claude/skills/anarlog-follow/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: anarlog-follow
 description: >
-  Follow a live Anarlog session in real-time, coaching the user through a
+  Follow a live Anarlog session in real-time and coach the user through a
   meeting or interview. Understands context from the session title, knowledge
   base, and candidate pipeline. Provides talking points, flags gaps in
   coverage, and suggests follow-up questions as the conversation unfolds.
@@ -10,48 +10,49 @@ description: >
 
 # Anarlog Follow
 
-Follow a live Anarlog recording, read the transcript as it grows, and coach the
-user through the meeting in real time. Gather knowledge-base context once before
-the session, then poll the transcript and provide actionable nudges as new
-content appears.
+Follow a live Anarlog recording. Read the transcript as it grows. Coach the user
+through the meeting in real time. Gather knowledge-base context once before the
+session. Then poll the transcript. Provide actionable nudges as new content
+appears.
 
 ## Trigger
 
 - The user asks to follow, shadow, or coach them through a live meeting.
 - "Follow my meeting", "coach me", "shadow this call".
-- The user starts a Anarlog recording and wants real-time support.
+- The user starts an Anarlog recording and wants real-time support.
 
 ## Prerequisites
 
-- Anarlog installed; sessions at
+- Anarlog installed. Sessions live at
   `~/Library/Application Support/anarlog/sessions/`.
 - An active or about-to-start session.
-- Knowledge base populated (attendee / candidate context).
+- A populated knowledge base (attendee / candidate context).
 
 ## Inputs
 
-- Live `transcript.json` (growing during the session).
+- Live `transcript.json` (it grows during the session).
 - `Knowledge/People/`, `Knowledge/Candidates/{Name}/{brief,screening,panel}.md`,
   `Knowledge/Roles/`, `Knowledge/Organizations/`, `Knowledge/Projects/`.
 - `~/.cache/fit/outpost/apple_calendar/*.json` for context.
 
 ## Outputs
 
-- Real-time coaching messages printed to the user.
-- **No files are written.** This skill is purely advisory.
+- This skill prints real-time coaching messages to the user.
+- **This skill writes no files.** It only advises.
 
 <do_confirm_checklist goal="Verify the follow session was useful and read-only">
 
-- [ ] Active session detected and confirmed with the user.
-- [ ] Meeting type classified from the title.
-- [ ] Knowledge-base context gathered for all attendees.
-- [ ] For interviews: standard expectations and screening focus areas loaded.
-- [ ] Coaching nudges were actionable and concise (1–3 lines each).
-- [ ] Coverage gaps tracked and surfaced before the meeting ended.
-- [ ] End-of-meeting detected; debrief provided.
-- [ ] Next steps offered (`req-assess` / `anarlog-process`); user decided
-      whether to run them.
-- [ ] No files were modified during the session.
+- [ ] Detect the active session and confirm it with the user.
+- [ ] Classify the meeting type from the title.
+- [ ] Gather knowledge-base context for all attendees.
+- [ ] For interviews, load the standard expectations and the focus areas from
+      screening.
+- [ ] Keep each coaching nudge actionable and concise (1–3 lines).
+- [ ] Track the coverage gaps. Surface them before the meeting ends.
+- [ ] Detect the end of the meeting. Debrief the user.
+- [ ] Offer the next steps (`req-assess` / `anarlog-process`). Let the user
+      decide whether to run them.
+- [ ] Modify no file during the session.
 
 </do_confirm_checklist>
 
@@ -65,10 +66,10 @@ content appears.
 node .claude/skills/anarlog-follow/scripts/follow.mjs --detect
 ```
 
-Returns the most recently modified session, whether it's live, and its title. If
-nothing has been modified in the last 5 minutes, warn the user and ask whether
-to follow a specific session. If multiple sessions could be active, confirm with
-the user.
+The script returns the most recently modified session, whether it is live, and
+its title. If nothing changed in the last 5 minutes, warn the user. Ask whether
+to follow a specific session. If more than one session could be active, confirm
+with the user.
 
 #### 2. Read session metadata
 
@@ -80,29 +81,29 @@ Capture **title**, **created_at**, **participants**.
 
 #### 3. Classify the meeting type
 
-Title pattern → type → coaching focus:
-[references/meeting-types.md](references/meeting-types.md). The type drives
-Phase 2 context loading and Phase 3 dimensions.
+[references/meeting-types.md](references/meeting-types.md) maps the title
+pattern → type → coaching focus. The type drives the context you load in
+Phase 2 and the dimensions you track in Phase 3.
 
 ### Phase 2 — Gather context (once)
 
 #### 4. Resolve attendees
 
-Extract names from title and participant list. For each:
+Extract the names from the title and the participant list. For each name:
 
 ```bash
 rg -l "{name}" Knowledge/People/
 rg -l "{name}" Knowledge/Candidates/
 ```
 
-Read matching notes for role, organization, history, open items, prior
+Read each note you find for role, organization, history, open items, and prior
 interactions.
 
 #### 5. Load type-specific context
 
-**Interviews:** read `Knowledge/Candidates/{Name}/{brief,screening,panel}.md`,
-look up the `Req` field's matching `Knowledge/Roles/*.md` file (check the
-`**Status:**` field for context), and load standard expectations:
+**Interviews:** read `Knowledge/Candidates/{Name}/{brief,screening,panel}.md`.
+Look up the `Req` field's matching `Knowledge/Roles/*.md` file. Check its
+`**Status:**` field for context. Then load the standard expectations:
 
 ```bash
 bunx fit-pathway job {discipline} {level} --track={track}
@@ -113,9 +114,9 @@ Project/Organization notes. Check open tasks: `rg "{name}" Knowledge/Tasks/`.
 
 #### 6. Build the coaching brief
 
-Synthesize gathered context into the pre-meeting brief format in
-[references/coaching.md](references/coaching.md#pre-meeting-brief-format) and
-print it to the user.
+Synthesize the gathered context into the pre-meeting brief format in
+[references/coaching.md](references/coaching.md#pre-meeting-brief-format). Print
+it to the user.
 
 ### Phase 3 — Follow loop
 
@@ -133,40 +134,40 @@ Subsequent reads (pass the last word ID):
 node .claude/skills/anarlog-follow/scripts/follow.mjs <session-id> --after <last-word-id>
 ```
 
-Returns JSON with grouped text segments, channel labels, and the next last-word
-ID.
+The script returns JSON with grouped text segments, channel labels, and the next
+last-word ID.
 
 #### 8. Analyze new content
 
-Track the dimensions in
-[references/coaching.md](references/coaching.md#dimensions-to-track) — interview
-vs. general — and apply the [principles](references/coaching.md#principles) and
+Track the interview dimensions or the general dimensions in
+[references/coaching.md](references/coaching.md#dimensions-to-track). Apply the
+[principles](references/coaching.md#principles) and the
 [constraints](references/coaching.md#constraints).
 
 #### 9. Provide coaching
 
-Output only when actionable. Use the
+Output only when the nudge is actionable. Use the
 [coaching output formats](references/coaching.md#coaching-output-formats). Keep
 each nudge 1–3 lines.
 
 #### 10. Detect meeting end
 
-Watch for: farewells ("bye", "take care", "have a good day"), wrap-up phrases
-("that's all", "let's wrap", "I'll let you go"), or final thank-yous with no
-substantive follow-up. When detected, move to Phase 4.
+Watch for farewells ("bye", "take care", "have a good day"). Watch for wrap-up
+phrases ("that's all", "let's wrap", "I'll let you go"). Watch for final
+thank-yous with no substantive follow-up. When you detect one, move to Phase 4.
 
 #### 11. Loop cadence
 
 **Do not use `sleep` or timed loops.** After each coaching output, read the next
-batch immediately — natural cadence emerges from read/analyze/output. On two
-consecutive empty reads, ask the user whether the meeting has ended.
+batch immediately. A natural cadence emerges from read/analyze/output. After two
+consecutive empty reads, ask the user whether the meeting ended.
 
 ### Phase 4 — Wrap-up
 
 #### 12–13. Debrief
 
-Use the appropriate template in [references/debrief.md](references/debrief.md) —
-interview vs. general.
+Pick the interview template or the general template in
+[references/debrief.md](references/debrief.md).
 
 #### 14. Offer next steps
 

package/templates/.claude/skills/anarlog-follow/references/coaching.md

@@ -45,19 +45,19 @@ Suggested topics:
 
 | Dimension               | What to watch for                                                                  |
 | ----------------------- | ---------------------------------------------------------------------------------- |
-| **Skills demonstrated** | Candidate shows (not just claims) standard skills                                  |
+| **Skills demonstrated** | Candidate shows standard skills. A claim alone does not count.                     |
 | **Behaviour signals**   | Own the Outcome, Think in Systems, Communicate with Precision, Polymath, Curiosity |
 | **Level signals**       | Autonomy, scope, complexity handling, mentoring                                    |
-| **Coverage gaps**       | Focus areas from screening that haven't been touched yet                           |
+| **Coverage gaps**       | Focus areas from screening that you did not touch yet                              |
 | **Red flags**           | Contradictions with CV, vague answers, deflection                                  |
-| **Time awareness**      | Are you running out of time with uncovered areas?                                  |
+| **Time awareness**      | Time runs out while areas stay uncovered                                           |
 
 ### General meetings
 
 | Dimension             | What to watch for                                    |
 | --------------------- | ---------------------------------------------------- |
-| **Open items**        | Were pending items raised and addressed?             |
-| **Decisions**         | What was decided? Who owns next steps?               |
+| **Open items**        | Someone raised and addressed the pending items       |
+| **Decisions**         | The decisions made, and who owns the next steps      |
 | **New commitments**   | Track who committed to what                          |
 | **Unasked questions** | Topics the user should raise before the meeting ends |
 | **Tone/dynamics**     | Shifts in energy, resistance, enthusiasm             |
@@ -81,30 +81,31 @@ Capture: decision made on {topic} — {who} will {what}
 
 - **Standard-grounded.** Every nudge ties to standard skills/behaviours. Don't
   coach on vibes.
-- **Evidence over claims.** Flag _claims_ vs. _demonstrations_; push for
+- **Evidence over claims.** Flag _claims_ vs. _demonstrations_. Push for
   specific examples.
-- **Coverage-aware.** Track which screening focus areas have been explored and
-  nudge before time runs out.
-- **Level-calibrated.** Know what the target level expects; flag
+- **Coverage-aware.** Track which screening focus areas you explored. Nudge
+  before time runs out.
+- **Level-calibrated.** Know what the target level expects. Flag
   below-/above-level answers.
-- **Don't lead.** Suggest open-ended probes, never loaded or leading questions.
+- **Don't lead.** Suggest open-ended probes. Never suggest a loaded or leading
+  question.
 
 ### General meetings
 
 - **Agenda-aware.** Track coverage of known topics or open items.
 - **Decision-focused.** Flag decisions and capture owners.
-- **Commitment-tracking.** Note who said they'd do what; surface unresolved
-  commitments from prior meetings.
-- **Time-conscious.** Nudge when the meeting is running long and key topics
-  aren't raised.
+- **Commitment-tracking.** Note who said they would do what. Surface unresolved
+  commitments from earlier meetings.
+- **Time-conscious.** Nudge when the meeting runs long and nobody raises the key
+  topics.
 
 ### Universal
 
-- **Be quiet when things are going well.** Speak only when actionable.
-- **Channel awareness.** Channel 0 = user; channel 1+ = guest(s). Reference what
-  the _guest_ said — the user already knows what they said.
+- **Be quiet when things go well.** Speak only when actionable.
+- **Channel awareness.** Channel 0 = user. Channel 1+ = guest(s). Reference what
+  the _guest_ said. The user already knows what they said.
 - **Never interrupt flow.** Hold nudges for the next natural pause.
-- **Respect the user.** Coach at the margin, don't patronise.
+- **Respect the user.** Coach at the margin. Do not patronise.
 
 ## Constraints
 
@@ -113,6 +114,6 @@ Capture: decision made on {topic} — {who} will {what}
   `req-assess`, or `anarlog-process`. Offer them after.
 - **Channel 0 = user.** Always.
 - **Transcription noise.** Live transcripts are messy. Don't coach from a single
-  ambiguous word — wait for context.
-- **Privacy.** Coaching may appear on a shared screen — keep nudges generic
-  enough that they don't reveal confidential assessment detail.
+  ambiguous word. Wait for context.
+- **Privacy.** Coaching may appear on a shared screen. Keep nudges generic. They
+  must not reveal confidential assessment detail.

package/templates/.claude/skills/anarlog-follow/scripts/follow.mjs

@@ -2,7 +2,7 @@
 
 /**
  * follow.mjs — Read a live Anarlog transcript and output new content since
- * the last read. Designed to be called repeatedly during a live session.
+ * the last read. Call it repeatedly during a live session.
  *
  * Usage:
  *   node follow.mjs <session-id>                    # First read — outputs everything
@@ -75,7 +75,7 @@ function detectActiveSession() {
         best = entry;
       }
     } catch {
-      // No transcript — skip
+      // Skip when no transcript exists
     }
   }
 
@@ -84,7 +84,7 @@ function detectActiveSession() {
     process.exit(1);
   }
 
-  // Check if the transcript was modified recently (within last 5 minutes)
+  // Check whether the transcript changed in the last 5 minutes
   const ageMs = Date.now() - bestMtime;
   const isLive = ageMs < 5 * 60 * 1000;
 
@@ -188,7 +188,7 @@ function buildChannelStats(allWords) {
 function filterNewWords(allWords, afterId) {
   if (!afterId) return allWords;
   const idx = allWords.findIndex((w) => w.id === afterId);
-  // If word ID not found, return everything (safety fallback)
+  // Return everything when the word ID is missing (safety fallback)
   return idx >= 0 ? allWords.slice(idx + 1) : allWords;
 }
 

package/templates/.claude/skills/anarlog-process/SKILL.md

@@ -1,26 +1,26 @@
 ---
 name: anarlog-process
-description: Process Anarlog meeting sessions (memos, summaries, transcripts) into the knowledge graph. Extracts people, organizations, projects, and topics from AI-generated meeting summaries and user notes, creating or updating Obsidian-compatible notes in Knowledge/. Use when the user asks to process meeting notes or after Anarlog sessions.
+description: Process Anarlog meeting sessions (memos, summaries, transcripts) into the knowledge graph. Extracts people, organizations, projects, and topics from AI-generated meeting summaries and user notes. Creates or updates Obsidian-compatible notes in Knowledge/. Use when the user asks to process meeting notes or after Anarlog sessions.
 ---
 
 # Process Anarlog
 
 Process meeting sessions from Anarlog (a local AI meeting-notes app) into the
 knowledge graph. Anarlog records meetings, transcribes them, and generates AI
-summaries; this skill reads that output and feeds it into `Knowledge/` — the
-same way `extract-entities` processes emails and calendar events.
+summaries. This skill reads that output and feeds it into `Knowledge/`.
+`extract-entities` processes emails and calendar events in the same way.
 
 ## Trigger
 
 - The user asks to process meeting notes or Anarlog sessions.
-- New meetings have been recorded.
+- Anarlog recorded new meetings.
 - The user asks to update the knowledge base from recent meetings.
 
 ## Prerequisites
 
-- Anarlog installed; sessions at
+- Anarlog installed. Sessions live at
   `~/Library/Application Support/anarlog/sessions/`.
-- User identity from running the `person-identify` skill, which writes
+- The user identity. The `person-identify` skill writes it to
   `~/.cache/fit/outpost/state/identity.md`.
 
 ## Inputs
@@ -31,7 +31,7 @@ same way `extract-entities` processes emails and calendar events.
 - `~/.cache/fit/outpost/state/graph_processed` — processed-file index (TSV,
   shared with `extract-entities`).
 - `~/.cache/fit/outpost/state/identity.md` — user identity for self-exclusion
-  (written by the `person-identify` skill).
+  (the `person-identify` skill writes it).
 
 ## Outputs
 
@@ -43,17 +43,18 @@ same way `extract-entities` processes emails and calendar events.
 
 <do_confirm_checklist goal="Verify each session was processed correctly">
 
-- [ ] Empty / test / onboarding sessions skipped (per skip rules).
-- [ ] Both `_memo.md` and `_summary.md` read (when present); transcript
-      consulted only for disambiguation.
-- [ ] "Would I prep?" test applied to each person; self excluded.
-- [ ] Interview sessions wrote to `Knowledge/Candidates/`, not
-      `Knowledge/People/`.
-- [ ] All links use absolute paths `[[Folder/Name]]`.
-- [ ] Activity entries describe relationship, not communication method.
-- [ ] No new `Priorities/` auto-created (user-set only); any
-      referenced priority had its progress updated.
-- [ ] `graph_processed` updated for every processed file (memo + summary).
+- [ ] Skip the empty, test, and onboarding sessions (per the skip rules).
+- [ ] Read both `_memo.md` and `_summary.md` (when present). Consult the
+      transcript only for disambiguation.
+- [ ] Apply the "Would I prep?" test to each person. Exclude the user.
+- [ ] Write interview sessions to `Knowledge/Candidates/`. Never write them
+      to `Knowledge/People/`.
+- [ ] Use an absolute path in every link (`[[Folder/Name]]`).
+- [ ] Describe the relationship in each activity entry. Leave out the
+      communication method.
+- [ ] Auto-create no new `Priorities/` note (the user sets these). Update the
+      progress on every priority the content references.
+- [ ] Update `graph_processed` for every processed file (memo + summary).
 
 </do_confirm_checklist>
 
@@ -72,12 +73,13 @@ node .claude/skills/anarlog-process/scripts/scan.mjs
 Flags: `--changed` (also detect changed memo/summary hashes), `--json`
 (programmatic output), `--count` (count only), `--limit N` (default 20).
 
-A session needs processing when its `_memo.md` is not in `graph_processed`, or
-its hash has changed (`--changed`), or its `_summary.md` exists and is not in
-`graph_processed` (or has changed).
+Process a session when its `_memo.md` is not in `graph_processed`. Also process
+it when the memo hash changed (`--changed`). Also process it when its
+`_summary.md` exists and is not in `graph_processed`, or when the summary
+changed.
 
 Process all unprocessed sessions in one run. **Don't write bespoke scan
-scripts** — this script handles the edge cases (empty memos, missing summaries,
+scripts.** This script handles the edge cases (empty memos, missing summaries,
 metadata fallback).
 
 ### 1. Build the knowledge index
@@ -95,8 +97,8 @@ as `extract-entities` Step 0).
 
 For each unprocessed session, read in this order: `_meta.json`, `_memo.md`,
 `_summary.md` (if present), `transcript.json` (only when disambiguation requires
-it). File shapes and skip rules:
-[references/sessions.md](references/sessions.md).
+it). See [references/sessions.md](references/sessions.md) for the file shapes
+and the skip rules.
 
 ### 3. Classify the source
 
@@ -104,19 +106,20 @@ Anarlog sessions are **meetings** and follow the meeting rules from
 `extract-entities`:
 
 - **Can create** People, Organization, Project, and Topic notes.
-- **Can update** existing notes — including Priorities, which are
-  user-set and never auto-created.
+- **Can update** existing notes, including Priorities. The user sets a
+  Priority. Nothing auto-creates one.
 - **Can detect** state changes.
 
 Apply the "Would I prep for this person?" test from `extract-entities` Step 5
-before creating a person note.
+before you create a person note.
 
 ### 4. Extract entities and content
 
-Combine memo and summary content (prefer summary when both exist). Extraction
-signals — entity types, decisions, commitments, key facts, activity-line format,
-interview-note rules, and linking rules — live in
-[references/extraction.md](references/extraction.md).
+Combine the memo and the summary content (prefer the summary when both exist).
+The extraction signals live in
+[references/extraction.md](references/extraction.md). They cover entity types,
+decisions, commitments, key facts, the activity-line format, the interview-note
+rules, and the linking rules.
 
 ### 5. Write updates
 
@@ -125,7 +128,7 @@ For **new** entities, use the templates in
 sessions, use the candidate brief template from `req-track` (under
 `Knowledge/Candidates/`).
 
-For **existing** entities, apply targeted edits — never rewrite the file:
+For **existing** entities, never rewrite the file. Apply targeted edits:
 
 - Add the new activity entry at the **top** of `## Activity`.
 - Update `Last seen` / `Last activity`.

package/templates/.claude/skills/anarlog-process/references/extraction.md

@@ -12,35 +12,38 @@ Look for names in:
   platform team").
 - `_meta.json` participants.
 
-For each: resolve against the knowledge index (Step 0); extract role,
-organization, relationship to the user; note what was discussed.
+For each name, resolve it against the knowledge index (Step 0). Extract the
+role, the organization, and the relationship to the user. Note what they
+discussed.
 
 ## Organizations
 
-Explicit mentions ("Acme Corp"), or inferred from people's roles or the
-surrounding context.
+Look for explicit mentions ("Acme Corp"). Also infer an organization from a
+person's role or from the context.
 
 ## Projects
 
-Explicit project names ("Customer Portal", "Q2 Migration") or described
-initiatives ("the hiring pipeline", "the product launch").
+Look for explicit project names ("Customer Portal", "Q2 Migration"). Also look
+for initiatives that the text describes ("the hiring pipeline", "the product
+launch").
 
 ## Topics
 
-Recurring themes ("AI coding agents", "interview process", "architecture
-decisions"). Only create a Topic note when the subject spans multiple meetings
-or is strategically important.
+Look for themes that repeat ("AI coding agents", "interview process",
+"architecture decisions"). Only create a Topic note when the subject spans
+multiple meetings or is strategically important.
 
 ## Self-exclusion
 
-Never create or update a note for the user — match against name, email, or
-`@domain` from `~/.cache/fit/outpost/state/identity.md`.
+Never create or update a note for the user. Match against the name, the email,
+or the `@domain` from `~/.cache/fit/outpost/state/identity.md`.
 
 ## Interview sessions (special case)
 
-If the title or memo indicates "interview with {Name}", the interviewee is a
-**candidate** — create or update their note in `Knowledge/Candidates/` (using
-the candidate brief template from `req-track`), **not** in `Knowledge/People/`.
+If the title or the memo says "interview with {Name}", the interviewee is a
+**candidate**. Create or update their note in `Knowledge/Candidates/` with the
+candidate brief template from `req-track`. **Never** write it in
+`Knowledge/People/`.
 
 ## Content signals
 
@@ -51,13 +54,14 @@ the candidate brief template from `req-track`), **not** in `Knowledge/People/`.
 ### Commitments / action items
 
 "will share", "plans to", "needs to", "to be created", "will upload". Extract
-owner, action, deadline (if any), status (default `open`).
+the owner, the action, the deadline (if any), and the status (default `open`).
 
 ### Key facts
 
-Specific numbers (headcount, budget, timeline), preferences ("non-traditional
-backgrounds"), process details (interview stages, evaluation criteria),
-strategic context (market trends, competitive landscape). Skip filler.
+Look for specific numbers (headcount, budget, timeline) and preferences
+("non-traditional backgrounds"). Look for process details (interview stages,
+evaluation criteria) and strategic context (market trends, competitive
+landscape). Skip filler.
 
 ### Activity summary
 
@@ -71,8 +75,8 @@ One line per session per entity:
 
 ### Interview notes (for candidates)
 
-Add to the candidate's `## Notes` section: impressions, technical assessment,
-strengths and concerns, any interview scoring or decisions.
+Add these to the candidate's `## Notes` section: impressions, the technical
+assessment, strengths and concerns, and any interview scores or decisions.
 
 ## Linking rules
 
@@ -80,5 +84,5 @@ Use absolute paths everywhere: `[[People/Name]]`, `[[Organizations/Name]]`,
 `[[Projects/Name]]`, `[[Priorities/Priority Name]]`.
 
 When meeting content references an existing Priority, follow the linking
-rules in `extract-entities` Step 7c — update progress and add backlinks, but
-**never** auto-create Priority notes.
+rules in `extract-entities` Step 7c. Update the progress and add the backlinks.
+**Never** auto-create Priority notes.

package/templates/.claude/skills/anarlog-process/references/sessions.md

@@ -15,8 +15,8 @@ Reference for `anarlog-process` Step 1. Each session lives at
 }
 ```
 
-Use: session date (from `created_at`), title, participants (often empty —
-Anarlog doesn't reliably populate this).
+Use the session date (from `created_at`), the title, and the participants.
+Anarlog does not reliably populate the participants, so the list is often empty.
 
 ## `_memo.md`
 
@@ -31,12 +31,12 @@ session_id: 213e0f78-a66a-468d-b8e5-bc3fbbe04bf4
 Chat with Sarah about the product roadmap.
 ```
 
-High-signal — every name and observation is intentional.
+The memo is high-signal. Every name and every observation is intentional.
 
 ## `_summary.md` (optional)
 
 YAML frontmatter (`id`, `position`, `session_id`, `title`) plus an AI-generated
-summary — typically the richest source:
+summary. The summary is typically the richest source:
 
 ```markdown
 ---
@@ -64,18 +64,18 @@ title: Summary
 }
 ```
 
-**Do not extract entities from the full transcript** — too noisy. Consult it
-only to disambiguate a name from the memo or summary, confirm who said what
-(channel 0 = user, channel 1 = other speaker), or find context around a specific
-topic or decision.
+**Do not extract entities from the full transcript.** It is too noisy. Consult
+it only for these purposes. Disambiguate a name from the memo or the summary.
+Confirm who said what (channel 0 = user, channel 1 = other speaker). Find
+context around a specific topic or decision.
 
 ## Skip rules
 
-A session is skipped when **all** of:
+Skip a session when **all** of these are true:
 
 - `_memo.md` body is empty or only ` ` / whitespace.
 - No `_summary.md` exists.
-- Title is empty or generic ("Hello", "Welcome to Anarlog", "Test").
+- The title is empty or generic ("Hello", "Welcome to Anarlog", "Test").
 
 Process a session if it has **either** a substantive memo **or** a
 `_summary.md`.

package/templates/.claude/skills/anarlog-process/scripts/scan.mjs

@@ -2,9 +2,10 @@
 /**
  * Scan for unprocessed Anarlog sessions.
  *
- * Compares session _memo.md and _summary.md files against the graph_processed
- * state file to identify sessions that need processing. Reports unprocessed
- * sessions with title, date, and content preview.
+ * This script compares session _memo.md and _summary.md files against the
+ * graph_processed state file. It finds the sessions you must still process. It
+ * reports each unprocessed session with a title, a date, and a content
+ * preview.
  *
  * Usage:
  *   node scripts/scan.mjs              List unprocessed sessions
@@ -29,9 +30,9 @@ Usage:
   node scripts/scan.mjs [options]
 
 Options:
-  --changed    Also detect sessions whose memo/summary hash has changed
-  --json       Output as JSON array
-  --count      Just print the unprocessed count (for scripting)
+  --changed    Also detect sessions whose memo/summary hash changed
+  --json       Output as a JSON array
+  --count      Just print the unprocessed count (for scripts)
   --limit N    Max sessions to display (default: 20)
   -h, --help   Show this help message
 
@@ -61,14 +62,14 @@ if (existsSync(STATE_FILE)) {
 }
 
 /**
- * Compute SHA-256 hash of file contents.
+ * Compute the SHA-256 hash of the file contents.
  */
 function fileHash(filePath) {
   return createHash("sha256").update(readFileSync(filePath)).digest("hex");
 }
 
 /**
- * Check if a file needs processing (new or changed).
+ * Check whether the script must process a file (new or changed).
  */
 function needsProcessing(filePath) {
   const storedHash = state.get(filePath);
@@ -81,7 +82,7 @@ function needsProcessing(filePath) {
 }
 
 /**
- * Extract title and date from a memo file.
+ * Extract the title and the date from a memo file.
  */
 function parseMemo(memoPath) {
   try {