Procurement and operations by day, internal tools and agentic systems by evening. Two practices that decided to be one role. The work below shows up specific, attributable, and mostly shipped.
Three vectors, one practice. Each one would be a job; together they're the role most teams currently have to staff with three hires.
I run sourcing and variance review at scale for a large residential community in the northeast. I write the SOPs that hold up under audit, manage union dynamics, and present the variance dossier to the Finance Committee monthly. Operations work, executed in the open.
Evenings I ship: a solar-investment dashboard for trustees on Vercel, a work-order portal for residents on Microsoft 365, contract-amendment tooling, design-token export pipelines. Vanilla stack where it earns its keep, framework where it doesn't.
I direct Claude Code the way a senior engineer directs juniors: with structure, taste, and accountability. Hooks for safety, skills for verbs, slash-commands for rituals, an MCP-served knowledge base for memory. Plan first, execute clean.
The cases below are anonymized at the employer level; the work is mine. If a case raises a question I'd rather answer in person, that's the point.
WO-2418
Carpentry · porch railing
In progress
WO-2401
Plumbing · main shut-off
Scheduled
WO-2376
Roofing · flashing repair
Closed
$ npm run build:css ✓ tailwind ............ 38 KB → 12 KB ✓ tokens .............. dtcg + json-tailwind ✓ fonts ............... 184 KB · woff2 · latin ✓ pages ............... 1 $ vercel --prod 🟢 deployed · 200 ms cached
Specific tools, specific reasons. The point of naming is so a peer can argue with the choices, and so a hiring manager can tell whether the practice is real.
Six hooks do small, specific work the model shouldn't have to remember. block_secrets and block_dangerous_bash draw the safety line. format_on_edit and typecheck_on_stop keep the diff honest. test_touched runs the right tests, no more. handoff_inject threads context between sessions so the next one starts where the last one left off.
block_secretsblock_dangerous_bashformat_on_edittest_touchedtypecheck_on_stophandoff_inject
/wrap closes a session: lessons, decisions, project state. /wrap-add appends after the fact. /project-history reads the long arc back. The store is Postgres behind an MCP server I run locally; the next session starts knowing the last one's shape, not its bytes.
/wrap/wrap-add/project-historyopen-brain · MCP
Skills are the things I want to be one keystroke away. /prd, /spec, /ux for the planning trio. /wrap and /q for the daily rituals. Office-suite skills (xlsx, docx, pptx) for the materials that still travel by attachment. A SessionStart hook quietly invokes the Hemingway skill at boot, so the voice is in place before the first paragraph.
/prd/spec/ux/wrap/qhemingway
Every non-trivial change starts in Plan mode. The plan goes to disk before any tool fires. Copy is read aloud at one-times speed before deploy; if a sentence trips the tongue, it gets cut. Em dashes are banned in user-facing copy. Pollen, Willow, Fuchsia are reserved by role and never used as decoration.
~/.claude/ ├── skills/ 13 entries; verbs I want a keystroke away ├── commands/ 8 entries; slash-commands and rituals ├── hooks/ 6 entries; safety, formatting, handoff ├── projects/ project-scoped context, plans, logs └── plans/ plan-mode artifacts, dated
Procurement-as-software, agent-driven internal tools, and the small idea you have on a Tuesday that survives Wednesday. New ones land here as they earn the room.
Three threads at once. The first is the variance dossier: ten months of architectural-change decisions, reduced from a binder to a queryable Dataverse table the Finance Committee can sort by quarter. The second is a residents-side roll-up of the work-order portal: a per-building view of ticket age, so the property managers can argue from the same numbers I do.
The third is the meta one. I'm treating my agentic toolchain the way I treat the M365 stack at work, as plumbing that should be visible, named, and replaceable. A skill I write today should be legible to a peer next year. A hook should fail loudly when it disagrees. The discipline is the same discipline procurement teaches: write down what you bought, why, and at what price.
■ more to come
An essay arguing that an RFP is a build configuration, a contract amendment is a migration, and the variance memo is a release note. In drafts.
“Editorial-grade. Long-form, deliberate, warm-restrained.”
From the design system header.