@forwardimpact/outpost 3.3.4 → 3.5.0

package/templates/.claude/skills/deck-summarize/references/brief-template.md

@@ -1,7 +1,7 @@
 # Engineering Brief Template
 
 Reference template for `deck-summarize` Step 8. Save the assembled brief to
-`knowledge/Projects/{Project Name} - Engineering Brief.md`.
+`Knowledge/Projects/{Project Name} - Engineering Brief.md`.
 
 ```markdown
 ---

package/templates/.claude/skills/doc-collab/SKILL.md

@@ -20,12 +20,12 @@ Run when the user asks to create, edit, review, or collaborate on a document.
 ## Inputs
 
 - User's editing instructions
-- `knowledge/` — existing notes and documents
+- `Knowledge/` — existing notes and documents
 - Document to edit (user-specified or searched)
 
 ## Outputs
 
-- Created or modified documents in `knowledge/` or user-specified location
+- Created or modified documents in `Knowledge/` or user-specified location
 
 ---
 
@@ -54,8 +54,8 @@ Follow their choice for the entire session.
 Search thoroughly before saying a document doesn't exist:
 
 ```bash
-rg -l -i "roadmap" knowledge/
-find knowledge/ -iname "*roadmap*" 2>/dev/null
+rg -l -i "roadmap" Knowledge/
+find Knowledge/ -iname "*roadmap*" 2>/dev/null
 ```
 
 **If found:** Read it and proceed. **If NOT found:** Ask "I couldn't find
@@ -63,7 +63,7 @@ find knowledge/ -iname "*roadmap*" 2>/dev/null
 
 **Creating new documents:**
 
-1. Ask: "Shall I create knowledge/[name].md?"
+1. Ask: "Shall I create Knowledge/[name].md?"
 2. Create with just a title — don't pre-populate with structure
 3. Ask: "What would you like in this?"
 
@@ -97,9 +97,9 @@ don't reorganize unless asked.
 When the user mentions people, companies, or projects:
 
 ```bash
