Announcing Greenroom: A private place to prepare your public commits

Greenroom: a private space to prepare for making public commits. Split panel showing the Green Room (<project>-private, holding superpowers docs and PRDs, design RFCs and plans, working notes and research) beside the Stage (<project>-public, holding polished production code, clean commits and PRs, and public releases), joined by one entry point at AGENTS.md.

I have been using Jesse Vincent’s incredible Superpowers actively for months now, and it is what really unlocked agentic coding for me. I’ve built my own agentic harnesses, which I’ve been using to help me contribute to great open source projects like agentsview, msgvault, and maclocal-api.

Doing this well means writing and iterating on a lot of docs, tests, etc. While this is critical context for me and for my agents… I think everyone is still figuring out where all this new context belongs. At the same time, the contribution bar has risen dramatically. Open source maintainers expect great communication, small, clear commits, with finely refined-and-polished code. To me, checking all of my work, my design docs, test plans, and notes on my own thinking into a public repo feels… weirdly vulnerable and private.

It reminds me of stepping on to a stage to perform, and I only want to do that when I am ready. In the theatre and conferences, a Green Room is the private space where performers prepare to take the stage. So I made Greenroom: A private place to prepare your public commits

Greenroom creates and maintains two (or more) repos under a top level project folder and then manages them carefully. For my open source forks and contributions I have a repo-public (my fork), repo-private (my Greenroom directory). Sometimes I have several forks I’m managing, or pull in dependencies, etc.

Install greenroom in claude code

/plugin marketplace add jesserobbins/greenroom
/plugin install greenroom@jesserobbins

Or with skills.sh for everything else

The standalone skill copies Greenroom straight into your project and works on Claude Code, Codex, Cursor, and the other 70-plus agents that skills.sh supports:

npx skills add jesserobbins/greenroom

Greenroom re-organizes your project in this layout

~/src/<project>/                 # parent folder, not a git repo
├── AGENTS.md                   # orientation for any agent launched here
├── <project>-public/           # public code repo (the thing on GitHub: the stage)
└── <project>-private/          # private notes repo (a separate private GitHub repo: the Greenroom)
    ├── AGENTS.md  # private-side orientation
    ├── docs/      # design docs
    ├── notes/     # dated working notes
    ├── drafts/    # PR/issue/blog drafts
    ├── reviews/   # private notes on PRs
    └── research/  # transcripts, links, experiments

I expect most people will use Greenroom to contribute to other people’s projects. This lets you build/iterate/refine/polish in private while keeping your notes until you are ready to push to public and issue that awesome PR. It is also great if you are the maintainer!

I think in the end we will see maintainers want design docs and plans along with high quality PR submissions, and everyone is still figuring that out.

Give it a try and let me know if it helps! github.com/jesserobbins/greenroom.

#ai #developer-tools #open-source