@forwardimpact/outpost 3.0.3

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

@@ -0,0 +1,127 @@
+# Templates
+
+Markdown templates used by `req-track` for Role files and Candidate briefs.
+
+## Role file stub
+
+Used by Step 0b when a Req appears on a candidate brief but no Role file exists.
+
+```markdown
+# {Title from candidate Req field}
+
+## Info
+**Req:** {req number}
+**Title:** {title from Req field}
+**Level:** —
+**Track:** —
+**Discipline:** —
+**Domain lead:** —
+**Hiring manager:** —
+**Locations:** —
+**Positions:** —
+**Channel:** hr
+**Status:** open
+**Opened:** —
+**Last activity:** {today}
+
+## Connected to
+- Staffing/recruitment project
+
+## Candidates
+<!-- Rebuilt each cycle -->
+
+## Notes
+- Stub created automatically — enrich with data from emails, calendar, and imports.
+```
+
+## Role Candidates table
+
+Step 0b rebuilds this table on each Role file by scanning briefs:
+
+```markdown
+## Candidates
+| Candidate | Status | Channel | First seen |
+|---|---|---|---|
+| [[Candidates/{Name}/brief\|{Name}]] | {status} | {channel} | {date} |
+```
+
+Sort by First seen, newest first.
+
+## Candidate brief
+
+Used by Step 5 for new candidates. File:
+`knowledge/Candidates/{Full Name}/brief.md`.
+
+```markdown
+# {Full Name}
+
+## Info
+**Title:** {professional title/function}
+**Rate:** {rate or "—"}
+**Availability:** {availability or "—"}
+**English:** {level or "—"}
+**Location:** {location or "—"}
+**Gender:** {Woman / Man / —}
+**Source:** [[Organizations/{Agency}]] via [[People/{Recruiter Name}]]
+**Status:** {pipeline status}
+**First seen:** {YYYY-MM-DD}
+**Last activity:** {YYYY-MM-DD}
+{extra fields here — see below}
+
+## Summary
+{2-3 sentences: role, experience level, key strengths}
+
+## CV
+- [CV.pdf](./CV.pdf)
+
+## Connected to
+- [[Organizations/{Agency}]] — sourced by
+- [[People/{Recruiter}]] — recruiter
+- [[Roles/{Role filename without .md}]] — applied to
+- [[People/{Hiring manager}]] — hiring manager
+- [[People/{Domain lead}]] — domain lead
+
+## Pipeline
+- **{date}**: {event}
+
+## Skills
+{comma-separated agent-aligned engineering standard skill IDs}
+
+## Interview Notes
+{omit section if no interviews yet}
+
+## Notes
+{free-form observations — always present, even if empty}
+```
+
+Omit `## CV` when no CV attachment exists.
+
+## Extra Info fields
+
+Place after `Last activity`, in this order, only when known:
+
+```markdown
+**Role:** {internal requisition profile, e.g. "Staff Engineer"}
+**Req:** [[Roles/{filename}|{req number}]] — {title}
+**Channel:** {hr / vendor}
+**Hiring manager:** {[[People/{name}]] or "—"}
+**Domain lead:** {[[People/{name}]] or "—"}
+**Internal/External:** {Internal / External / External (Prior Worker)}
+**Model:** {engagement model, e.g. "B2B (via Agency) — conversion to FTE not possible"}
+**Current title:** {current job title and employer}
+**Email:** {personal or work email}
+**Phone:** {phone number}
+**LinkedIn:** {profile URL}
+**Also known as:** {alternate spellings}
+```
+
+For vendor-pipeline candidates the Req backlink uses
+`[[Roles/{filename}|Vendor]] — {description}`.
+
+## Optional sections
+
+Add between `## Skills` and `## Notes` when data is rich enough, in this order:
+`## Education`, `## Certifications`, `## Work History`, `## Key Facts`,
+`## Interview Notes` (`### YYYY-MM-DD — {description}` per interview).
+
+`## Notes` is always last. If `## Open Items` exists, place it after Notes.

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