-rg -l "Name" knowledge/
-cat "knowledge/People/Person.md"
-cat "knowledge/Organizations/Company.md"
+rg -l "Name" Knowledge/
+cat "Knowledge/People/Person.md"
+cat "Knowledge/Organizations/Company.md"
 ```
 
 Use `[[wiki-links]]` to connect to other notes. Only link to notes that exist.

package/templates/.claude/skills/doc-create/SKILL.md

@@ -23,18 +23,18 @@ submission, brief, or any multi-page PDF that is not a slide deck.
 ## Inputs
 
 - User's description of the document
-- `knowledge/` — optional context about company, product, team, projects
+- `Knowledge/` — optional context about company, product, team, projects
 
 ## Outputs
 
 - An HTML file and a PDF rendered from it, placed where the user specifies
-  (default: `knowledge/Projects/`)
+  (default: `Knowledge/Projects/`)
 
 ---
 
 ## Workflow
 
-1.  Check `knowledge/` for relevant context about the company, product, team,
+1.  Check `Knowledge/` for relevant context about the company, product, team,
     projects, or people mentioned.
 2.  Ensure Playwright is installed:
     `bun install playwright && bunx playwright install chromium`

package/templates/.claude/skills/draft-emails/SKILL.md

@@ -22,13 +22,13 @@ The user asks to draft, reply to, respond to, or send an email.
 
 | Data            | Location                                     |
 | --------------- | -------------------------------------------- |
-| People          | `knowledge/People/*.md`                      |
-| Organizations   | `knowledge/Organizations/*.md`               |
+| People          | `Knowledge/People/*.md`                      |
+| Organizations   | `Knowledge/Organizations/*.md`               |
 | Email threads   | `~/.cache/fit/outpost/apple_mail/*.md`       |
 | Calendar events | `~/.cache/fit/outpost/apple_calendar/*.json` |
-| Handled IDs     | `drafts/handled` (one ID per line)           |
-| Ignored IDs     | `drafts/ignored` (one ID per line)           |
-| Draft files     | `drafts/{email_id}_draft.md`                 |
+| Handled IDs     | `Drafts/handled` (one ID per line)           |
+| Ignored IDs     | `Drafts/ignored` (one ID per line)           |
+| Draft files     | `Drafts/{email_id}_draft.md`                 |
 
 `handled` and `ignored` both exclude threads from `scan-emails.mjs`. Use
 `handled` for resolved threads (sent here, replied manually, resolved via DM);
@@ -37,7 +37,7 @@ reply).
 
 <do_confirm_checklist goal="Verify a draft is safe and ready before sending">
 
-- [ ] Sender and organization were looked up in `knowledge/` before drafting.
+- [ ] Sender and organization were looked up in `Knowledge/` before drafting.
 - [ ] Draft is a single email (not multiple variants) and matches the incoming
       tone.
 - [ ] Body has no sign-off / name / "Best" — Apple Mail signature handles it.
@@ -45,7 +45,7 @@ reply).
       direct-to-candidate draft is flagged `⚠️ RECRUITER ONLY`.
 - [ ] No sensitive personal data (health, politics, etc.) was included.
 - [ ] User has explicitly approved the draft before any send.
-- [ ] Send used `--draft <path>` so cleanup and `drafts/handled` happen
+- [ ] Send used `--draft <path>` so cleanup and `Drafts/handled` happen
       automatically.
 
 </do_confirm_checklist>
@@ -59,11 +59,11 @@ node scripts/scan-emails.mjs
 ```
 
 Outputs `email_id<TAB>subject` for unprocessed emails (those not in
-`drafts/handled` or `drafts/ignored`).
+`Drafts/handled` or `Drafts/ignored`).
 
 ### 2. Classify
 
-**Ignore** (append ID to `drafts/ignored`): newsletters, marketing, automated
+**Ignore** (append ID to `Drafts/ignored`): newsletters, marketing, automated
 notifications, spam, outbound with no reply.
 
 **Draft a response**: meeting requests, personal mail from known contacts,
@@ -73,12 +73,12 @@ Be conservative with ignore — when in doubt, draft.
 
 ### 3. Gather context
 
-Before drafting, look up the sender and organization in `knowledge/`:
+Before drafting, look up the sender and organization in `Knowledge/`:
 
 ```bash
-rg -l "sender_name" knowledge/
-cat "knowledge/People/Sender Name.md"
-cat "knowledge/Organizations/Company Name.md"
+rg -l "sender_name" Knowledge/
+cat "Knowledge/People/Sender Name.md"
+cat "Knowledge/Organizations/Company Name.md"
 ```
 
 For scheduling emails, also read the relevant calendar event:
@@ -93,7 +93,7 @@ unclear or the person has multiple contexts, **ask** rather than guess.
 
 ### 4. Write the draft
 
-Save to `drafts/{email_id}_draft.md` using the template in
+Save to `Drafts/{email_id}_draft.md` using the template in
 [references/template.md](references/template.md). Reference past interactions
 naturally; for scheduling, propose specific times from calendar availability.
 
@@ -101,7 +101,7 @@ naturally; for scheduling, propose specific times from calendar availability.
 
 Candidates **must never** be copied on internal threads about them.
 
-- Identify the candidate from the thread and `knowledge/Candidates/`.
+- Identify the candidate from the thread and `Knowledge/Candidates/`.
 - Strip the candidate from To/CC; draft to internal stakeholders only.
 - Direct-to-candidate emails carry the warning header
   `⚠️ RECRUITER ONLY — This email goes directly to the candidate.`
@@ -124,18 +124,18 @@ node scripts/send-email.mjs \
   --cc "other@example.com" \
   --subject "Re: Subject" \
   --body "Plain text body" \
-  --draft "drafts/12345_draft.md"
+  --draft "Drafts/12345_draft.md"
 ```
 
 Required: `--to`, `--subject`, `--body` (plain text). Optional: `--cc`, `--bcc`,
 `--draft`. With `--draft`, the draft file is deleted and the email ID is
-appended to `drafts/handled` automatically.
+appended to `Drafts/handled` automatically.
 
 ### 8. Mark handled without sending
 
 When a thread is resolved through other channels:
 
 ```bash
-echo "$EMAIL_ID" >> drafts/handled
-rm -f "drafts/${EMAIL_ID}_draft.md"
+echo "$EMAIL_ID" >> Drafts/handled
+rm -f "Drafts/${EMAIL_ID}_draft.md"
 ```

package/templates/.claude/skills/draft-emails/references/template.md

@@ -1,6 +1,6 @@
 # Draft File Template
 
-Save each draft to `drafts/{email_id}_draft.md` using this layout:
+Save each draft to `Drafts/{email_id}_draft.md` using this layout:
 
 ```markdown
 # Draft Response

package/templates/.claude/skills/draft-emails/scripts/scan-emails.mjs

@@ -3,7 +3,7 @@
  * Scan for unprocessed emails and output their IDs and subjects.
  *
  * Checks ~/.cache/fit/outpost/apple_mail/ for email thread markdown files not
- * yet listed in drafts/handled or drafts/ignored. Outputs one tab-separated
+ * yet listed in Drafts/handled or Drafts/ignored. Outputs one tab-separated
  * line per unprocessed thread: email_id<TAB>subject. Used by the draft-emails
  * skill to identify threads that need a reply.
  */
