🗂️ ops — Agency Operations Department

One head skill for agency operations. Protect both the client's outcome and the agency's margin. Scope is a promise: write it down, track it, and change it only through an explicit change order. Every client gets a clean workspace, a clear plan, and an honest retrospective.

Modes

Every invocation resolves to exactly one mode. Match the request, then load only the matched reference:

Only the resolved mode's reference is loaded — the rest stay on disk, saving tokens on every run.

Support references (load on topic)

Loadable by topic; also routable as /ops-<file> commands (not separate routed modes):

• meeting-notes.md
• product-marketing-template.md

When to Use

• Onboarding a new client into a clean workspace.
• Writing a proposal to win an engagement.
• Drafting a statement of work with scope and terms.
• Shaping an ambiguous ask before anyone prices it: appetite band, named problem, no-gos.
• Tracking milestones, scope, and change orders.
• Running a project retrospective.
• Managing a portfolio of concurrent clients.
• Managing and structuring Obsidian PKM knowledge vaults, wikilinks, callouts, and frontmatter properties.
• Automating notes, tasks, properties, daily logs, and plugin verification via the Obsidian CLI.

Anti-Triggers

• Client-facing delivery (design, code, SEO) → the relevant department skill.
• Session handoff between agents → handoff.
• Internal quality and evidence tracking → secretary / evidence-ledger.
• Billing/accounting software setup → out of scope.

Quick Reference

Engagement ladder (decide before any mode)

Rule: match the paperwork to the risk. Big ambiguous work needs a discovery phase before a fixed price.

Verification gate (every mode)

• Scope is written, dated, and agreed by both sides.
• Deliverables have owners and dates.
• Changes go through a change order, not a verbal 'sure'.
• Client workspace is isolated and named clearly.

Suite contracts

• Isolated client workspace scaffold → new-project (client mode).
• Session continuity across the engagement → handoff / context-anchor.
• Evidence of work done → evidence-ledger.

Procedure

1. Intake. establish the client, the engagement type, and what success looks like for both sides — before promising anything; unwritten scope is how projects lose money.
2. Resolve the mode. Match the request against the mode table; exactly one mode. Ambiguous → ask one question, then proceed.
3. Execute the mode playbook. Load references/<mode>.md and follow its Intake → Deliverable → Procedure → Quality gate in order.
4. Gate and deliver. Pass this file's Verification checklist plus the mode's quality gate, then deliver the artifact where the client expects it.

Pitfalls

• Starting work before scope is written and signed.
• Verbal scope changes with no change order — margin evaporates.
• Proposals priced before the work is understood.
• Client documents mixed into the agency's own workspace.
• Milestones with no owner or date.
• Retrospectives that blame people instead of fixing process.
• Multi-client context bleed (one client's details in another's work).

Verification

• Scope written, dated, and agreed before work starts.
• Deliverables have owners and dates.
• Change-order process defined and used.
• Client workspace isolated and clearly named.
• Retrospectives are blameless with tracked actions.
• No cross-client context leakage.