@forwardimpact/outpost 3.3.4 → 3.5.0

package/templates/.claude/skills/req-workday/SKILL.md

@@ -2,7 +2,7 @@
 name: req-workday
 description: >
   Import candidates from a Workday requisition export (.xlsx) into
-  knowledge/Candidates/. Parses requisition metadata and candidate data,
+  Knowledge/Candidates/. Parses requisition metadata and candidate data,
   creates candidate briefs and CV.md files from resume text, and integrates
   with the existing req-track pipeline. Use when the user provides a
   Workday export file or asks to import candidates from an XLSX requisition
@@ -12,7 +12,7 @@ description: >
 # Workday Requisition Import
 
 Import candidates from a Workday requisition export (`.xlsx`) into
-`knowledge/Candidates/`. Extract requisition metadata and candidate profiles,
+`Knowledge/Candidates/`. Extract requisition metadata and candidate profiles,
 create standardized briefs and `CV.md` files from the embedded resume text, and
 integrate with the `req-track` pipeline format.
 
@@ -36,9 +36,9 @@ integrate with the `req-track` pipeline format.
 
 ## Outputs
 
-- `knowledge/Candidates/{Clean Name}/brief.md` — candidate profile.
-- `knowledge/Candidates/{Clean Name}/CV.md` — resume text as markdown.
-- `knowledge/Roles/{Req ID} — {Title}.md` — created or updated.
+- `Knowledge/Candidates/{Clean Name}/brief.md` — candidate profile.
+- `Knowledge/Candidates/{Clean Name}/CV.md` — resume text as markdown.
+- `Knowledge/Roles/{Req ID} — {Title}.md` — created or updated.
 - Updated existing briefs when a candidate already exists.
 
 <do_confirm_checklist goal="Verify the Workday import is consistent with
@@ -46,7 +46,7 @@ req-track">
 
 - [ ] XLSX parsed; candidate count matches the parser summary.
 - [ ] Requisition metadata extracted (ID, title; HM/recruiter when available).
-- [ ] Each candidate has a directory under `knowledge/Candidates/{Clean Name}/`
+- [ ] Each candidate has a directory under `Knowledge/Candidates/{Clean Name}/`
       (annotation stripped).
 - [ ] `CV.md` created for every candidate with resume text — faithfully
       reproduced (no rewriting).
@@ -93,13 +93,13 @@ header indices, name annotations) are in
 ### 3. Create or update the Role file
 
 ```bash
-ls knowledge/Roles/ | grep "{Req ID}"
+ls Knowledge/Roles/ | grep "{Req ID}"
 ```
 
 Use the **Role file stub** in
 [references/templates.md](references/templates.md). Resolve the domain lead by:
 
-1. `rg "{Req ID}" knowledge/` — look in project timelines, People notes, Topics
+1. `rg "{Req ID}" Knowledge/` — look in project timelines, People notes, Topics
    for context.
 2. Reading the hiring manager's People note for `**Reports to:**` and walking up
    to a VP or senior leader.