@@ -17,7 +17,7 @@ const HELP = `scan-emails — list unprocessed email threads
 Usage: node scripts/scan-emails.mjs [-h|--help]
 
 Scans ~/.cache/fit/outpost/apple_mail/ for .md thread files not yet
-recorded in drafts/handled or drafts/ignored. Outputs one line per
+recorded in Drafts/handled or Drafts/ignored. Outputs one line per
 unprocessed thread as: email_id<TAB>subject`;
 
 if (process.argv.includes("-h") || process.argv.includes("--help")) {
@@ -49,8 +49,8 @@ function extractSubject(filePath) {
 function main() {
   if (!existsSync(MAIL_DIR)) return;
 
-  const handled = loadIdSet("drafts/handled");
-  const ignored = loadIdSet("drafts/ignored");
+  const handled = loadIdSet("Drafts/handled");
+  const ignored = loadIdSet("Drafts/ignored");
 
   for (const name of readdirSync(MAIL_DIR).sort()) {
     if (!name.endsWith(".md")) continue;

package/templates/.claude/skills/draft-emails/scripts/send-email.mjs

@@ -30,7 +30,7 @@ Options:
   --bcc <addrs>      Comma-separated BCC recipients
   --subject <subj>   Email subject line (required)
   --body <text>      Plain-text email body (required)
-  --draft <path>     Draft file — deleted after send, ID appended to drafts/handled
+  --draft <path>     Draft file — deleted after send, ID appended to Drafts/handled
   -h, --help         Show this help message and exit
 
 Mail.app must be running. No signature or sign-off needed — Apple Mail appends it.`;
@@ -113,7 +113,7 @@ function handleDraftCleanup(draft) {
   const draftBasename = basename(draft, ".md");
   const emailId = draftBasename.replace(/_draft$/, "");
   if (emailId) {
-    appendFileSync("drafts/handled", emailId + "\n");
+    appendFileSync("Drafts/handled", emailId + "\n");
     console.log(`Marked as handled: ${emailId}`);
   }
 }

package/templates/.claude/skills/extract-entities/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: extract-entities
-description: Process synced email/calendar files from ~/.cache/fit/outpost/ and ad-hoc document files (e.g. from ~/Desktop/ or ~/Downloads/) to extract structured knowledge into knowledge/ as Obsidian-compatible markdown notes. Use on a schedule, when the user asks to process/extract entities, or when invoked by another skill (e.g. organize-files). Builds the core knowledge graph from raw data.
+description: Process synced email/calendar files from ~/.cache/fit/outpost/ and ad-hoc document files (e.g. from ~/Desktop/ or ~/Downloads/) to extract structured knowledge into Knowledge/ as Obsidian-compatible markdown notes. Use on a schedule, when the user asks to process/extract entities, or when invoked by another skill (e.g. organize-files). Builds the core knowledge graph from raw data.
 ---
 
 # Extract Entities
 
 Process synced email and calendar files from `~/.cache/fit/outpost/`, plus
 ad-hoc documents passed by other skills, into Obsidian-compatible markdown notes
-under `knowledge/`. The core knowledge-graph builder.
+under `Knowledge/`. The core knowledge-graph builder.
 
 ## Trigger
 
@@ -35,13 +35,13 @@ under `knowledge/`. The core knowledge-graph builder.
 
 ## Outputs
 
-- `knowledge/People/`, `knowledge/Organizations/`, `knowledge/Projects/`,
-  `knowledge/Topics/` — created or updated.
-- `knowledge/Goals/`, `knowledge/Priorities/` — **updated only**, never
+- `Knowledge/People/`, `Knowledge/Organizations/`, `Knowledge/Projects/`,
+  `Knowledge/Topics/` — created or updated.
+- `Knowledge/Priorities/` — **updated only**, never
   auto-created.
-- `knowledge/Conditions/` — created when cross-cutting patterns are detected, or
+- `Knowledge/Conditions/` — created when cross-cutting patterns are detected, or
   updated.
-- `knowledge/Roles/`, `knowledge/Candidates/*/brief.md` — enriched with inferred
+- `Knowledge/Roles/`, `Knowledge/Candidates/*/brief.md` — enriched with inferred
   metadata.
 - `~/.cache/fit/outpost/state/graph_processed` — updated.
 
@@ -55,10 +55,10 @@ well-grounded notes">
       a substantive `## Summary`, calendar-only attendees routed to Organization
       `## Contacts`.
 - [ ] All links use absolute paths `[[Folder/Name]]`; bidirectional links
-      consistent (incl. Goal ↔ Project, Priority ↔ Goal).
+      consistent (incl. Project ↔ Priority).
 - [ ] Summaries describe relationship, not communication method; key facts are
       substantive; open items are commitments.
-- [ ] State changes logged with `[Field → value]`; no Goal or Priority entities
+- [ ] State changes logged with `[Field → value]`; no Priority entities
       auto-created.
 - [ ] Conditions created only when ≥ 3 entities reference the same cross-cutting
       state; resolution detected when evidence supports.
@@ -89,13 +89,13 @@ instead of scanning `~/.cache/fit/outpost/` — still check each against
 ### 1. Build the knowledge index
 
 ```bash
-find knowledge/People knowledge/Organizations knowledge/Projects \
-     knowledge/Topics knowledge/Goals knowledge/Priorities \
-     knowledge/Conditions -name "*.md" 2>/dev/null
+find Knowledge/People Knowledge/Organizations Knowledge/Projects \
+     Knowledge/Topics Knowledge/Priorities \
+     Knowledge/Conditions -name "*.md" 2>/dev/null
 ```
 
 For each note, `head -20` to capture key fields. Build a mental index of People,
-Organizations, Projects, Goals, Priorities, Topics by name, email, organization,
+Organizations, Projects, Priorities, Topics by name, email, organization,
 role, status, and aliases.
 
 ### 2. Classify the source
@@ -123,7 +123,7 @@ Collect every name variant per
 For each variant, search the knowledge index. Apply the
 [matching table](references/resolution.md#matching) and the
 [disambiguation priority](references/resolution.md#disambiguation-priority).
-Goals and Priorities are
+Priorities are
 [never auto-created](references/resolution.md#never-auto-create) — link to
 existing entries only.
 
@@ -150,9 +150,8 @@ filler or meta-commentary.
 - **Recruitment** (Req-number detection, hiring-manager / recruiter /
   domain-lead inference):
   [references/recruitment.md](references/recruitment.md).
-- **Goal & Priority links** (Step 7c): rules in
-  [references/links.md](references/links.md#goals-step-7c) and
-  [Priorities](references/links.md#priorities-step-7c). **Never auto-create.**
+- **Priority links** (Step 7c): rules in
+  [references/links.md](references/links.md#priorities-step-7c). **Never auto-create.**
 - **Conditions** (cross-cutting states affecting ≥ 3 entities):
   [references/conditions.md](references/conditions.md).
 

package/templates/.claude/skills/extract-entities/references/TEMPLATES.md

@@ -7,8 +7,8 @@ index.
 - [templates-people-orgs.md](templates-people-orgs.md) — People, Organizations.
 - [templates-projects-topics.md](templates-projects-topics.md) — Projects,
   Topics.
-- [templates-goals-priorities.md](templates-goals-priorities.md) — Goals,
-  Priorities. **Never auto-created** by `extract-entities` or `anarlog-process`
+- [templates-priorities.md](templates-priorities.md) — Priorities.
+  **Never auto-created** by `extract-entities` or `anarlog-process`
   — set by the user.
 - [templates-conditions.md](templates-conditions.md) — Conditions (time-bound
   cross-cutting states).

package/templates/.claude/skills/extract-entities/references/conditions.md

@@ -20,7 +20,7 @@ same constraint or state, suspect a Condition.
 
 ## Creating a Condition
 
-1. Check existing: `ls knowledge/Conditions/ 2>/dev/null`.
+1. Check existing: `ls Knowledge/Conditions/ 2>/dev/null`.
 2. **No match:** create a new Condition note using
    [templates-conditions.md](templates-conditions.md). Name descriptively
    ("Hiring Freeze Q2", "Division Reorg").
@@ -31,8 +31,8 @@ same constraint or state, suspect a Condition.
 
 When a Condition is created or updated:
 
-1. Add `[[Conditions/{Condition}]]` to the `## Blockers` section of affected
-   Goals.
+1. Add `[[Conditions/{Condition}]]` to the `## Affects` section of affected
+   Priorities.
 2. Add `[Status → on hold]` state changes to affected Projects where
    appropriate.
 3. Add a `## Blockers` entry to affected Role files if recruitment is frozen.
@@ -45,7 +45,7 @@ Source content indicates the Condition has ended: "approved", "freeze lifted",
 "reorg complete", "back on track".
 
 - Set `**Status:** resolved`, `**Resolved:** {date}`.
-- Remove `[[Conditions/{Condition}]]` from affected Goal `## Blockers`.
+- Remove `[[Conditions/{Condition}]]` from affected Priority `## Affects`.
 - Log with `[Status → resolved]`.
 
 ## Conservatism

package/templates/.claude/skills/extract-entities/references/links.md

@@ -1,6 +1,6 @@
 # Bidirectional Links
 
-Reference for `extract-entities` Step 10 and Step 7c (Goals / Priorities).
+Reference for `extract-entities` Step 10 and Step 7c (Priorities).
 
 ## Bidirectional link rules
 
@@ -11,28 +11,13 @@ After writing, verify each link goes both ways.
 | Person → Organization  | Organization → Person (in People section)    |
 | Person → Project       | Project → Person (in People section)         |
 | Project → Organization | Organization → Project (in Projects section) |
-| Project → Goal         | Goal → Project (in Projects section)         |
-| Goal → Priority        | Priority → Goal (in Goals section)           |
 | Project → Priority     | Priority → Project (in Projects section)     |
-| Condition → Goal       | Goal → Condition (in Blockers section)       |
 | Condition → Project    | Project → Condition (in Related section)     |
 | Condition → Role       | Role → Condition (notes or status field)     |
 
 Use absolute paths everywhere: `[[People/Sarah Chen]]`,
 `[[Organizations/Acme Corp]]`, `[[Projects/Acme Integration]]`,
-`[[Goals/Goal Name]]`, `[[Priorities/Priority Name]]`,
-`[[Conditions/Condition Name]]`.
-
-## Goals (Step 7c)
-
-When source content references an existing `knowledge/Goals/*.md`:
-
-- Add a `[[Goals/{Goal}]]` link to the relevant Project or Topic activity entry.
-- Add a progress entry to the Goal's `## Progress` section.
-- If evidence suggests a status change ("we won't hit the Q3 target"), update
-  `**Status:**` and log `[Status → value]`.
-
-**Never auto-create Goals.**
+`[[Priorities/Priority Name]]`, `[[Conditions/Condition Name]]`.
 
 ## Priorities (Step 7c)
 
@@ -44,5 +29,5 @@ Match source themes against priority names and descriptions.
   serves it.
 
 **Never auto-create Priorities.** Don't over-link — a project that already links
-to a Goal which links to a Priority doesn't need a redundant direct Priority
+to a Priority through a related Topic doesn't need a redundant direct Priority
 link.

package/templates/.claude/skills/extract-entities/references/recruitment.md

@@ -1,16 +1,16 @@
 # Recruitment Inference
 
-Reference for `extract-entities` Step 7b. Enrich `knowledge/Roles/` and
-`knowledge/Candidates/` with metadata that no single source carries.
+Reference for `extract-entities` Step 7b. Enrich `Knowledge/Roles/` and
+`Knowledge/Candidates/` with metadata that no single source carries.
 
 ## Requisition number detection
 
 Scan email subjects and bodies for requisition numbers (e.g. 7-digit Workday
 IDs).
 
-1. `ls knowledge/Roles/ | grep "{req_number}"` — does a Role file exist?
+1. `ls Knowledge/Roles/ | grep "{req_number}"` — does a Role file exist?
 2. **No file:** create a stub using the Role-stub template in `req-track` Step
-   0b. Search `rg "{req_number}" knowledge/` for context to enrich it.
+   0b. Search `rg "{req_number}" Knowledge/` for context to enrich it.
 3. **File exists:** check whether the email provides new metadata (hiring
    manager, recruiter, locations) and update the Role file.
 
@@ -20,11 +20,11 @@ When a calendar event title matches an interview pattern — "Interview",
 "Screening", "Screen", "Decomposition", "Panel", "Technical Assessment",
 "Candidate" — combined with a person name:
 
-1. Cross-reference the candidate against `knowledge/Candidates/`.
+1. Cross-reference the candidate against `Knowledge/Candidates/`.
 2. Extract the **organizer**. If the organizer isn't the user (per
    `~/.cache/fit/outpost/state/identity.md`),
    they are likely the hiring manager.
-3. Confirm: look up the organizer in `knowledge/People/` for a manager/HM role
+3. Confirm: look up the organizer in `Knowledge/People/` for a manager/HM role
    indication.
 4. Check the candidate's `brief.md` for a `Req` field; if known, set the
    matching Role file's `Hiring manager` (only if currently `—`).
@@ -33,9 +33,9 @@ When a calendar event title matches an interview pattern — "Interview",
 ## Recruiter — email-thread inference
 
 When a thread references candidates (name match against
-`knowledge/Candidates/`):
+`Knowledge/Candidates/`):
 
-1. Cross-reference To/CC against `knowledge/People/`.
+1. Cross-reference To/CC against `Knowledge/People/`.
 2. If a CC'd person's note mentions "recruiter", "talent acquisition", or a
    similar role, they are likely the internal recruiter.
 3. Update the candidate's `brief.md` recruiter field and the matching Role file

package/templates/.claude/skills/extract-entities/references/resolution.md

@@ -11,10 +11,8 @@ Extract every way each entity is referenced.
 - **Organizations:** full names, short names, abbreviations, email domains.
 - **Projects:** explicit names, descriptive references ("the pilot", "the
   deal").
-- **Goals:** references to time-bound targets, OKRs, or measurable outcomes that
-  match `knowledge/Goals/` entries.
-- **Priorities:** references to strategic directions that match
-  `knowledge/Priorities/` entries.
+- **Priorities:** references to strategic directions, time-bound targets, or
+  measurable outcomes that match `Knowledge/Priorities/` entries.
 
 ## Matching
 
@@ -82,5 +80,5 @@ Format: `**Role:** Product Lead (inferred from evaluation discussions)`.
 
 ## Never auto-create
 
-`Goals/` and `Priorities/`. Link to existing entries when referenced; update
+`Priorities/`. Link to existing entries when referenced; update
 progress / backlinks; never create new ones from extracted content.

package/templates/.claude/skills/extract-entities/references/sources.md

@@ -40,7 +40,7 @@ write a placeholder profile; see the
 
 ## Process — update existing notes only
 
-- Emails from people already in `knowledge/People/`.
+- Emails from people already in `Knowledge/People/`.
 - Emails referencing existing projects or organizations.
 
 ## Process — can create new notes

package/templates/.claude/skills/extract-entities/references/templates-conditions.md

@@ -16,8 +16,8 @@ are detected, or manually created by the user. Lifecycle: active → resolved.
 **Resolution signal:** {What would indicate this condition has ended}
 
 ## Affects
-{Goals, Projects, Roles, and People impacted by this condition}
-- [[Goals/{Goal}]] — {how it's affected}
+{Priorities, Projects, Roles, and People impacted by this condition}
+- [[Priorities/{Priority}]] — {how it's affected}
 - [[Projects/{Project}]] — {how it's affected}
 - [[Roles/{Role}]] — {how it's affected}
 

package/templates/.claude/skills/extract-entities/references/templates-priorities.md

@@ -0,0 +1,32 @@
+# Priority Templates
+
+Priorities are **never auto-created** by `extract-entities`. They are set
+deliberately by the user. This template is for manual creation only —
+`extract-entities` and `anarlog-process` only **link to** and **update progress
+on** existing notes.
+
+## Priorities
+
+```markdown
+# {Priority Name}
+
+## About
+{2-3 sentences: what this strategic direction means and why it matters}
+
+**Status:** {active|paused|retired}
+**Owner:** [[People/{Person}]]
+**Set:** {YYYY-MM-DD}
+
+## What this means
+{Bullet list of concrete implications — what does pursuing this priority look like?}
+
+## Actions
+{Concrete, time-bound actions that ladder to this priority. Targets live inline
+here — there is no separate Goals entity.}
+
+## Projects
+- [[Projects/{Project}]] — {relationship}
+
+## Key facts
+{substantive facts only — leave empty if none}
+```

package/templates/.claude/skills/extract-entities/references/templates-projects-topics.md

@@ -14,8 +14,8 @@
 ## Summary
 {2-3 sentences}
 
-## Goals
-- [[Goals/{Goal}]] — {how this project contributes}
+## Priorities
+- [[Priorities/{Priority}]] — {how this project contributes}
 
 ## People
 - [[People/{Person}]] — {role}

package/templates/.claude/skills/meeting-prep/SKILL.md

@@ -22,13 +22,12 @@ meetings.
 ## Inputs
 
 - `~/.cache/fit/outpost/apple_calendar/*.json` — calendar events
-- `knowledge/People/*.md` — attendee context
-- `knowledge/Organizations/*.md` — company context
-- `knowledge/Projects/*.md` — project context
-- `knowledge/Goals/*.md` — active goals relevant to the meeting topic
-- `knowledge/Priorities/*.md` — strategic context for framing
-- `knowledge/Candidates/*/brief.md` — candidate context (for interview meetings)
-- `knowledge/Roles/*.md` — role/requisition context (for interview meetings)
+- `Knowledge/People/*.md` — attendee context
+- `Knowledge/Organizations/*.md` — company context
+- `Knowledge/Projects/*.md` — project context
+- `Knowledge/Priorities/*.md` — active priorities and strategic context for framing
+- `Knowledge/Candidates/*/brief.md` — candidate context (for interview meetings)
+- `Knowledge/Roles/*.md` — role/requisition context (for interview meetings)
 
 ## Outputs
 
@@ -44,8 +43,8 @@ knowledge base.**
 When the user asks to prep for a meeting:
 
 1. **STOP** — Do not create a generic brief
-2. **SEARCH** — Look up each attendee: `rg -l "Attendee Name" knowledge/`
-3. **READ** — Read their notes: `cat "knowledge/People/Attendee Name.md"`
+2. **SEARCH** — Look up each attendee: `rg -l "Attendee Name" Knowledge/`
+3. **READ** — Read their notes: `cat "Knowledge/People/Attendee Name.md"`
 4. **UNDERSTAND** — Extract role, organization, history, open items
 5. **THEN BRIEF** — Create the meeting brief using this context
 
@@ -92,18 +91,18 @@ Extract: summary, start/end time, attendees (names and emails), description.
 For each attendee:
 
 ```bash
-rg -l "attendee_name" knowledge/People/
-rg -l "attendee_email" knowledge/People/
-cat "knowledge/People/Attendee Name.md"
-cat "knowledge/Organizations/Their Company.md"
-rg -l "attendee_name" knowledge/Projects/
+rg -l "attendee_name" Knowledge/People/
+rg -l "attendee_email" Knowledge/People/
+cat "Knowledge/People/Attendee Name.md"
+cat "Knowledge/Organizations/Their Company.md"
+rg -l "attendee_name" Knowledge/Projects/
 ```
 
 Extract: role/title, company, key facts, previous interactions, open items.
 
-Also check `knowledge/Goals/` and `knowledge/Priorities/` for context relevant
+Also check `Knowledge/Priorities/` for context relevant
 to the meeting topic — e.g. if the meeting is about hiring, surface the relevant
-hiring Goal's status and progress.
+hiring Priority's status and progress.
 
 ### Step 4: Create Meeting Brief
 
@@ -141,11 +140,11 @@ Suggested Talking Points
 ### Interview Meeting Context
 
 When preparing for interview meetings (title contains "Interview", "Screening",
-"Decomposition", "Panel", or a candidate name from `knowledge/Candidates/`):
+"Decomposition", "Panel", or a candidate name from `Knowledge/Candidates/`):
 
-1. **Read the candidate brief:** `knowledge/Candidates/{Name}/brief.md`
+1. **Read the candidate brief:** `Knowledge/Candidates/{Name}/brief.md`
 2. **Read the Role file:** Look up the `Req` field and read the corresponding
-   `knowledge/Roles/*.md` file.
+   `Knowledge/Roles/*.md` file.
 3. **Include in the briefing:**
    - Candidate's current status, skills, and screening recommendation
    - Role context: hiring manager, domain lead, remaining positions