@@ -0,0 +1,162 @@
+---
+name: req-workday
+description: >
+  Import candidates from a Workday requisition export (.xlsx) into
+  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
+  export.
+---
+
+# Workday Requisition Import
+
+Import candidates from a Workday requisition export (`.xlsx`) into
+`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.
+
+## Trigger
+
+- The user provides a Workday requisition export (`.xlsx`).
+- The user asks to import candidates from Workday or an XLSX export.
+- The user mentions a requisition ID and asks to process the export.
+
+## Prerequisites
+
+- A Workday requisition export accessible on the filesystem.
+- `read-excel-file` package installed:
+  `bun pm ls read-excel-file 2>/dev/null || bun install read-excel-file`.
+- User identity in `USER.md`.
+
+## Inputs
+
+- Path to the `.xlsx` file (e.g. `~/Downloads/4951493_…(Open).xlsx`).
+
+## 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.
+- Updated existing briefs when a candidate already exists.
+
+<do_confirm_checklist goal="Verify the Workday import is consistent with
+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}/`
+      (annotation stripped).
+- [ ] `CV.md` created for every candidate with resume text — faithfully
+      reproduced (no rewriting).
+- [ ] Pipeline status mapped from **Step / Disposition** (not Stage); raw step
+      preserved in the Pipeline entry.
+- [ ] Internal/External derived from name annotations and source.
+- [ ] Existing candidates updated via targeted edits (not duplicated).
+- [ ] Skills tagged with standard IDs; Gender set to `—` (export has no signal);
+      Channel = `hr`; Req backlinks to the Role file.
+
+</do_confirm_checklist>
+
+## Procedure
+
+Process **10 candidates per run**.
+
+### 1. Set up
+
+Read `USER.md`. Confirm the XLSX path. Ensure the parser dependency is
+installed:
+
+```bash
+bun pm ls read-excel-file 2>/dev/null || bun install read-excel-file
+```
+
+### 2. Parse the export
+
+```bash
+node .claude/skills/req-workday/scripts/parse-workday.mjs "<path>" --summary
+```
+
+Review the summary for sanity (candidate count, header detection). For the JSON
+consumed by later steps:
+
+```bash
+node .claude/skills/req-workday/scripts/parse-workday.mjs "<path>"
+```
+
+The output is `{ requisition, candidates }`. Format details (sheet shapes,
+header indices, name annotations) are in
+[references/xlsx-format.md](references/xlsx-format.md).
+
+### 3. Create or update the Role file
+
+```bash
+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
+   for context.
+2. Reading the hiring manager's People note for `**Reports to:**` and walking up
+   to a VP or senior leader.
+3. Falling back to `Domain lead: —` for later cycles.
+
+If the Role file already exists, follow the existing-file rules in
+`references/templates.md`.
+
+### 4. Build the candidate index
+
+```bash
+ls -d knowledge/Candidates/*/ 2>/dev/null
+```
+
+Match imported candidates against existing notes by name (fuzzy — middle names,
+accents, spelling variations).
+
+### 5. Determine pipeline status
+
+Map **Step / Disposition** to the `req-track` status using
+[references/status-mapping.md](references/status-mapping.md). Preserve the raw
+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
+[references/templates.md](references/templates.md).
+
+### 7. Write or update the brief
+
+Column-to-field map: [references/field-mapping.md](references/field-mapping.md).
+Brief layout (new candidates) and edit rules (existing candidates):
+[references/templates.md](references/templates.md).
+
+```bash
+mkdir -p "knowledge/Candidates/{Clean Name}"
+```
+
+For existing candidates, apply targeted Edit operations only — never rewrite the
+file.
+
+### 8. Capture insights
+
+After the batch, review for strategic observations and add bullets to
+`knowledge/Candidates/Insights.md` under `## Placement Notes` with
+`[[Candidates/Name/brief|Name]]` links. See `req-track` Step 5b for the
+inclusion criteria.
+
+### 9. Tag skills
+
+```bash
+bunx fit-pathway skill --list
+```
+
+Use standard skill IDs in each brief's `## Skills` section. Flag candidates with
+a `CV.md` for `req-screen`.
+
+### 10. Batch and report
+
+Process 10 candidates per run. Report `Processed {N}/{Total}`. If more remain,
+tell the user how many and offer to continue.

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

@@ -0,0 +1,40 @@
+# Field Mapping
+
+Reference for `req-workday` Step 5. Map Workday columns to candidate brief
+fields.
+
+## Core columns
+
+| Header                 | Maps to brief field…                              |
+| ---------------------- | ------------------------------------------------- |
+| Job Application        | `# {Name}`                                        |
+| Stage                  | Row detection only (not used for status)          |
+| Step / Disposition     | **Workday step** → status (see status-mapping.md) |
+| Resume                 | Reference only (no file)                          |
+| Date Applied           | **First seen**                                    |
+| Current Job Title      | **Current title**, Title                          |
+| Current Company        | **Current title** suffix                          |
+| Source                 | **Source**                                        |
+| Referred by            | **Source** suffix                                 |
+| Candidate Location     | **Location**                                      |
+| Phone                  | **Phone**                                         |
+| Email                  | **Email**                                         |
+| Availability Date      | **Availability**                                  |
+| Visa Requirement       | Notes                                             |
+| Eligible to Work       | Notes                                             |
+| Relocation             | Notes                                             |
+| Salary Expectations    | **Rate**                                          |
+| Non-Compete            | Notes                                             |
+| Total Years Experience | Summary context                                   |
+| All Job Titles         | Work History context                              |
+| Companies              | Work History context                              |
+| Degrees                | Education                                         |
+| Fields of Study        | Education                                         |
+| Language               | **English** / Language                            |
+| Resume Text            | `CV.md` content                                   |
+
+## Extra info field order
+
+After `Last activity`, in this order, only when known: `Req`,
+`Internal/External`, `Current title`, `Email`, `Phone`, `LinkedIn`. Follow the
+same order as `req-track`.

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

@@ -0,0 +1,38 @@
+# Step → Status Mapping
+
+Reference for `req-workday` Step 3. Map the **Step / Disposition** column to the
+`req-track` pipeline status. Do **not** use the Stage column for status — Stage
+is only used for row detection (stop condition).
+
+| Workday Step / Disposition             | Pipeline status    |
+| -------------------------------------- | ------------------ |
+| `Considered`                           | `new`              |
+| `Review`                               | `new`              |
+| `Manager Resume Screen`                | `screening`        |
+| `Schedule Recruiter Phone Screen`      | `screening`        |
+| `Manager Request to Move Forward (HS)` | `screening`        |
+| `Proposed Interview Slate`             | `screening`        |
+| `Assessment`                           | `screening`        |
+| `Manager Request to Decline (HS)`      | `rejected`         |
+| `Interview` / `Phone Screen`           | `first-interview`  |
+| `Second Interview`                     | `second-interview` |
+| `Reference Check`                      | `second-interview` |
+| `Offer`                                | `offer`            |
+| `Employment Agreement`                 | `offer`            |
+| `Background Check`                     | `hired`            |
+| `Ready for Hire`                       | `hired`            |
+| `Rejected` / `Declined`                | `rejected`         |
+
+Empty or unrecognized step → default to `new`.
+
+## Preserving the raw step
+
+The raw `step` value is always preserved in the parser's JSON output and must be
+stored in the candidate brief's `## Pipeline` section, e.g.
+
+```
+- **2026-02-10**: Applied via LinkedIn — Step: Manager Request to Move Forward (HS)
+```
+
+This lets the user filter and query candidates by their exact Workday
+disposition.

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

@@ -0,0 +1,126 @@
+# Output Templates
+
+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`.
+
+```markdown
+# {Requisition Title}
+
+## Info
+**Req:** {Req ID}
+**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}
+**Domain lead:** —
+**Hiring manager:** {From export metadata if available, or "—"}
+**Locations:** {Primary Location from export}
+**Positions:** —
+**Channel:** hr
+**Status:** open
+**Opened:** {Recruiting Start Date from export}
+**Last activity:** {today}
+
+## Connected to
+- Staffing/recruitment project
+
+## Candidates
+<!-- Rebuilt by req-track role sync -->
+
+## Notes
+- Created from requisition export on {today}.
+```
+
+If the Role file already exists: set `Hiring manager` only when the export
+provides one and the field is `—`; update `Last activity` to today; append
+`- Requisition export processed on {today}: {N} candidates` to Notes.
+
+## CV.md template
+
+Save to `knowledge/Candidates/{Clean Name}/CV.md` when resume text exists. Skip
+when it doesn't.
+
+```markdown
+# {Clean Name} — Resume
+
+> Extracted from Workday requisition export {Req ID} on {today's date}.
+> Original file: {Resume filename from column G}
+
+---
+
+{Resume text from column AC, preserving original formatting}
+```
+
+**Formatting:** preserve paragraph breaks; convert ALL-CAPS headers to
+`## Heading`; keep bullets/lists; never rewrite or summarise.
+
+## Candidate brief
+
+Save to `knowledge/Candidates/{Clean Name}/brief.md`. Format follows
+`req-track`.
+
+```markdown
+# {Clean Name}
+
+## Info
+**Title:** {Current Job Title or "—"}
+**Rate:** {Salary Expectations or "—"}
+**Availability:** {Availability Date or "—"}
+**English:** {Language field or "—"}
+**Location:** {Candidate Location or "—"}
+**Gender:** —
+**Source:** {Source} {via Referred by, if present}
+**Status:** {pipeline status}
+**First seen:** {Date Applied, YYYY-MM-DD}
+**Last activity:** {Date Applied, YYYY-MM-DD}
+**Req:** [[Roles/{Role filename}|{Req ID}]] — {Req Title}
+**Channel:** hr
+**Hiring manager:** {From Role file or "—"}
+**Domain lead:** {From Role file or "—"}
+**Internal/External:** {Internal / External / External (Prior Worker)}
+**Current title:** {Current Job Title at Current Company}
+**Email:** {Email or "—"}
+**Phone:** {Phone or "—"}
+
+## Summary
+{2–3 sentences from resume text: focus, years of experience, key strengths.
+Fall back to Current Job Title + Total Years Experience.}
+
+## CV
+- [CV.md](./CV.md)
+
+## Connected to
+- [[Roles/{Role filename}]] — applied to
+- {[[People/{Hiring manager}]] — hiring manager, if known}
+- {[[People/{Domain lead}]] — domain lead, if known}
+- {Referred-by person, if present}
+
+## Pipeline
+- **{Date Applied}**: Applied via {Source} — Step: {Workday step}
+
+## Skills
+{Agent-aligned standard skill IDs from `bunx fit-pathway skill --list`}
+
+## Education
+{Degrees + Fields of Study}
+
+## Work History
+{All Job Titles + Companies}
+
+## Notes
+{Visa, Eligibility, Relocation, Non-compete, Years experience}
+```
+
+Gender is `—` (Workday exports carry no gender signals).
+
+## Existing-candidate edits
+
+Apply targeted edits to `brief.md` — never rewrite. Set/update `Req`, advance
+`Status` if the Workday step is more advanced, update `Last activity`, append
+`**{Date Applied}**: Applied to {Req ID} — {Title} via {Source}` to Pipeline,
+fill only missing Email/Phone/ Location. Never overwrite richer existing data
+with sparser Workday data.

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

@@ -0,0 +1,56 @@
+# Workday Export Format
+
+Reference for `req-workday`. The export format varies between Workday versions;
+the parse script handles both with header-driven column mapping and dynamic
+header-row detection.
+
+## Sheet 1 — requisition metadata
+
+### Old format (key/value)
+
+| Row | Field                 | Example                                |
+| --- | --------------------- | -------------------------------------- |
+| 1   | Title header          | `4951493 Principal Software Engineer…` |
+| 2   | Recruiting Start Date | `02/10/2026`                           |
+| 3   | Target Hire Date      | `02/10/2026`                           |
+| 4   | Primary Location      | `USA - NY - Headquarters`              |
+| 5   | Hiring Manager Title  | `Hiring Manager`                       |
+| 6   | Hiring Manager        | Name                                   |
+| 7   | Recruiter Title       | `Recruiter`                            |
+| 8   | Recruiter             | Name                                   |
+
+### New format (stage-count summary)
+
+| Row | Field             | Example                                |
+| --- | ----------------- | -------------------------------------- |
+| 1   | Title header      | `4951493 Principal Software Engineer…` |
+| 2   | Active Candidates | `74 of 74`                             |
+| 3   | Active Referrals  | `3 of 3`                               |
+| 4   | Active Internal   | `4 of 4`                               |
+| 7+  | Stage counts      | `56 → Considered`                      |
+
+The new format does not carry hiring manager, recruiter, or location.
+
+## Candidates sheet
+
+Auto-detected:
+
+- **Old format:** 3+ sheets; candidates on the "Candidates" sheet or Sheet3;
+  header at row 3 (index 2); two "Job Application" columns.
+- **New format:** 2 sheets; candidates on Sheet2; header at row 8 (index 7);
+  single "Job Application" column.
+
+Column mapping is header-driven — the parser reads the header row and maps
+columns by name. Columns that vary between exports ("Jobs Applied to", "Referred
+by", "Convenience Task") are handled automatically.
+
+## Name annotations
+
+Names may include parenthetical annotations:
+
+- `(Prior Worker)` → Internal/External = `External (Prior Worker)`.
+- `(Internal)` → Internal/External = `Internal`.
+- No annotation, source contains "Internal" → `Internal`.
+- Otherwise → `External`.
+
+Strip the annotation from the directory name and the brief heading.