work-session
Use when starting AI development sessions, resuming interrupted work, managing multi-session projects, or orchestrating work with human checkpoint control (supervised, semi-auto, auto, or unattended modes).
What this skill does
# Work Session Orchestrate AI-assisted development with configurable human control, using ohno for task management via MCP. ## When NOT to Use - **Planning work** — Use `planning` to create epics/stories/tasks before starting sessions - **Quick one-off tasks** — Use `/quick` for simple tasks that don't need the full subagent pipeline - **Revising a plan** — Use `plan-revision` to modify scope, dependencies, or task hierarchy - **Running a spike** — Use `spike` for time-boxed investigation before committing to implementation ## Key Principles - Fresh context per task via subagent dispatch (no context degradation) - Configurable checkpoint control: supervised, semi-auto, auto, or unattended - Smart worktree isolation by task type (feature/bug → worktree, chore/docs → in-place) - Hooks handle lifecycle automatically (sync, commit, tests) - ohno MCP provides session continuity across conversations - Evidence before completion claims (`verification-before-completion`) - Root-cause-first bug handling (`systematic-debugging`) - Explicit branch finish choice: merge, PR, keep, or discard (`finishing-branch`) - Token-aware dispatch: stay inline for tiny work, use focused agents when isolation or parallelism is worth the cost ## Quick Start Checklist 1. Initialize ohno: `npx @stevestomp/ohno-cli init` 2. Get session context: MCP `get_session_context()` 3. Get next task: MCP `get_next_task()` 4. Dispatch subagent for implementation 5. Review results at checkpoints (based on mode) ## Operating Modes | Mode | Task Complete | Story Complete | Epic Complete | |------|--------------|----------------|---------------| | supervised | PAUSE | PAUSE | PAUSE | | semi-auto | log | PAUSE | PAUSE | | auto | skip | log | PAUSE | | unattended | skip | skip | skip | ## References | Reference | Description | |-----------|-------------| | [subagent-dispatch.md](references/subagent-dispatch.md) | Coordinator vs implementer roles, dispatch mechanics | | [session-protocol.md](references/session-protocol.md) | Session start/end checklists, MCP workflow | | [checkpoint-types.md](references/checkpoint-types.md) | PAUSE, REVIEW, NOTIFY checkpoint patterns | | [skill-routing.md](references/skill-routing.md) | Task type to skill mapping | | [operating-modes.md](references/operating-modes.md) | Supervised, semi-auto, auto, unattended details | | [worktree-management.md](references/worktree-management.md) | Setup, completion, merge/PR workflows | | [parallel-execution.md](references/parallel-execution.md) | Parallel Execution: benefits, tradeoffs, dependency handling | | [hook-integration.md](references/hook-integration.md) | Work loop with hooks, mode-specific behavior | | [ohno-integration.md](references/ohno-integration.md) | MCP tools and CLI commands reference | | [error-recovery.md](references/error-recovery.md) | Build failures, blocked tasks | | [approval-policy.md](references/approval-policy.md) | Runtime approval defaults for safe pokayokay automation | | [token-budgeting.md](references/token-budgeting.md) | Token/context budgeting rules for agents, skills, parallelism, and handoffs | | [anti-patterns.md](references/anti-patterns.md) | Common mistakes and fixes | | [bug-fix-pipeline.md](references/bug-fix-pipeline.md) | Agent pipeline for `/fix --thorough` and `/hotfix` commands | | [pre-flight-checks.md](references/pre-flight-checks.md) | Checks run before unattended/headless sessions |
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.