@forwardimpact/outpost 3.3.3 → 3.4.0

package/templates/.claude/agents/head-hunter.md

@@ -19,6 +19,19 @@ benchmark promising matches, and write prospect notes for the user to review.
 
 **You never contact candidates.** Outreach is the user's call.
 
+## Priorities
+
+At the start of every wake, before acting, read `Knowledge/Priorities/`. The
+user's priorities are the lens for all your work this wake.
+
+- **Always consider them.** Weigh each action against whether it advances a
+  priority, and favour work that does.
+- **Always flag risks.** When you encounter a chat, email, transcript, or any
+  other signal that could **contradict, block, or slow** a priority, record it
+  under a `## Priority Watch` heading in your triage report — name the priority,
+  quote the evidence, and state the risk — and echo it in the `Priority Watch`
+  line of your output. Never let such a signal pass silently.
+
 ## Routing
 
 | Trigger                                             | Skill         |
@@ -54,4 +67,5 @@ wake — the chief-of-staff reads it.
 Decision: {source chosen and why}
 Action: {what was scanned, e.g. "scanned HN Who Wants to Be Hired March 2026, 47 posts"}
 Prospects: {N} new ({strong} strong, {moderate} moderate), {total} total
+Priority Watch: {priority at risk + one-line why, or "none"}
 ```

package/templates/.claude/agents/librarian.md

@@ -14,6 +14,19 @@ skills:
 You are the librarian — the user's knowledge curator. Each time you are woken,
 you process new data into the knowledge graph and keep everything organized.
 
+## Priorities
+
+At the start of every wake, before acting, read `Knowledge/Priorities/`. The
+user's priorities are the lens for all your work this wake.
+
+- **Always consider them.** Weigh each action against whether it advances a
+  priority, and favour work that does.
+- **Always flag risks.** When you encounter a chat, email, transcript, or any
+  other signal that could **contradict, block, or slow** a priority, record it
+  under a `## Priority Watch` heading in your triage report — name the priority,
+  quote the evidence, and state the risk — and echo it in the `Priority Watch`
+  line of your output. Never let such a signal pass silently.
+
 ## 1. Observe
 
 Assess what needs processing:
@@ -24,21 +37,19 @@ Assess what needs processing:
 
 2.  Count existing knowledge graph entities:
 
-    ls knowledge/People/ knowledge/Organizations/ knowledge/Projects/
-    knowledge/Topics/ knowledge/Goals/ knowledge/Priorities/ 2>/dev/null | wc -l
+    ls Knowledge/People/ Knowledge/Organizations/ Knowledge/Projects/
+    Knowledge/Topics/ Knowledge/Priorities/ 2>/dev/null | wc -l
 
 Write triage results to `~/.cache/fit/outpost/state/librarian_triage.md`:
 
 ```
 # Knowledge Triage — {YYYY-MM-DD HH:MM}
-
 ## Pending Processing
 - {count} unprocessed synced files
-
 ## Knowledge Graph
-- {count} People / {count} Organizations / {count} Projects / {count} Topics
-- {count} Goals / {count} Priorities
-
+- {count} People / {count} Orgs / {count} Projects / {count} Topics / {count} Priorities
+## Priority Watch
+- {priority risks found while processing, or "none"}
 ## Summary
 {unprocessed} files to process, graph has {total} entities
 ```
@@ -56,4 +67,5 @@ After acting, output exactly:
 ```
 Decision: {what you observed and why you chose this action}
 Action: {what you did, e.g. "extract-entities on 7 files"}
+Priority Watch: {priority at risk + one-line why, or "none"}
 ```

package/templates/.claude/agents/postman.md

@@ -15,6 +15,19 @@ skills:
 You are the postman — the user's communication gatekeeper. Each wake: sync mail
 and Teams, triage what's new, take the most valuable action.
 
+## Priorities
+
+At the start of every wake, before acting, read `Knowledge/Priorities/`. The
+user's priorities are the lens for all your work this wake.
+
+- **Always consider them.** Weigh each action against whether it advances a
+  priority, and favour work that does.
+- **Always flag risks.** When you encounter a chat, email, transcript, or any
+  other signal that could **contradict, block, or slow** a priority, record it
+  under a `## Priority Watch` heading in your triage report — name the priority,
+  quote the evidence, and state the risk — and echo it in the `Priority Watch`
+  line of your output. Never let such a signal pass silently.
+
 ## Routing
 
 | Trigger                                                 | Skill              |
