Opskeep

Opskeep routes the work around the work.

Choose one primary destination, hand off to that skill or reference, return sources, owners, next actions, and TBD for unknowns.

Workflow

1. Classify the request. Decide whether this is business work, managing Opskeep, using a Opskeep tool, explicit help/menu, or not a Opskeep task.
2. Pick one primary destination. Use the command matrix, routing rules, and tie-breakers. If no command is present, route by conversation context when safe.
3. Load the destination. Prefer the standalone skill named in the matrix. Use router references only for help/menu details.
4. Check route-specific gotchas. Use this router's gotchas plus the destination skill's rules before output with external-tool risk or owner-facing consequences.
5. Use connectors only when needed. For setup/status, route to opskeep-manage. For live app reads/writes, route to opskeep-tools/Composio with discovery and schema checks.
6. Run the workflow. Preserve required inputs, approval gates, provenance, and output contract. Use TBD for missing facts.
7. Return the smallest useful next step. Include secondary follow-ups only when useful, unless user asks for a chain.
8. Update notice (once a day, after the answer). Follow references/update-check.md: if a newer Opskeep version exists, end with its plain-language notice and offer to install it. Never delay or replace the user's answer for it.

No command? Use conversation context to choose the best destination. Show the menu only for explicit help/menu, sparse context, or unsafe routing. Not service ops, Opskeep setup/config, or a Opskeep utility? Do not force Opskeep.

Command Matrix

Routing Rules

