@forwardimpact/outpost 3.3.0 → 3.3.2

package/templates/.claude/skills/manage-tasks/SKILL.md

@@ -1,152 +0,0 @@
----
-name: manage-tasks
-description: Create, update, list, and close tasks on per-person task boards in knowledge/Tasks/. Manages task lifecycle, extracts action items from other skills, and keeps boards current. Use when the user asks to add, update, or review tasks, or when chained from extract-entities or hyprnote-process.
----
-
-# Manage Tasks
-
-Manage per-person task boards in `knowledge/Tasks/`. Each person has a single
-living document tracking open, in-progress, blocked, and recently completed
-tasks. Task boards are the **canonical source** for task tracking — other notes
-link to them rather than duplicating.
-
-## Trigger
-
-- The user asks to add, update, close, or list tasks.
-- Chained from `extract-entities` or `hyprnote-process` with extracted action
-  items.
-- The user asks to see someone's task board or workload.
-- Scheduled housekeeping (prune done items, flag overdue).
-
-## Prerequisites
-
-- `knowledge/Tasks/` directory exists.
-- User identity configured in `USER.md`.
-
-## Inputs
-
-User-initiated: person name and task details from the request.
-
-Chained from other skills, action items in this shape:
-
-```
-TASKS:
-- Owner: {Full Name}
-  Task: {Description — starts with a verb}
-  Priority: high|medium|low
-  Due: YYYY-MM-DD (if known)
-  Source: meeting|email
-  Source date: YYYY-MM-DD
-  Project: {Project Name} (if applicable)
-  Context: {brief context}
-```
-
-## Outputs
-
-- `knowledge/Tasks/{Person Name}.md` — created or updated.
-
-<do_confirm_checklist goal="Verify task board changes are clean and consistent">
-
-- [ ] Task title is actionable and starts with a verb.
-- [ ] Priority is set; medium-default omitted.
-- [ ] Due date present only when there's a real deadline.
-- [ ] Project link `[[Projects/Name]]` set when applicable.
-- [ ] No duplicate tasks on the board.
-- [ ] All backlinks use absolute paths `[[Folder/Name]]`.
-- [ ] Context line is concise (1–2 lines max).
-- [ ] New boards include all four sections.
-- [ ] Housekeeping pruned `## Recently Done` to the last 14 days.
-
-</do_confirm_checklist>
-
-Board layout, entry format, conventions, and useful queries:
-[references/format.md](references/format.md).
-
-## Procedure
-
-### 1. Resolve the person
-
-Read `USER.md`, then resolve the target name to its canonical form:
-
-```bash
-ls knowledge/Tasks/
-rg "{name}" knowledge/People/
-```
-
-If no board exists yet, create one (Step 4).
-
-### 2. Read the current board
-
-```bash
-cat "knowledge/Tasks/{Person Name}.md"
-```
-
-Parse the existing entries to: avoid duplicates, understand current workload,
-and find the right insertion point.
-
-### 3. Perform the operation
-
-Pick **add**, **update**, **close**, **list**, or **housekeeping** based on the
-request.
-
-#### Add
-
-1. Check for duplicates. If a near-duplicate exists, update it instead.
-2. Pick the section per the routing rules in
-   [references/format.md](references/format.md#section-routing).
-3. Append the entry at the **bottom** of that section using the format from
-   `references/format.md`.
-4. Verify any referenced Project note exists.
-
-#### Update
-
-Find the task by its bold title (fuzzy match OK). Apply changes:
-
-- **Status change:** move the entire entry between sections.
-- **Priority change:** update the `| {priority} |` segment.
-- **Due date change:** update or add `| due YYYY-MM-DD |`.
-- **Add context:** append to the indented line.
-
-Use Edit for targeted modifications.
-
-#### Close
-
-Find the task, remove it from its section, and add to the **top** of
-`## Recently Done` using the closed-task format in
-[references/format.md](references/format.md#closed-task-format).
-
-#### List
-
-Run the queries in [references/format.md](references/format.md#useful-queries)
-and present results grouped by person or project as the user's question
-warrants.
-
-#### Housekeeping (scheduled)
-
-1. Prune entries older than 14 days from `## Recently Done`.
-2. Flag overdue tasks (due in the past, still in `## Open` or `## In Progress`)
-   — report to the user; do **not** auto-modify.
-3. Merge duplicates on the same board.
-4. Spot-check `[[People/]]`, `[[Projects/]]`, `[[Goals/]]` references point to
-   existing notes.
-
-### 4. Write updates
-
-For a new board, create `knowledge/Tasks/{Person Name}.md` with all four
-sections (template in
-[references/format.md](references/format.md#board-structure)).
-
-For an existing board, use Edit for targeted changes — never rewrite the whole
-file.
-
-### 5. Migrate open items (one-time)
-
-When first setting up boards, scan source notes for `## Open items` sections:
-
-```bash
-rg -l "## Open items" knowledge/People/ knowledge/Projects/ knowledge/Goals/
-```
-
-Convert each item into a task entry on the relevant person's board. **Do not**
-remove the original — it stays as the historical record; the board becomes the
-living tracker.

package/templates/.claude/skills/manage-tasks/references/format.md

@@ -1,73 +0,0 @@
-# Task Board Format
-
-Reference data for `manage-tasks`.
-
-## Board structure
-
-Each task board is a markdown file with four sections, always present (even if
-empty), in this order:
-
-```markdown
-# {Person Name}
-
-## In Progress
-
-## Open
-
-## Blocked
-
-## Recently Done
-```
-
-## Task entry
-
-```markdown
-- [ ] **{Task title}** | {priority} | due {YYYY-MM-DD} | [[Projects/Name]] → [[Goals/Name]]
-  {Context line with source info and backlinks.}
-```
-
-### Conventions
-
-- **Priorities:** `high` | `medium` | `low`. Omit when medium (the default).
-- **Due dates:** include only when there is a real deadline. Format
-  `due YYYY-MM-DD`.
-- **Goal link:** append `→ [[Goals/Name]]` only when the task clearly serves a
-  specific Goal — not every task needs one.
-- **Titles are the ID:** keep them unique within a board. No task IDs.
-- **Recently Done:** keep the last 14 days; older entries are pruned during
-  housekeeping.
-
-## Closed-task format
-
-Closed entries drop priority, due date, project link, and context:
-
-```markdown
-- [x] **{Task title}** | completed {YYYY-MM-DD}
-```
-
-## Section routing
-
-- Default add target: `## Open`.
-- Move to `## In Progress` when the user says "I'm working on" / "started".
-- Move to `## Blocked` when the user describes a wait condition; include what's
-  needed and from whom in the context line.
-- Move to `## Recently Done` when closed.
-
-## Useful queries
-
-```bash
-# All open / in-progress tasks
-rg "^- \[ \] \*\*" knowledge/Tasks/
-
-# Tasks for a specific project
-rg "Projects/{Name}" knowledge/Tasks/
-
-# High priority tasks
-rg "\| high \|" knowledge/Tasks/
-
-# Find every due date — compare against today to spot overdue
-rg "due 20[0-9]{2}-[0-9]{2}-[0-9]{2}" knowledge/Tasks/
-
-# Blocked tasks with their context
-rg -A1 "^- \[ \]" knowledge/Tasks/ | rg -B1 "Waiting on"
-```

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

@@ -1,141 +0,0 @@
----
-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

@@ -1,55 +0,0 @@
-# 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/USER.md

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