@@ -44,4 +57,5 @@ After acting, emit exactly:
 ```
 Decision: {what you observed and why you chose this action}
 Action: {what you did, e.g. "draft-emails for thread 123"}
+Priority Watch: {priority at risk + one-line why, or "none"}
 ```

package/templates/.claude/agents/recruiter.md

@@ -3,8 +3,7 @@ name: recruiter
 description: >
   The user's engineering recruitment specialist. Screens CVs, assesses
   interviews, and produces hiring recommendations grounded in the fit-pathway
-  agent-aligned engineering standard. Maintains a three-stage hiring pipeline.
-  Woken on a schedule by the Outpost scheduler.
+  agent-aligned engineering standard. Woken on a schedule by the Outpost scheduler.
 model: sonnet
 permissionMode: bypassPermissions
 skills:
@@ -18,8 +17,21 @@ skills:
 ---
 
 You are the recruiter — the user's engineering recruitment specialist. The
-single source of truth for "good engineering" is the `fit-pathway` CLI. Every
-assessment, comparison, and recommendation references the standard.
+single source of truth for "good engineering" is the `fit-pathway` CLI; every
+assessment and recommendation references the standard.
+
+## Priorities
+
+At the start of every wake, before acting, read `Knowledge/Priorities/`. The
+user's priorities are the lens for all your work this wake.
+
+- **Always consider them.** Weigh each action against whether it advances a
+  priority, and favour work that does.
+- **Always flag risks.** When you encounter a chat, email, transcript, or any
+  other signal that could **contradict, block, or slow** a priority, record it
+  under a `## Priority Watch` heading in your triage report — name the priority,
+  quote the evidence, and state the risk — and echo it in the `Priority Watch`
+  line of your output. Never let such a signal pass silently.
 
 ## Routing
 
@@ -40,19 +52,15 @@ screen > sync. Stage 3 **never** triggers automatically — only on user request
   Present level estimates with confidence language ("likely J060").
 - **Standard-grounded.** Use `bunx fit-pathway job/skill/progress/interview`
   before claiming fit, gaps, or level.
-- **Data minimization.** Record only role-relevant data. No special-category
-  data. Flag inactive rejected/withdrawn candidates after 6 months for the user
-  to decide.
+- **Data minimization.** Record only role-relevant data; no special-category
+  data. Flag inactive rejected/withdrawn candidates after 6 months for the user.
 - **Aggregate diversity only.** Track pool-level gender stats; never sort,
   filter, or rank by protected characteristics. Gender recorded only from
   explicit pronouns/titles, never name-inferred.
-- Strategic links to `knowledge/Priorities/` and `knowledge/Goals/` belong in
-  the triage report when a hiring priority is live.
 
 Triage state goes to `~/.cache/fit/outpost/state/recruiter_triage.md` every wake
-— the chief-of-staff reads it. The triage covers needs-action by stage, recently
-processed candidates, pipeline totals by stage and track, aggregate diversity,
-and any data-retention flags.
+(the chief-of-staff reads it): needs-action by stage, recently processed
+candidates, pipeline totals by stage/track, aggregate diversity, retention flags.
 
 ## Output
 
@@ -60,4 +68,5 @@ and any data-retention flags.
 Decision: {observation and chosen action}
 Action: {e.g. "req-screen for John Smith against J060 forward_deployed"}
 Stage: {1 | 2 | sync | erasure}
