Open-source agent OS for Claude Code that puts you in Builder Mode — and keeps you there for the whole life of a product. Claude Code setup that builds, launches, and learns. Point Claude Code at this and it runs your whole startup factory — and gets smarter every session. Works with Cursor, Codex & Windsurf too.
Run the full engineering cycle autonomously end-to-end — spec → plan → build → test → review → ship — making reasonable calls without stopping at every gate. Use /full-cycle instead when the user wants to approve each gate; use /goal instead when there's a measurable objective to converge on.
Search the Hamzaish brain — learnings, decisions, playbooks, product docs. Use for "what did we decide about X" / "have we seen this before" recall, or before re-deriving something. Returns ranked citations with snippets.
Orchestrate the full engineering cycle — setup → spec → plan → test → build → review → ship — pausing at each gate for approval. Use /auto instead when the user says go/just-do-it (no gates); use /goal instead when converging on a measurable objective.
Pursue a measurable objective autonomously — score against a rubric, fix the biggest gap, verify, log every run, and stop only when a fresh-eyes agent confirms the goal is met (or the run budget is spent). Use /auto instead for a feature build with no numeric target; use /write-a-goal first if the objective isn't…
Momentum router. Default is BUILD — routes straight to the full-cycle build engine. Strategy rails (idea/pricing/GTM) and stage-resume are opt-in side doors, never a toll. Skip is available at every step.
Run the impact-scored learning loop at a major-cycle boundary — gather the cycle's candidate learnings, score them with the rubric, promote the top few into guardrails, and append a changelog line.
One-command repo ship — branch → commit → PR → wait for CI → squash-merge → sync local. The safe GitHub flow, hidden behind one step, narrated in plain English. For shipping a change to a repo's main; NOT a product production deploy (that's /ship).
Review the auto-captured learning queue and hand survivors to the brain (distilled, never pasted). The human gate between automatic capture and /learn-loop.
Cut the next public release at a major-cycle boundary — pick the next semver tag, assemble notes from meta/changelog.md, create an annotated tag + GitHub Release, and mark it latest.
Fast security baseline audit of a product — tracked secrets, unpinned/vulnerable GitHub Actions, workflow permission scope, untrusted-input triggers, MCP-config surface, and an RLS reminder. Add --live to also check the RUNNING system for drift (live RLS status, storage-bucket visibility, Security Advisors, preview…
Scaffold or refresh a project's Claude Code file structure — CLAUDE.md, path-scoped rules, docs, gitignored personal overrides, and a starter /ship command.
Promote reviewed commit(s) from the working branch to the product's production branch and push — the single deploy action. Auto-commit wip snapshots stay on the working branch and never reach production. For deploying a PRODUCT to production; use /pr instead when shipping a change to a repo's main branch.
The gate an idea must pass before it earns a validation attempt — six items that make it TESTABLE, not "good". Fills products/ /validation/idea-gate.md and is checked by bun run check-idea-gate .
★not rated 8 3d agoA53 tokens
AGPL-3.0
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: