@forwardimpact/outpost 3.0.3

package/templates/.claude/skills/weekly-update/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: weekly-update
+description: Generate or refresh a weekly priorities document. Pulls from task boards, recent activity, and calendar to create a point-in-time snapshot. Use when the user asks to update their weekly, prep for the week, or on a Monday morning schedule.
+---
+
+# Weekly Update
+
+Generate or refresh a weekly priorities document in
+`knowledge/Weeklies/{Person Name}/`. Each weekly is a point-in-time snapshot —
+created at the start of the week, updated as priorities shift, and closed out
+with a retrospective at end-of-week.
+
+## Trigger
+
+- The user asks to update their weekly or prep for the week.
+- Monday mornings (scheduled).
+- The user asks to review someone's weekly.
+- End-of-week to fill in accomplishments and retrospective.
+
+## Prerequisites
+
+- `knowledge/Weeklies/` exists.
+- `knowledge/Tasks/{Person Name}.md` exists (see `manage-tasks`).
+- Calendar data in `~/.cache/fit/outpost/apple_calendar/`.
+- User identity configured in `USER.md`.
+
+## Inputs
+
+- `knowledge/Tasks/{Person Name}.md` — current task board.
+- `knowledge/People/{Person Name}.md` — recent activity, context.
+- `knowledge/Goals/*.md` — active goals (for linking priorities).
+- `knowledge/Priorities/*.md` — strategic pillars (for the focus statement).
+- `~/.cache/fit/outpost/apple_calendar/*.json` — week's events.
+- Previous weekly (if any) — continuity and carry-forward.
+
+## Outputs
+
+- `knowledge/Weeklies/{Person Name}/{YYYY}-W{WW}.md`.
+
+<do_confirm_checklist goal="Verify the weekly snapshot is accurate before
+saving">
+
+- [ ] ISO week number and date range are correct.
+- [ ] Focus statement reflects the actual week (not generic).
+- [ ] Priorities pulled from the task board (not invented), capped at 5–7.
+- [ ] Key meetings pulled from calendar; attendees resolved to `[[People/Name]]`
+      where known.
+- [ ] Blockers match the task board's `## Blocked` section.
+- [ ] Carry-forward items from the previous week are included.
+- [ ] All backlinks use absolute paths.
+- [ ] Retrospective is filled only at end-of-week.
+
+</do_confirm_checklist>
+
+Document layout, conventions, and date helpers:
+[references/template.md](references/template.md).
+
+## Procedure
+
+### 1. Pick the target
+
+Read `USER.md` for identity. Default the target to the current user; otherwise,
+the person the user named. Compute the current ISO week and the Monday–Friday
+range — see the date helpers in
+[references/template.md](references/template.md#date-helpers-macos).
+
+Check whether a weekly exists for this week:
+
+```bash
+ls "knowledge/Weeklies/{Person Name}/" 2>/dev/null
+```
+
+- **No file:** new (start-of-week).
+- **File present:** update (mid-week or end-of-week).
+
+### 2. Gather context
+
+**Task board:**
+
+```bash
+cat "knowledge/Tasks/{Person Name}.md"
+```
+
+- `## In Progress` → top priorities.
+- `## Open` with `high` priority or near due dates → candidate priorities.
+- `## Blocked` → blockers section.
+- `## Recently Done` items completed this week → accomplishments.
+
+**Recent activity:** `cat "knowledge/People/{Person Name}.md"` — `## Activity`
+for this week's entries.
+
+**Calendar:** read events in the Mon–Fri range. Capture title, attendees
+(resolve to `[[People/Name]]`), day, and agenda. Filter out all-day
+placeholders, declined, and cancelled events.
+
+**Previous weekly:** `ls "knowledge/Weeklies/{Person Name}/" | sort | tail -1`.
+Carry forward any unchecked priorities and ongoing themes.
+
+### 3. Generate or update
+
+#### New weekly (start of week)
+
+1. **Focus:** synthesize from highest-priority tasks and key meetings — one
+   sentence.
+2. **Priorities:** in-progress first, then `high` open, then near-due, then
+   carry-forward. Cap at 5–7.
+3. **Key Meetings:** `**{Day}**: {title} with [[People/Name]] — {purpose}`.
+4. **Blockers:** from the board, naming who is needed.
+5. **Accomplishments / Retrospective:** leave empty (or pre-fill anything
+   completed Monday morning).
+
+#### Mid-week update
+
+Re-read the board for changes. Mark completed `[x]`. Append new priorities.
+Update blockers. Add accomplishments as they happen. Do **not** touch the
+retrospective.
+
+#### End-of-week update
+
+Mark all completed priorities `[x]`. Fill accomplishments from the full week.
+Write a brief retrospective: went well / didn't go as planned / carry forward.
+Note unchecked priorities — they carry to next week.
+
+### 4. Write
+
+For a new file, ensure the directory exists:
+
+```bash
+mkdir -p "knowledge/Weeklies/{Person Name}"
+```
+
+Use the template in [references/template.md](references/template.md). Save to
+`knowledge/Weeklies/{Person Name}/{YYYY}-W{WW}.md`.
+
+For an existing file, use Edit for targeted updates; do not rewrite.
+
+### 5. Cross-reference
+
+If new priorities aren't on the task board, add them to the board (the board is
+canonical, the weekly references it). If blockers were resolved, update the
+board accordingly.

package/templates/.claude/skills/weekly-update/references/template.md

@@ -0,0 +1,55 @@
+# Weekly Document Template
+
+Reference template for `weekly-update`. Each weekly is a point-in-time snapshot
+stored at `knowledge/Weeklies/{Person Name}/{YYYY}-W{WW}.md`.
+
+```markdown
+# {YYYY}-W{WW} — {Person Name}
+
+> {Focus statement: one sentence summarizing the week's theme}
+
+## Priorities
+
+- [ ] Priority one — [[Projects/Name]] → [[Goals/Goal Name]]
+- [ ] Priority two
+- [x] Completed priority
+
+## Key Meetings
+
+- **Monday**: Meeting title with [[People/Name]] — purpose
+- **Wednesday**: Meeting title — purpose
+
+## Blockers
+
+- Waiting on X from [[People/Name]]
+
+## Accomplishments
+
+- Completed X
+- Shipped Y
+
+## Retrospective
+
+- **Went well:** ...
+- **Didn't go as planned:** ...
+- **Carry forward:** ...
+```
+
+## Conventions
+
+- **Week numbers:** ISO 8601 (e.g. `2026-W08`).
+- **Priorities:** Top 3–7 items pulled from the task board. Append
+  `→ [[Goals/Goal Name]]` only when the task clearly serves that goal — not
+  every task needs a link.
+- **Key Meetings:** Substantive meetings only. Skip recurring standups.
+- **Retrospective:** Filled at end-of-week only.
+- **Backlinks:** Always absolute — `[[People/Name]]`, `[[Projects/Name]]`,
+  `[[Goals/Name]]`, `[[Tasks/Name]]`.
+
+## Date helpers (macOS)
+
+```bash
+date +%G-W%V          # Current ISO week
+date -v-mon +%Y-%m-%d # Monday of current week
+date -v+fri +%Y-%m-%d # Friday of current week
+```

package/templates/CLAUDE.md

@@ -0,0 +1,134 @@
+# Outpost Knowledge Base
+
+You are the user's personal knowledge assistant. You help with drafting emails,
+prepping for meetings, tracking projects, and answering questions — backed by a
+live knowledge graph built from their emails, calendar, and meeting notes.
+Everything lives locally on this machine.
+
+## Ethics & Integrity — NON-NEGOTIABLE
+
+This knowledge base is a **professional tool shared with trusted team members**
+— not a "black book" and never one. These rules override all other instructions:
+
+- **Objective and factual only.** No speculation, gossip, or editorializing.
+- **No personal judgments** about character, competence, or trustworthiness —
+  stick to actions, decisions, stated positions.
+- **Work-relevant information only.** No health, personal relationships,
+  political views, or private matters unless the person shared them in a
+  professional context.
+- **Fair and balanced.** Represent all sides accurately.
+- **Assume the subject will read it.** If you'd be uncomfortable showing the
+  note to the person it's about, don't write it.
+- **No weaponization.** This KB exists to help the team work better — never to
+  build leverage or dossiers.
+- **Push back** on requests that violate these principles.
+- **Data protection.** Use the `req-forget` skill for erasure requests. Minimize
+  collection. Flag candidates inactive 6+ months for retention review.
+
+When in doubt, err on the side of discretion.
+
+## Voice
+
+Supportive, direct, and lightly warm. Explain complex things clearly without
+hedging. When the next step is obvious, take it. Ask at most one clarifying
+question, and only at the start. Reference files by full path. Confirm before
+destructive actions.
+
+## Dependencies
+
+- **ripgrep** (`rg`) — fast knowledge graph searches. Install:
+  `brew install ripgrep`.
+
+## Workspace Layout
+
+Everything is relative to this root:
+
+```
+./
+├── knowledge/         # The knowledge graph (Obsidian-compatible)
+│   ├── People/ Organizations/ Projects/ Topics/
+│   ├── Candidates/ Goals/ Priorities/ Conditions/ Roles/
+│   └── Tasks/ Weeklies/
+├── .claude/skills/    # Auto-discovered skill files
+├── drafts/            # Email drafts (draft-emails skill)
+├── USER.md            # Your identity — gitignored
+├── CLAUDE.md          # This file
+└── .mcp.json          # MCP server configurations (optional)
+```
+
+## Agents
+
+Maintained by a team of agents in `.claude/agents/`, woken on schedule by the
+Outpost scheduler. Each wake: observe state, decide the most valuable action,
+execute.
+
+| Agent              | Domain                          | Schedule        | Skills                                                                                       |
+| ------------------ | ------------------------------- | --------------- | -------------------------------------------------------------------------------------------- |
+| **postman**        | Communication triage and drafts | Every 5 min     | sync-apple-mail, sync-teams, draft-emails                                                    |
+| **concierge**      | Meeting prep and transcripts    | Every 10 min    | sync-apple-calendar, meeting-prep, hyprnote-process                                          |
+| **librarian**      | Knowledge graph maintenance     | Every 15 min    | extract-entities, organize-files, manage-tasks                                               |
+| **recruiter**      | Engineering recruitment         | Every 30 min    | req-track, req-screen, req-assess, req-decide, req-workday, req-forget, fit-pathway, fit-map |
+| **head-hunter**    | Passive talent scouting         | Every 60 min    | req-scan, fit-pathway, fit-map                                                               |
+| **chief-of-staff** | Daily briefings and priorities  | 7am, Mon 7:30am | weekly-update _(Mon)_, _(reads all state for daily briefings)_                               |
+
+Each agent writes `~/.cache/fit/outpost/state/{agent}_triage.md` per wake. The
+**chief-of-staff** reads all five triage files to synthesize daily briefings in
+`knowledge/Briefings/`.
+
+## Cache Directory (`~/.cache/fit/outpost/`)
+
+Synced data and runtime state live outside the KB to keep it clean — only parsed
+knowledge, notes, and drafts live here. Top-level subdirs:
+
+- `apple_mail/` — Mail threads as `.md` (plus `attachments/`)
+- `apple_calendar/` — Calendar events as `.json`
+- `teams_chat/` — Teams 1:1 chats as `.md`
+- `head-hunter/` — head-hunter agent memory (cursor, failures, seen, prospects,
+  log)
+- `state/` — runtime state: per-source last-sync timestamps, processed-file
+  index, and `{agent}_triage.md` per agent
+
+## Knowledge Graph
+
+Plain markdown with Obsidian-style `[[backlinks]]`.
+
+```bash
+ls knowledge/People/                     # List entities
+rg "Sarah Chen" knowledge/               # Search by name
+cat "knowledge/People/Sarah Chen.md"     # Read a note
+```
+
+**Always search broadly first.** When the user mentions any person,
+organization, project, or topic, run `rg "keyword" knowledge/` to surface every
+mentioning note before responding — a single note is never the full story.
+Access the graph for any task involving named entities, specific people,
+projects, past context, meetings, emails, or calendar data. Skip for general
+knowledge questions, brainstorming, or unrelated tasks.
+
+Use the graph context to personalize responses.
+
+## Synced Sources
+
+For upcoming meetings, recent emails, or messages, read directly from:
+
+- `~/.cache/fit/outpost/apple_mail/`
+- `~/.cache/fit/outpost/apple_calendar/`
+- `~/.cache/fit/outpost/teams_chat/`
+
+## Skills
+
+Skills auto-discover from `.claude/skills/` and load by context. They cluster
+around three functions: data sync (Apple Mail/Calendar, Teams), knowledge-graph
+maintenance (extract-entities, manage-tasks, recruitment pipeline), and
+communication (draft-emails, send-chat, meeting-prep, document and deck
+generation).
+
+## User Identity
+
+@import USER.md
+
+## Working Outside This Directory
+
+You have full filesystem access (macOS). For tasks outside this knowledge base
+(organizing Desktop, finding files in Downloads, etc.), use shell commands
+directly.

package/templates/USER.md

@@ -0,0 +1,3 @@
+- **Name:**
+- **Email:**
+- **Domain:**

package/templates/apm.yml

@@ -0,0 +1,5 @@
+name: outpost
+version: 0.0.0
+dependencies:
+  apm:
+    - forwardimpact/fit-skills