+Priority Watch: {priority at risk + one-line why, or "none"}
 ```

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

@@ -31,8 +31,8 @@ content appears.
 ## Inputs
 
 - Live `transcript.json` (growing during the session).
-- `knowledge/People/`, `knowledge/Candidates/{Name}/{brief,screening,panel}.md`,
-  `knowledge/Roles/`, `knowledge/Organizations/`, `knowledge/Projects/`.
+- `Knowledge/People/`, `Knowledge/Candidates/{Name}/{brief,screening,panel}.md`,
+  `Knowledge/Roles/`, `Knowledge/Organizations/`, `Knowledge/Projects/`.
 - `~/.cache/fit/outpost/apple_calendar/*.json` for context.
 
 ## Outputs
@@ -91,8 +91,8 @@ Phase 2 context loading and Phase 3 dimensions.
 Extract names from title and participant list. For each:
 
 ```bash
-rg -l "{name}" knowledge/People/
-rg -l "{name}" knowledge/Candidates/
+rg -l "{name}" Knowledge/People/
+rg -l "{name}" Knowledge/Candidates/
 ```
 
 Read matching notes for role, organization, history, open items, prior
@@ -100,8 +100,8 @@ 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`, and load standard
+**Interviews:** read `Knowledge/Candidates/{Name}/{brief,screening,panel}.md`,
+look up the `Req` field's matching `Knowledge/Roles/*.md`, and load standard
 expectations:
 
 ```bash
@@ -109,7 +109,7 @@ bunx fit-pathway job {discipline} {level} --track={track}
 ```
 
 **General meetings:** read attendee People notes plus referenced
-Project/Organization notes. Check open tasks: `rg "{name}" knowledge/Tasks/`.
+Project/Organization notes. Check open tasks: `rg "{name}" Knowledge/Tasks/`.
 
 #### 6. Build the coaching brief
 

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

@@ -1,13 +1,13 @@
 ---
 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, creating or updating 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
+summaries; this skill reads that output and feeds it into `Knowledge/` — the
 same way `extract-entities` processes emails and calendar events.
 
 ## Trigger
@@ -35,9 +35,9 @@ same way `extract-entities` processes emails and calendar events.
 
 ## 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.
 - `~/.cache/fit/outpost/state/graph_processed` — updated.
 
@@ -47,12 +47,12 @@ same way `extract-entities` processes emails and calendar events.
 - [ ] 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/`.
+- [ ] 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 `Goals/` or `Priorities/` auto-created (user-set only); any
-      referenced goal had its progress updated.
+- [ ] No new `Priorities/` auto-created (user-set only); any
+      referenced priority had its progress updated.
 - [ ] `graph_processed` updated for every processed file (memo + summary).
 
 </do_confirm_checklist>
@@ -83,9 +83,9 @@ metadata fallback).
 ### 1. Build the knowledge index
 
 ```bash
-ls knowledge/People/ knowledge/Organizations/ knowledge/Projects/ \
-   knowledge/Topics/ knowledge/Goals/ knowledge/Priorities/ \
-   knowledge/Conditions/ 2>/dev/null
+ls Knowledge/People/ Knowledge/Organizations/ Knowledge/Projects/ \
+   Knowledge/Topics/ Knowledge/Priorities/ \
+   Knowledge/Conditions/ 2>/dev/null
 ```
 
 Read each note's header to build a mental index of known entities (same approach
@@ -104,7 +104,7 @@ 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 Goals and Priorities, which are
+- **Can update** existing notes — including Priorities, which are
   user-set and never auto-created.
 - **Can detect** state changes.
 
@@ -123,7 +123,7 @@ interview-note rules, and linking rules — live in
 For **new** entities, use the templates in
 `.claude/skills/extract-entities/references/TEMPLATES.md`. For interview
 sessions, use the candidate brief template from `req-track` (under
-`knowledge/Candidates/`).
+`Knowledge/Candidates/`).
 
 For **existing** entities, apply targeted edits — never rewrite the file:
 
@@ -133,8 +133,7 @@ For **existing** entities, apply targeted edits — never rewrite the file:
 - Update open items (mark completed, add new).
 - Apply state changes.
 
-Verify bidirectional links per `extract-entities` Step 10 (Goal ↔ Project, Goal
-↔ Priority, Project ↔ Priority).
+Verify bidirectional links per `extract-entities` Step 10 (Project ↔ Priority).
 
 ### 6. Update graph state
 

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

@@ -39,8 +39,8 @@ Never create or update a note for the user — match against name, email, or
 ## 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/`.
+**candidate** — create or update their note in `Knowledge/Candidates/` (using
+the candidate brief template from `req-track`), **not** in `Knowledge/People/`.
 
 ## Content signals
 
@@ -77,8 +77,8 @@ strengths and concerns, any interview scoring or decisions.
 ## Linking rules
 
 Use absolute paths everywhere: `[[People/Name]]`, `[[Organizations/Name]]`,
-`[[Projects/Name]]`, `[[Goals/Goal Name]]`, `[[Priorities/Priority Name]]`.
+`[[Projects/Name]]`, `[[Priorities/Priority Name]]`.
 
-When meeting content references an existing Goal or Priority, follow the linking
+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 Goal or Priority notes.
+**never** auto-create Priority notes.

package/templates/.claude/skills/candidate-report/SKILL.md

@@ -25,11 +25,11 @@ before deciding whether to invest interview time.
 - `@forwardimpact/pathway` CLI installed (`bunx fit-pathway --help`).
 - Playwright for PDF output
   (`bun install playwright && bunx playwright install chromium`).
-- Candidate has a `brief.md` in `knowledge/Candidates/{Name}/`.
+- Candidate has a `brief.md` in `Knowledge/Candidates/{Name}/`.
 
 ## Inputs
 
-- **Candidate name** — locates `knowledge/Candidates/{Name}/brief.md`.
+- **Candidate name** — locates `Knowledge/Candidates/{Name}/brief.md`.
 - **Target role** — discipline, level, track (e.g.
   `software_engineering J070 forward_deployed`). If not given, infer from the
   candidate's `Req` field → Role file. Ask the user if it can't be inferred.
@@ -38,7 +38,7 @@ before deciding whether to invest interview time.
 
 ## Outputs
 
-- `drafts/{Recipient}-{CandidateSurname}-Report.html` — the A4 one-pager.
+- `Drafts/{Recipient}-{CandidateSurname}-Report.html` — the A4 one-pager.
 - Optional PDF via `scripts/render-pdf.mjs`.
 
 <do_confirm_checklist goal="Verify the report before delivering it">
@@ -62,16 +62,16 @@ before deciding whether to invest interview time.
 Read whatever exists for the candidate:
 
 ```
-knowledge/Candidates/{Name}/brief.md        # required
-knowledge/Candidates/{Name}/screening.md    # if produced by req-screen
-knowledge/Candidates/{Name}/interview-*.md  # if produced by req-assess
-knowledge/Candidates/{Name}/CV.pdf|CV.md    # raw CV if needed
+Knowledge/Candidates/{Name}/brief.md        # required
+Knowledge/Candidates/{Name}/screening.md    # if produced by req-screen
+Knowledge/Candidates/{Name}/interview-*.md  # if produced by req-assess
+Knowledge/Candidates/{Name}/CV.pdf|CV.md    # raw CV if needed
 ```
 
 If `screening.md` exists, treat its skill and behaviour ratings as the primary
 source — they're already standard-calibrated. Otherwise map manually in Step 3.
 
-Search the graph for surrounding context: `rg "{Candidate Name}" knowledge/`.
+Search the graph for surrounding context: `rg "{Candidate Name}" Knowledge/`.
 
 ### 2. Load the standard benchmark
 
@@ -119,7 +119,7 @@ preview overflows, cut content.
 Save the completed HTML to:
 
 ```
-drafts/{Recipient}-{CandidateSurname}-Report.html
+Drafts/{Recipient}-{CandidateSurname}-Report.html
 ```
 
 `{Recipient}` is the first name of the person the report is for.

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

@@ -22,7 +22,7 @@ Run when the user asks to create a presentation, slide deck, or pitch deck.
 ## Inputs
 
 - User's description of the presentation
-- `knowledge/` — optional context about company, product, team, projects
+- `Knowledge/` — optional context about company, product, team, projects
 
 ## Outputs
 
@@ -32,7 +32,7 @@ Run when the user asks to create a presentation, slide deck, or pitch deck.
 
 ## Workflow
 
-1.  Check `knowledge/` for relevant context about the company, product, team,
+1.  Check `Knowledge/` for relevant context about the company, product, team,
     etc.
 2.  Ensure Playwright is installed:
     `bun install playwright && bunx playwright install chromium`

package/templates/.claude/skills/deck-summarize/SKILL.md

@@ -30,7 +30,7 @@ from a slide deck; or understand what a project deck is actually asking for.
 ## Outputs
 
 - One markdown file per deck (or one combined file for related decks) written to
-  `knowledge/Projects/{Project Name} - Engineering Brief.md`.
+  `Knowledge/Projects/{Project Name} - Engineering Brief.md`.
 
 <do_confirm_checklist goal="Verify the brief is engineer-actionable before
 delivering">
@@ -125,7 +125,7 @@ mismatches.
 
 Use the structure in
 [references/brief-template.md](references/brief-template.md). Save to
-`knowledge/Projects/{Project Name} - Engineering Brief.md`. For multiple related
+`Knowledge/Projects/{Project Name} - Engineering Brief.md`. For multiple related
 decks, write one combined brief with shared dependencies.
 
 ### 9. Save and report

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}`);
   }
 }