Operations
3 signed skills and professions from 2 vendors, with 0 videos and 2 articles. Read any page free; a free account downloads them.
Profession3 imagesDelivery Manager
@di-atomic · Operations
Delivery Manager — a hireable role that owns the propagate stage of any launch. Seeds ONE launch card whose fields are the shared state, coordinates the surface skills (blog, changelog, listing, marketplace, docs) to shipped so the hero renders once and every surface reuses it, holds the publish gate, describes only the real release (never fabricates), and hands the evergreen surfaces (social, SEO) to a standing agent on a cadence. 17 links, 4 workflows, and the delivery-manager guild.
Profession4 imagesClient Strategist
@di-atomic · Operations
Client Strategist — a hireable role that owns the proactive half of the client relationship, the half that runs whether or not the client writes in. It reads each account's communication record over a bounded window, compares it against that account's own stored baselines rather than against a notion of warmth, and scores two independent axes: delivery health across five verdicts — including two that say plainly "I could not see this" — and competitive position across four, so an account delivering above contract while a rival bids for its core deliverable is not filed as healthy. It scores drift before it becomes churn, drafts the response in the owner's voice and queues it for approval, and asks quarterly whether the retainer still fits what is delivered. Its defining discipline is that absence is a finding: an account it could not read is declared unmeasured, never healthy, and an account whose room it cannot see is position unknown, never secure. 16 links, 5 workflows, and the client-strategist guild.
Agent Ops Skills
@spideriq · Operations
A verified agent lifecycle for any software project, and an installer that adopts it into one. Worker sessions start, test and ship a board card; an orchestrator drains the deploy column, merges, classifies, builds or reuses an image, pins, swaps, smokes and writes back to the board; release, deploy, verify and launch procedures and a planner method sit beside them. Every command keeps a LEDGER: a script records each step's measurement and refuses the report until every step is PASS or N/A, with CANNOT never counted as a pass. The commands render from templates plus ONE project profile and project notes, so the method stays portable and the facts stay in one file. The installer DRAFTS that profile from a target repository, leaves every field it cannot read MISSING rather than defaulted, MEASURES each one with a probe AND a control that could have gone the other way, and refuses to render a slot nobody measured.