1. Known command/alias after Opskeep -> matching route.
2. Exact help or menu -> show command menu.
3. No command, missing command, or unknown command with clear context -> route by intent instead of showing menu.
4. Business lane intent wins for business work. Tool/setup intent wins only when the user asks to operate Opskeep or use a standalone utility.
5. opskeep-manage owns Opskeep onboarding, business profile, preferences, company brain, connected tools, automations, triggers, and recurring loops.
6. opskeep-tools owns standalone hosted utilities and exact utility jobs: audio briefs, voice huddles, follow-up reminders, time tracking, and Composio-backed tool access.
7. Generic client follow-up stays keep clients or deliver work. One-shot self-email reminders go through opskeep-tools to opskeep-follow-up-reminders.
8. One-time status/update work stays deliver work. Event-driven setup goes through opskeep-manage to opskeep-triggers. Recurring/repeating reminder setup (daily/weekly/monthly cadence) goes through opskeep-manage directly.
9. Live external app access or writes go through opskeep-tools/Composio discovery/schema rules. Never guess slugs.
10. Multiple matches -> one primary destination plus secondary follow-ups, unless user asks for chain.
11. Handoff checks -> return Objective, Source Check or Tool Access Check, Current Signal, actions with owner/date/evidence, TBD gaps, and next lane follow-ups. Do not execute multiple lanes unless asked.
12. Sparse or unsafe route -> help/menu plus one clarifying question only if needed.
13. Retail/shop or hospitality/venue business-model intent (stock up, reorder, low stock, SKU, till, markdown or prep list, reservation, table, waitlist, nightly close-out) routes to the matching installed vertical pack router: opskeep-retail or opskeep-hospitality. Accounting-practice client work (a client's books, reconciliations, records requests, filing deadlines, management accounts, engagement letters) routes to opskeep-accounting. That pack's lanes own its loop end-to-end; do not flatten shop, venue or client-books work into core service lanes. The accounting practice's own invoices, WIP, retainers and aged debtors stay in core get paid.
14. Vertical packs are separate installs staged under verticals/<pack>/skills/. If the matching vertical router is not installed, return the clone-and-copy install path and use TBD for the target skill rather than inventing or running opskeep-retail-* / opskeep-hospitality-* / opskeep-accounting-* skills as if they were present.
15. Agent-manager bookkeeping intent (the user's clients' AI API keys, top-ups, credit balances, or what their agents use) routes to opskeep-manage-client-keys. Per-client money still stays in get paid, and live external app writes stay in composio.
16. Starting something new to build (an app, website, dashboard, internal tool, store or major redesign) with no approved design on record routes to opskeep-project-gate first (the free lite version or the full Opskeep Pro version, whichever is installed). It owns the problem, the bet and the direction; it never authorises implementation. After it is approved, opskeep-elliot-design runs the security gate. Changing a foundational decision on an approved gate ("make it mobile-first") also goes back to opskeep-project-gate.

Tie-Breakers

• status -> deliver work, unless automation/tool connection setup/status.
• triage -> deliver work for tickets/intake, unless triaging route choice.
• budget -> get paid for burn, forecast, variance, margin, invoice, change-control health. define work for new baseline. Ambiguous? Ask one short question.
• brief alone -> define work for working brief or deliver work for status brief, not audio.
• follow up with client -> keep clients, unless self-email reminder requested.
• plan -> define work, not another PM skill; planning a new app, site or redesign to be built -> opskeep-project-gate.
• scope -> define work for a client engagement's scope; opskeep-project-gate for what a new product should be and how it looks before building.
• monitor -> deliver work, unless money/relationship wording dominates.
• stakeholder map/setup/decision authority -> define work; relationship health/check-ins/retention -> keep clients.
• company brain -> opskeep-manage for setup/config/access; improve operations for ongoing process learning.
• client portal -> define work for setup, deliver work for active maintenance, improve operations for reusable template.
• weekly client update -> deliver work; recurring update automation -> opskeep-manage.
• change control -> get paid only when money/billable/margin/budget/invoice impact dominates. Scope/delivery changes stay define work or deliver work.
• video/YouTube link/transcript -> improve operations when the goal is a reusable SOP/process doc. opskeep-tools to opskeep-audio-brief only when the user explicitly wants a listenable/audio brief instead.
• Reddit/social post -> get work when the goal is researching a topic to draft new content. keep clients for a testimonial/review-style social ask tied to a specific client relationship instead.
• reconcile/reconciliation -> opskeep-accounting when it's a client's bank or ledger; get paid when it's matching payments received against the business's own invoices; opskeep-retail for a shop till.
• invoice/who owes us/aged debtors/WIP/retainer -> get paid, even for an accounting practice.
• credit(s)/top up/usage/api key -> opskeep-manage-client-keys when the subject is a client's AI budget or installed keys. get paid when the wording is about invoicing, payments, or margin.

References

• Help/menu: load references/help-menu.md only for explicit help/menu, sparse context, or unsafe routing; include decision stub: next action, owner, date, evidence; use TBD when missing.
• Utility workflows: route through opskeep-tools or opskeep-manage, then named standalone skill.
• User-facing reports/updates/escalations/handoffs: use references/communication-style.md.
• Lane workflows: load the standalone lane skill. The lane skill owns its references and examples.
• Connectors: use opskeep-manage for connection setup/status and opskeep-tools/Composio for live app reads/writes.

Gotchas

• Do not route generic coding, writing, or research into Opskeep.
• Do not treat opskeep-retail, opskeep-hospitality or opskeep-accounting as installed unless the user's environment actually has them (they are separate packs). Shop/venue work stays out of core service lanes, and the install path is returned when the pack is missing.
• Do not present Opskeep as an acronym.
• Do not mention old public pm-* skills as commands or installation targets.
• Do not edit/copy internals of opskeep-audio-brief, opskeep-huddle-beta, opskeep-follow-up-reminders, opskeep-time-tracking, opskeep-expense-tracking, opskeep-escalate-to-owner, opskeep-triggers, or composio; standalone skills own them.
• Do not weaken confirmation gates for triggers, reminders, Composio writes, huddles, audio publishing, or time-record writes.
• Do not invent owners, due dates, source facts, external-app slugs, invoices, payments, or project decisions. Use TBD for unknowns.