Engineering OS, SME Edition

01You build the product. Your agents are the team.

Coding agents are fast, and they will also paste an API key into a config file, push straight to main, edit a failing test so it passes, and announce "done" with a red build. Writing more prompt text doesn't fix that. What fixes it is rules the agent can't skip.

Engineering OS turns any repo, new or already in production, into a governed AI-native workflow: intent.md → spec.md → plan.md → code → PR.

Already using GitHub Spec Kit? Engineering OS works alongside it: Spec Kit gives you the spec workflow, Engineering OS adds the enforcement, the store path and the legal pack.

02Enforced by a hook, a test or CI, not a prompt

• No secret leaves the laptop

  API keys, private keys, .env and keystore files are blocked when the agent writes them, blocked again at git commit, and scanned in CI.

• The AI doesn't merge to main

  Pushes to main are blocked in the agent and in git pre-push. Every change arrives as a PR a reviewer subagent has already checked.

• "Done" means the verify gate is green

  Your lint, tests and build plus the framework checks. The agent can't end its turn while the gate is red, and CI runs the same gate.

• To the store, legally

  Internal test builds through Firebase App Distribution, Google Play including the 12-tester closed test, App Store via TestFlight, plus a legal pack.

03What's inside

• /init-sdlc sets up the framework in a new repo in about 15 minutes; /init-sdlc-with-exists-source does the same for a running codebase without changing its behavior.
• The sdlc skill drives intent → spec → plan → code → PR, one approval at a time, with verifier and pr-reviewer subagents.
• Guard hooks for secrets, key files, env files, push to main, manual deploys and repo deletion. Edits to the gate itself ask you first.
• scripts/verify.sh with stack checks for Flutter, Android/KMP, iOS, Node, Go, Python and notebooks; CI for GitHub Actions and GitLab CI.
• The eos mobile wizard for non-technical builders: signs you in to GitHub and Firebase, registers your apps, invites testers and moves the Firebase key straight into GitHub Secrets.
• Legal without the research: privacy policy and terms templates, GDPR, CCPA, COPPA and Vietnam data law, store policies, payments, refunds and tax (a checklist, not legal advice).
• The eos CLI (apply, switch, remove, status, doctor) across Claude Code, Codex, Antigravity, Gemini CLI, Grok Build and OpenCode.

04After-sale support, long term

• 12-tester launch service for Google Play: new personal Play accounts need 12 testers for 14 days before production. When your app is ready, the author's tester group of real people joins your closed test (one app per license). It gets you to the point where you can apply for production; Google makes the approval decision.
• 12 months of free updates: new harness versions, new guard protections, store and legal rule changes.
• Email help within 2 business days.

05Small team plan adds

• Team rollout kit: a 5-day rollout plan, multi-repo setup with branch protection, a day-one onboarding checklist, CODEOWNERS, REVIEW.md and decision templates, and a 12-slide team intro deck.
• Priority support: replies within 1 business day, plus a setup review of up to 10 repos from your eos doctor output.

06Tested like a product, not a prompt pack

287 automated selftest scenarios ship in the zip, and you can run them yourself. They build every project type and stack in a temp directory, attack the hooks, feed each harness's real hook payloads through the adapters, and check that the git backstop holds.

Requirements

git, jq, bash (macOS, Linux or WSL), and at least one of the supported agents.