@forwardimpact/outpost 3.8.0 → 3.8.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@forwardimpact/outpost",
-  "version": "3.8.0",
+  "version": "3.8.1",
   "description": "Personal operations center — context from email, calendar, and knowledge assembled so preparation is continuous, not a morning scramble.",
   "homepage": "https://www.forwardimpact.team",
   "repository": {

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

@@ -66,7 +66,7 @@ candidates, pipeline totals by stage/track, aggregate diversity, retention flags
 
 ```
 Decision: {observation and chosen action}
-Action: {e.g. "req-screen for John Smith against J060 forward_deployed"}
+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/candidate-report/SKILL.md

@@ -31,7 +31,7 @@ before deciding whether to invest interview time.
 
 - **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
+  `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.
 - **Recipient** — pod lead or hiring manager the report is for.
 - **CV file** (optional) — read directly when no `screening.md` exists.

package/templates/.claude/skills/req-assess/references/rubric.md

@@ -51,7 +51,7 @@ from the transcript — "seemed strong" is not evidence.
 | `emerging`      | Behaviour not observed or only when prompted                 |
 | `developing`    | Behaviour present but inconsistent or surface-level          |
 | `practicing`    | Behaviour consistent and natural throughout the interview    |
-| `role_modeling` | Behaviour demonstrated at high level, influenced the room    |
+| `role-modeling` | Behaviour demonstrated at high level, influenced the room    |
 | `exemplifying`  | Behaviour exceptional, set the standard for the conversation |
 
 ## Level signals

package/templates/.claude/skills/req-decide/references/template.md

@@ -64,7 +64,7 @@ journey.}
 
 ### Track Confirmation
 
-**Recommended track:** {forward_deployed / platform / either}
+**Recommended track:** {forward-deployed / platform / either}
 
 {Explain track fit, referencing interview moments.}
 

package/templates/.claude/skills/req-scan/references/template.md

@@ -10,7 +10,7 @@ Reference for `req-scan` Step 4. Save to `Knowledge/Prospects/{Name}.md`.
 **Date found:** {YYYY-MM-DD}
 **Location:** {location or "Not specified"}
 **Estimated level:** {J040–J110} (confidence: {high/medium/low})
-**Best track fit:** {forward_deployed / platform / either}
+**Best track fit:** {forward-deployed / platform / either}
 **Match strength:** {strong / moderate}
 
 ## Profile

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

@@ -92,7 +92,7 @@ If no target is available, estimate one using the level heuristics in
 ```bash
 bunx fit-pathway job {discipline} {level} --track={track}
 bunx fit-pathway job {discipline} {level} --track={track} --skills
-bunx fit-pathway track forward_deployed
+bunx fit-pathway track forward-deployed
 bunx fit-pathway track platform
 ```
 

package/templates/.claude/skills/req-screen/references/template.md

@@ -26,7 +26,7 @@ around the screening question — is this worth an interview?}
 | Dimension      | Assessment                             |
 | -------------- | -------------------------------------- |
 | **Level**      | {estimated level and confidence}       |
-| **Track fit**  | {forward_deployed / platform / either} |
+| **Track fit**  | {forward-deployed / platform / either} |
 | **Discipline** | {best discipline match}                |
 | **Gender**     | {Woman / Man / —}                      |
 
@@ -54,7 +54,7 @@ Standard reference: `{discipline} {level} --track={track}`
 
 ## Track Fit Analysis
 
-{Paragraph explaining why the candidate fits forward_deployed,
+{Paragraph explaining why the candidate fits forward-deployed,
 platform, or either. Reference specific CV evidence.}
 
 ## Screening Recommendation

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

@@ -186,7 +186,7 @@ either skill until it changes.
 bunx fit-pathway skill --list
 ```
 
-Use agent-aligned engineering standard IDs (e.g. `data_integration`,
+Use agent-aligned engineering standard IDs (e.g. `data-integration`,
 `full_stack_development`, `architecture_and_design`) in the `## Skills` section
 instead of free-form tags. Flag any candidate with a CV attachment for
 `req-screen`.

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

@@ -15,7 +15,7 @@ Use when no Role file exists for the requisition. Filename:
 **Title:** {Full title from export}
 **Level:** {Infer from title: "Principal" → J100, "Staff" → J090, "Director" → J100 M-track, "Senior" → J070}
 **Track:** {P-track for IC roles, M-track for Director/Manager roles}
-**Discipline:** {Infer: "Software Engineer" → software_engineering, "Data Engineer" → data_engineering, "Data Scientist" → data_science}
+**Discipline:** {Infer: "Software Engineer" → software-engineering, "Data Engineer" → data-engineering, "Data Scientist" → data-science}
 **Domain lead:** —
 **Hiring manager:** {From export metadata if available, or "—"}
 **Locations:** {Primary Location from export}