@@ -111,7 +111,7 @@ If the Role file already exists, follow the existing-file rules in
 ### 4. Build the candidate index
 
 ```bash
-ls -d knowledge/Candidates/*/ 2>/dev/null
+ls -d Knowledge/Candidates/*/ 2>/dev/null
 ```
 
 Match imported candidates against existing notes by name (fuzzy — middle names,
@@ -126,7 +126,7 @@ step value in the Pipeline entry.
 ### 6. Write `CV.md`
 
 For every candidate with resume text, create
-`knowledge/Candidates/{Clean Name}/CV.md` using the **CV.md template** in
+`Knowledge/Candidates/{Clean Name}/CV.md` using the **CV.md template** in
 [references/templates.md](references/templates.md).
 
 ### 7. Write or update the brief
@@ -136,7 +136,7 @@ Brief layout (new candidates) and edit rules (existing candidates):
 [references/templates.md](references/templates.md).
 
 ```bash
-mkdir -p "knowledge/Candidates/{Clean Name}"
+mkdir -p "Knowledge/Candidates/{Clean Name}"
 ```
 
 For existing candidates, apply targeted Edit operations only — never rewrite the
@@ -145,7 +145,7 @@ file.
 ### 8. Capture insights
 
 After the batch, review for strategic observations and add bullets to
-`knowledge/Candidates/Insights.md` under `## Placement Notes` with
+`Knowledge/Candidates/Insights.md` under `## Placement Notes` with
 `[[Candidates/Name/brief|Name]]` links. See `req-track` Step 5b for the
 inclusion criteria.
 

package/templates/.claude/skills/req-workday/references/templates.md

@@ -5,7 +5,7 @@ Reference templates for `req-workday` Steps 1b, 4, and 5.
 ## Role file stub
 
 Use when no Role file exists for the requisition. Filename:
-`knowledge/Roles/{Req ID} — {Short Title}.md`.
+`Knowledge/Roles/{Req ID} — {Short Title}.md`.
 
 ```markdown
 # {Requisition Title}
@@ -41,7 +41,7 @@ provides one and the field is `—`; update `Last activity` to today; append
 
 ## CV.md template
 
-Save to `knowledge/Candidates/{Clean Name}/CV.md` when resume text exists. Skip
+Save to `Knowledge/Candidates/{Clean Name}/CV.md` when resume text exists. Skip
 when it doesn't.
 
 ```markdown
@@ -60,7 +60,7 @@ when it doesn't.
 
 ## Candidate brief
 
-Save to `knowledge/Candidates/{Clean Name}/brief.md`. Format follows
+Save to `Knowledge/Candidates/{Clean Name}/brief.md`. Format follows
 `req-track`.
 
 ```markdown

package/templates/.claude/skills/send-chat/SKILL.md

@@ -35,7 +35,7 @@ Run when the user asks to:
 When the user mentions ANY person:
 
 1. **STOP** — Do not open the chat platform yet
-2. **SEARCH** — Look them up: `rg -l "{name}" knowledge/People/`
+2. **SEARCH** — Look them up: `rg -l "{name}" Knowledge/People/`
 3. **READ** — Read their note to understand context, role, recent interactions
 4. **UNDERSTAND** — Know who they are, what you've been working on together
 5. **THEN PROCEED** — Only now compose the message and use browser automation
@@ -53,10 +53,10 @@ a full name using the knowledge graph:
 
 ```bash
 # Find person by partial name
-rg -l -i "{name}" knowledge/People/
+rg -l -i "{name}" Knowledge/People/
 
 # If ambiguous, read candidates to disambiguate
-cat "knowledge/People/{Candidate}.md"
+cat "Knowledge/People/{Candidate}.md"
 ```
 
 **If ambiguous** (multiple matches), ask the user which person they mean — list
@@ -73,7 +73,7 @@ can review and edit the exact message before it's sent.
 ### Draft Workflow
 
 1. **Compose the message** based on context and user intent.
-2. **Write it to a draft file** at `drafts/chat-{recipient-slug}-{date}.md`
+2. **Write it to a draft file** at `Drafts/chat-{recipient-slug}-{date}.md`
    - `{recipient-slug}` = lowercase, hyphenated full name (e.g. `sarah-chen`)
    - `{date}` = ISO date (e.g. `2026-02-19`)
 3. **Show the user the draft** — display the file path and contents.

package/templates/.claude/skills/upstream-instructions/SKILL.md

@@ -0,0 +1,154 @@
+---
+name: upstream-instructions
+description: Track changes made to this installation's instruction files — the root CLAUDE.md, agent profiles, and skills — and record them in a single root CHANGELOG.md so improvements can be contributed back to the upstream monorepo. Use when CLAUDE.md, agents, or skills have been modified, added, or removed locally and those changes should be documented for upstream.
+---
+
+# Upstream Instructions
+
+Track changes to this installation's **instructions** and record them in one
+root `CHANGELOG.md` so improvements can be contributed back to the upstream
+monorepo. "Instructions" means all three surfaces, treated equally:
+
+- **`CLAUDE.md`** (root) — installation-wide instructions.
+- **`.claude/agents/*.md`** — agent profiles.
+- **`.claude/skills/*/`** — skills (`SKILL.md` and reference files).
+
+## Trigger
+
+- The user asks to prepare local instruction changes for upstream contribution.
+- The root `CLAUDE.md`, an agent profile, or a skill has been modified, added,
+  or removed.
+- The user wants to document what changed locally before syncing upstream.
+
+## Prerequisites
+
+- A working Outpost installation with `CLAUDE.md`, `.claude/agents/`, and
+  `.claude/skills/`.
+- Git available for change detection.
+
+## Inputs
+
+- `CLAUDE.md` — root installation instructions.
+- `.claude/agents/*.md` — agent profiles.
+- `.claude/skills/*/SKILL.md` and reference files — skills.
+- `CHANGELOG.md` (root) — the existing changelog, for the last documented date.
+- Git history and working tree — change detection.
+
+## Outputs
+
+- `CHANGELOG.md` (root) — a **single** reverse-chronological changelog covering
+  all three surfaces. There are no per-skill or per-agent changelogs.
+
+<do_confirm_checklist goal="Verify the changelog is upstream-ready">
+
+- [ ] Exactly one root `CHANGELOG.md`; no stray per-skill / per-agent changelogs
+      left behind.
+- [ ] Every entry names its **Scope** (which surface(s) and file(s) it touched).
+- [ ] Each entry has **What**, **Why**, and **Details**.
+- [ ] Descriptions are specific enough for an upstream maintainer to act on (not
+      "updated CLAUDE.md" / "fixed stuff").
+- [ ] New skills/agents include a brief description of their purpose; removed
+      ones explain why.
+- [ ] Dates come from git history (or the date the change was made for
+      uncommitted edits), not guessed.
+- [ ] No duplicate entries for the same change.
+
+</do_confirm_checklist>
+
+## Procedure
+
+### 1. Find the last documented state
+
+```bash
+head -20 CHANGELOG.md 2>/dev/null   # newest date already recorded, if any
+```
+
+### 2. Identify changed instructions
+
+Detect changes across all three surfaces — committed and uncommitted:
+
+```bash
+# Committed changes since the last documented date (or all history)
+git log --after="<last-entry-date>" --name-status -- \
+  CLAUDE.md '.claude/agents/' '.claude/skills/'
+
+# Uncommitted working-tree changes (common in a live installation)
+git status --short -- CLAUDE.md '.claude/agents/' '.claude/skills/'
+```
+
+If no `CHANGELOG.md` exists yet, consider all changes since the initial commit.
+
+### 3. Classify each change
+
+| Surface       | What it covers                                  |
+| ------------- | ----------------------------------------------- |
+| `CLAUDE.md`   | Root installation instructions                  |
+| `agent:<name>`| A profile in `.claude/agents/`                  |
+| `skill:<name>`| A skill in `.claude/skills/`                    |
+
+| Type       | Description                                            |
+| ---------- | ------------------------------------------------------ |
+| `added`    | New instruction file that doesn't exist upstream       |
+| `modified` | Existing instruction updated                           |
+| `removed`  | Instruction file or directory deleted                  |
+| `renamed`  | File or directory renamed                              |
+
+A single change often spans surfaces (e.g. a KB-structure change touching
+`CLAUDE.md`, several agents, and several skills) — record it as **one entry**
+whose Scope lists every surface touched. Diff to confirm the actual change:
+
+```bash
+git diff <commit> -- CLAUDE.md
+git diff <commit> -- '.claude/agents/<agent>.md'
+git diff <commit> -- '.claude/skills/<skill>/'
+```
+
+### 4. Describe each change
+
+Every entry must answer:
+
+1. **What changed?** — the specific instruction or behaviour modified.
+2. **Why?** — the problem encountered or improvement discovered in use.
+3. **Details** — a summary of the actual change (not a full diff).
+
+Good: "Agents now read `Knowledge/Priorities/` at the start of every wake and
+flag anything that threatens a priority — drafts and triage were ignoring
+strategic context."
+
+Bad: "Updated the agents" / "Fixed stuff" / "Changed line 42".
+
+### 5. Write the changelog
+
+Create or update the single root `CHANGELOG.md` (newest first):
+
+```markdown
+# Outpost Instructions Changelog
+
+Changes to this installation's instructions — root `CLAUDE.md`, agent profiles
+(`.claude/agents/`), and skills (`.claude/skills/`) — for consideration upstream
+in the Forward Impact monorepo. Documents only; pushes nothing.
+
+## <YYYY-MM-DD>
+
+**Scope:** <surfaces/files, e.g. "skill: extract-entities; CLAUDE.md; agents: librarian, recruiter">
+**Type:** <added | modified | removed | renamed>
+
+**What:** <one-line summary>
+
+**Why:** <problem or improvement that motivated it>
+
+**Details:**
+<2–6 lines describing the specific changes across the listed surfaces>
+
+---
+```
+
+Worked examples in [references/examples.md](references/examples.md).
+
+## Notes
+
+- This skill **documents only** — it does not push or merge anything.
+- The single root `CHANGELOG.md` is consumed by the **downstream-instructions**
+  skill in the upstream monorepo.
+- When in doubt about whether a change is upstream-worthy, include it; the
+  upstream maintainer decides what to incorporate.

package/templates/.claude/skills/upstream-instructions/references/examples.md

@@ -0,0 +1,97 @@
+# Changelog Examples
+
+Reference output for `upstream-instructions` Step 5. There is **one** root
+`CHANGELOG.md` with reverse-chronological entries. Each entry's **Scope** names
+the surface(s) it touched — `CLAUDE.md`, `agent:<name>`, `skill:<name>` — and a
+single entry may span several.
+
+## Cross-surface change (one change, many files)
+
+```markdown
+## 2026-06-18
+
+**Scope:** KB structure; CLAUDE.md; agents: librarian, chief-of-staff, recruiter; skills: extract-entities, anarlog-process, meeting-prep, req-decide
+**Type:** removed
+
+**What:** Dropped the Goals entity type; Priorities is now the only user-set
+strategic layer.
+
+**Why:** One strategic layer is simpler than two — time-bound targets fold into
+Priorities, removing the Project↔Goal↔Priority coupling that earned nothing.
+
+**Details:**
+- Deleted `Knowledge/Goals/`; repointed live backlinks to `Priorities/C - Onboarding`.
+- CLAUDE.md workspace-layout tree no longer lists `Goals/`.
+- Agents: dropped Goals from the librarian index/triage, chief-of-staff state
+  sources, and recruiter strategic links.
+- extract-entities: removed Goals from resolution/index; renamed
+  `templates-goals-priorities.md` → `templates-priorities.md`; deleted Goal link
+  rules. anarlog-process / meeting-prep / req-decide: dropped Goals inputs.
+
+---
+```
+
+## Modified skill
+
+```markdown
+## 2026-03-01
+
+**Scope:** skill: req-track
+**Type:** modified
+
+**What:** Added gender field extraction for diversity tracking.
+
+**Why:** The recruitment pipeline lacked diversity metrics — pool composition was
+invisible without structured gender data.
+
+**Details:**
+- Added a Gender field to the candidate brief template (Woman / Man / —).
+- Added extraction rules (pronouns, gendered titles) and a note that the field
+  has no bearing on hiring decisions.
+- Updated the quality checklist to verify the field.
+
+---
+```
+
+## Modified agent
+
+```markdown
+## 2026-06-19
+
+**Scope:** agents: all six profiles
+**Type:** modified
+
+**What:** Agents now read `Knowledge/Priorities/` at the start of every wake and
+flag anything that threatens a priority.
+
+**Why:** Sync, triage, and drafting were ignoring strategic context; signals that
+could block a priority passed silently.
+
+**Details:**
+- Added a uniform `## Priorities` section and a `Priority Watch` output line to
+  the five worker agents.
+- The chief-of-staff consolidates each agent's `Priority Watch` flags into a
+  dedicated section of the daily briefing.
+
+---
+```
+
+## New skill
+
+```markdown
+## 2026-03-01
+
+**Scope:** skill: anarlog-process
+**Type:** added
+
+**What:** New skill for processing Anarlog meeting recordings.
+
+**Why:** Meeting notes were being lost — Anarlog captures transcriptions but they
+weren't integrated into the knowledge base.
+
+**Details:**
+- Reads transcription files, extracts people/decisions/action items, and links
+  attendees to `Knowledge/People/`.
+
+---
+```

package/templates/CLAUDE.md

@@ -2,7 +2,8 @@
 
 You are the user's personal knowledge assistant. You help draft emails, prep for
 meetings, track projects, and answer questions, backed by a live knowledge graph
-built from their emails, calendar, and meeting notes, all stored locally.
+built from their emails, calendar, and meeting notes, all stored as plain files on
+the user's machine.
 
 ## Ethics & Integrity — NON-NEGOTIABLE
 
@@ -27,26 +28,31 @@ When in doubt, err toward discretion.
 
 ## Voice
 
-Be 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.
+Be supportive and direct. Explain complex things clearly without hedging. When
+the next step is obvious, take it. Ask at most one clarifying question, at the
+start. Reference files by full path. Confirm before destructive actions.
 
 ## Dependencies
 
 - **ripgrep** (`rg`) for fast knowledge graph searches — `brew install ripgrep`.
 
-## Workspace Layout
+## Workspace Layout & Sharing
+
+The **root is personal and local — never shared.** Only `Knowledge/` is shared
+with the team over a synced filesystem; each member keeps their own root,
+`Drafts/`, and `Briefings/`. KBs are **not** Git repositories — they sync as
+plain files. `CLAUDE.md` and `.claude/` are yours to tweak; use the `fit-outpost`
+CLI to install or update the standard instruction set.
 
 ```
-./
-├── knowledge/         # The knowledge graph (Obsidian-compatible)
-│   ├── People/ Organizations/ Projects/ Topics/
-│   └── Candidates/ Goals/ Priorities/ Conditions/ Roles/
-├── .claude/skills/    # Auto-discovered skill files
-├── drafts/            # Email drafts (draft-emails skill)
-├── CLAUDE.md          # This file
-└── .mcp.json          # MCP server configurations (optional)
+./                      # Personal root — never shared
+├── CLAUDE.md           # This file
+├── .claude/            # Agent profiles + auto-discovered skills
+├── Knowledge/          # Knowledge graph — SHARED (Obsidian-compatible)
+│   └── People/ Organizations/ Projects/ Topics/ Candidates/ Priorities/ Conditions/ Roles/
+├── Drafts/             # Email/chat drafts (personal)
+├── Briefings/          # Daily briefings (personal)
+└── .mcp.json           # MCP config (optional)
 ```
 
 ## Agents
@@ -54,29 +60,29 @@ destructive actions.
 Agents in `.claude/agents/` maintain this KB, woken on a 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, anarlog-process                                          |
-| **librarian**      | Knowledge graph maintenance     | Every 15 min    | extract-entities, organize-files                                                             |
-| **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 | _(reads all state for daily briefings)_                                                      |
+Each agent's skills are declared in its own profile under `.claude/agents/`.
+
+| Agent              | Domain                          | Schedule        |
+| ------------------ | ------------------------------- | --------------- |
+| **postman**        | Communication triage and drafts | Every 5 min     |
+| **concierge**      | Meeting prep and transcripts    | Every 10 min    |
+| **librarian**      | Knowledge graph maintenance     | Every 15 min    |
+| **recruiter**      | Engineering recruitment         | Every 30 min    |
+| **head-hunter**    | Passive talent scouting         | Every 60 min    |
+| **chief-of-staff** | Daily briefings and priorities  | 7am, Mon 7:30am |
 
 Each agent writes `~/.cache/fit/outpost/state/{agent}_triage.md` per wake. The
-**chief-of-staff** reads all five to write daily briefings in
-`knowledge/Briefings/`.
+**chief-of-staff** reads all of them to write daily briefings in `Briefings/`.
 
 ## Cache Directory (`~/.cache/fit/outpost/`)
 
-Synced data and runtime state live outside the KB; only notes and drafts live
-inside it.
+Synced data and runtime state live outside the KB; only notes, drafts, and
+briefings live inside it.
 
-**Resolve `~` before passing a path to a tool.** Paths like
-`~/.cache/fit/outpost/` are shorthand; read `$HOME` at runtime and never hardcode
-it. Shell commands expand `~`, but the Write and Edit tools do not — a literal
-`~/...` given to those creates a stray `.cache/` inside the KB. Always pass them
-the full `$HOME/...` path.
+**Resolve `~` before passing a path to a tool.** Shell commands expand `~`, but
+the Write and Edit tools do not — a literal `~/...` creates a stray `.cache/`
+inside the KB. Read `$HOME` at runtime and pass the full `$HOME/...` path. Read
+meetings, emails, and messages directly from the source dirs below.
 
 - `apple_mail/` — Mail threads as `.md` (plus `attachments/`)
 - `apple_calendar/` — Calendar events as `.json`
@@ -90,38 +96,26 @@ the full `$HOME/...` path.
 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
+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, org, project,
-or topic, run `rg "keyword" knowledge/` to surface every note first — one note is
-never the full story. Use it for tasks involving named entities, people, projects,
-meetings, emails, or calendar data; skip general knowledge and brainstorming.
-
-## Synced Sources
-
-Read upcoming meetings, recent emails, and messages directly from:
-
-- `~/.cache/fit/outpost/apple_mail/`
-- `~/.cache/fit/outpost/apple_calendar/`
-- `~/.cache/fit/outpost/teams_chat/`
+or topic, run `rg "keyword" Knowledge/` to surface every note — one note is never
+the full story. Skip it only for general knowledge and brainstorming.
 
 ## Skills
 
-Skills auto-discover from `.claude/skills/` and load by context: data sync (Apple
-Mail, Calendar, Teams), knowledge-graph maintenance (extract-entities, recruitment
-pipeline), and communication (draft-emails, send-chat, meeting-prep, decks, docs).
+Skills auto-discover from `.claude/skills/` and load by context — data sync,
+knowledge-graph maintenance, recruitment, and communication.
 
 ## User Identity
 
 The current user's identity is cached at
-`~/.cache/fit/outpost/state/identity.md` — read it directly. If it is missing or
-stale, run the `identify-user` skill to refresh it from the corporate directory.
+`~/.cache/fit/outpost/state/identity.md` — read it directly. If missing or stale,
+run the `identify-user` skill to refresh it from the corporate directory.
 
 ## Working Outside This Directory
 
-You have full filesystem access (macOS). For tasks outside this KB
-(organizing the Desktop, finding files in Downloads), use shell commands
-directly.
+You have full filesystem access (macOS). For tasks outside this KB, use shell
+commands directly.

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

@@ -1,63 +0,0 @@
-# Goal and Priority Templates
-
-Goals and Priorities are **never auto-created** by `extract-entities`. They are
-set deliberately by the user. These templates are 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?}
-
-## Goals
-{Time-bound targets that ladder to this priority — backlinks to knowledge/Goals/}
-
-## Projects
-- [[Projects/{Project}]] — {relationship}
-
-## Key facts
-{substantive facts only — leave empty if none}
-```
-
-## Goals
-
-```markdown
-# {Goal Name}
-
-## Info
-**Priority:** [[Priorities/{Priority}]]
-**Status:** {on track|at risk|off track|achieved|abandoned}
-**Owner:** [[People/{Person}]]
-**Target date:** {YYYY-MM-DD}
-**Set:** {YYYY-MM-DD}
-
-## Outcome
-{1-2 sentences: what measurable success looks like}
-
-## Blockers
-{Active Conditions that impede this goal — link to knowledge/Conditions/}
-- [[Conditions/{Condition}]] — {impact on this goal}
-
-## Projects
-- [[Projects/{Project}]] — {how it contributes}
-
-## Progress
-- **{YYYY-MM-DD}**: {Update on progress toward the outcome}
-
-## Key facts
-{substantive facts only — leave empty if none}
-
-## Risks
-{known risks to achieving this goal — leave empty if none}
-```