goldBug
goldBug Project OS icon
goldBug Project OS
RULES FOR WORKING WITH AI AGENTSPUBLIC

goldBug Project OS is how I work with AI collaborators without losing the thread. It is not an app and not a second project-management tool: it is a repository of Markdown — shared agent instructions, a project lifecycle, playbooks for executing and reviewing a task, and the template files every product repository starts from. Every project on this page runs on it, including this site. The public repository is a sanitized snapshot of the private one; the rules are the product.

DOCUMENTATION REPOSITORY · NOTHING TO INSTALL
ScreensSWIPE →
REPOSITORY
REPOSITORY
PLAYBOOKS
PLAYBOOKS
REVIEW PLAYBOOK
REVIEW PLAYBOOK
PR TEMPLATE
PR TEMPLATE

Why I built it

Working with several agents at once — Claude, Codex, a cloud session, a local one — goes wrong in predictable ways: an agent fixes something nobody asked for, two agents edit the same file, a decision gets "corrected" because nobody wrote down why it was made. The OS is the written answer to each of those: one issue per outcome, one branch per issue, a draft PR with its own validation table, a review by an agent that did not write the code, and a decisions file that explains the choices that would otherwise look like accidents. I open-sourced it because the rules are more useful than any single project built on them.

How it works

  1. 01I approve an outcome, in one sentence.
  2. 02An agent turns it into a bounded GitHub issue with acceptance criteria and a stop-loss.
  3. 03The agent implements on its own branch and opens a draft PR with a validation table.
  4. 04A different agent reviews the task, the diff and the evidence, and posts findings.
  5. 05I resolve the choices that matter and merge.
  6. 06Reusable lessons go back into the OS through a separate pull request.

Built with

MARKDOWNGITHUB ISSUES & PULL REQUESTSGITHUB ACTIONSPYTHONBASHJQ

Roadmap

  • Rules, playbooks and templates in one versioned repository — done
  • Configurable profile so other maintainers can adopt it — done
  • Sanitized public snapshot — done
  • Mascot and README refresh in the public repository

Known limitations

  • —Written for one maintainer working with a few agents; it is not a general project-management framework and does not try to be.
  • —The public repository is a snapshot: the private project registry and the pilot profile stay out of it.
  • —There is no UI and there will not be one — the GitHub repository is the whole product.