Business & Operations

Work Mesh Live — automatic presence via hq mesh daemon; context reconcile/organize; manual session task-status, blocked, and note only.

Take an idea all the way to a finished deliverable in one command — capture it, research and compare approaches, generate the PRD, then execute every story to the actual work product (code, artwork, documents), continuously and without pausing. Recommended answers are taken automatically and recorded in the decision ledger; --gated pauses at human decisions instead; --plan-only stops at the execution-ready PRD. Use when the user says "/orchestrate", "take this idea to done", "make this end to...

Scaffold a new HQ company AND optionally take it all the way to operational — business-discovery interview, seeded knowledge/workers/skills/projects, brand design packs (generated from website/PDF/Drive and bound to deploys via policy), connected integrations, org groups + ACL rules, teammate invites, and optional cloud agents.

Provision a fleet agent end-to-end — identity, membership, vault join, secrets, file access, MCP/runtime bootstrap, mission brief, and a verified capability probe. Use when standing up a new HQ agent (Slack bot, reporting agent, ops agent) or when an existing agent reports it is blocked on access.

Inspect or change HQ vault ACLs, grants, and shared prefixes.

Turn a resolved ticket into a help-center article, draft a known-issue status page when something breaks, send personalized 'you asked, we shipped' notes to the customers who requested a feature, or flag stale articles that need a refresh after a product change. Pick the flavor and get a publish-ready draft grounded in real conversations and your voice.

Update the rules that decide how incoming tickets get sorted and where they go. Change what counts as a bug versus a feature request, point bugs at a new tracker, update who approves refunds, add a new category, or adjust VIP routing. Every triage after the update automatically follows the new rules.

Hand me a new ticket and I sort it for you. I read the message, figure out what it is (bug, how-to, billing, feature request), check if the customer is a VIP, assign a priority based on your routing rules, and slot it into your queue so you know exactly what needs attention and how fast.

Every time you tell a customer you'll do something by a certain date, I write it down with a deadline so it doesn't slip. I pull the promise straight from your reply, parse the due date, and link it to the thread. These show up in your morning brief automatically, so nothing falls through the cracks.

Tell me the basics about your product, your customers, and how you handle support so I can give you better help. I ask a few quick questions about your product, response-time targets, VIP list, routing rules, and known gotchas. You only need to do this once, and I keep it updated as things change.

Get a structured readout of how support is going. A weekly rollup that covers every domain with volume, top themes, overdue promises, and churn flags opened. A help-center digest that surfaces ticket themes, request velocity, and the single most useful article to write next. Or a per-account review that maps wins, shipped requests, open friction, and next moves so you walk into the call prepared.

Give me a customer name and pick what you need: a dossier with their plan, history, and open items; a full timeline of every interaction; a health score (green/yellow/red) with the three signals driving it; or a churn-risk check that tells you if they're slipping and what to do about it. One customer, four angles.

Spot something in a ticket that's bigger than the ticket itself and I file it properly. A bug report gets logged with repro steps and severity so engineering can act on it. A feature request gets attributed to the customer who asked. And if I see the same question come up three or more times without a help article, I flag the docs gap and offer to write one.

Look at what your customers keep asking about and figure out where your help center is falling short. Ranks the gaps by how many people hit them and how valuable those customers are, gives you the top three with the actual tickets behind each one, and offers to draft the articles right there.

Tell me which conversation and I write your reply. I pull up the customer's history, read your past messages to match your voice, and draft something that actually addresses what they asked, whether it's a bug, a how-to, or a billing question. I never send it and I never promise a date you haven't approved.

Draft the messages that move customers through your lifecycle. A welcome series that walks new signups to their first win across five touches, a 90/60/30-day renewal sequence grounded in what the account actually achieved, a one-off expansion nudge when usage data shows someone hitting a ceiling, or a save message when a customer signals they want to leave. Every draft references real account data and your actual policies, nothing invented.

Get a quick read on your support inbox. Pick what you need: a morning brief that ranks the 5-10 tickets that actually need you today, an overdue check that flags anything about to miss response-time targets or already past due, or a stale-threads sweep that catches conversations you dropped. I scan, rank, and tell you where to start.

Point me at a customer conversation and I give you the short version: where things stand, what you promised, and what the customer is waiting for. Three bullets instead of re-reading a 20-message thread. Especially useful before you draft a reply on something that's been sitting.

Pull your recent customer replies from your connected inbox, read how you actually write, and distill it into a voice profile that every future draft matches. Catches your greeting style, sentence rhythm, sign-off, favorite phrases, and the corporate fluff you never use. After this runs, every reply, article, and lifecycle message sounds like you wrote it.

Draft the outreach you need: a grounded cold email, a sixty-second cold-call script, a post-call follow-up, an inbound reply, a renewal note, or a churn-save email. Every draft is voice-matched to your sent inbox, anchored in your playbook, and stays in a file until you copy and send.

Draft a one-page proposal grounded in the deal: their verbatim problem statement, your proposed approach, scope (in and out), pricing within your playbook's stance, terms, success metrics, timeline, and next step. Anything outside your pricing non-negotiables gets flagged for your approval, never silently committed.

Build a mutual action plan with the prospect: a shared timeline across procurement, security review, budget approval, and legal - with owners (yours and theirs) and dated milestones. Top three risks and any unknown stakeholder surfaced explicitly so you know what to learn on the next call.

Tell me the basics about your company, your ideal customer, your pricing stance, deal stages, and how you handle objections so I can give you better sales help. I ask a few quick questions and write the playbook every other skill reads first. You only need to do this once, and I keep it updated as things change.

Score what you need scored. Pick the subject: every un-scored lead against your ideal customer profile, a single lead's fit and angle, every open deal on health drivers, or every customer's color. I name the top two drivers per row so nothing is a black-box number.