dsh-plugin-oh-my-engine

Many teams want to bring Oh My Engine's structured engineering process into their DeepSeek Harness workflows, but OME is deliberately platform-neutral and ships no frontend binding, leaving DSH users without a native integration path. dsh-plugin-oh-my-engine closes that gap by injecting the OME engineering preset as an isolated agent into Web and Desktop profiles. It consumes only OME's public lifecycle API, stores all runtime state in the active DSH Session Event Log, and leaves every other preset—Standard, Code, Minimal, and beyond—completely untouched in tools, commands, and prompts.\n\nThe full Define, Plan, Build, Verify, Review, Ship, and Learn pipeline ships with a hard Plan-approval gate that only the /ome-approve command can pass. The Verify stage demands test evidence that references a successful prior tool call within the same Session, and the Learn phase records OME Memory so the entire lifecycle remains traceable in the Session event log. Subagents inherit context but are restricted to calling ome_status, while editing, commands, sandboxing, approvals, and cancellation stay firmly with DSH native tools, keeping role boundaries crisp and predictable.\n\nIt is built for solo developers and small teams already on DeepSeek Harness who value an auditable engineering loop: every build is gated by explicit approval, every verification is backed by traceable evidence, and the whole lifecycle is logged for post-hoc review—all with zero intrusion into the rest of your profile configuration.