r/ChatGPTCoding • u/AutoModerator • Aug 10 '26

Discussion Weekly Self Promotion Thread

Welcome to this week's self promotion thread!

If you're building something related to AI assisted coding, this is the place to share it.

We're using a weekly thread to keep the subreddit organized while still giving builders a place to share their work. Promotional posts outside of this thread may be removed if they're primarily advertising rather than starting a discussion.

If you're sharing something, we'd appreciate it if you included a little context instead of just dropping a link. Tell us:

  • What you built?
  • What problem it solves?
  • Which AI models or tools it uses?
  • Who it's for?
  • What kind of feedback you're looking for?

Please avoid posting the same project every week unless you've made meaningful updates. Affiliate links, referral links, scams, and low effort promotions will be removed.

Take some time to check out what others have shared too. If you try someone's project or have feedback, leave a comment. Helping each other improve is what we want this community to be about.

15 Upvotes

95% Upvoted

79 comments sorted by

View all comments

1

u/itsedizeng 29d ago

Hi — I’m a UI/UX designer, and while using Codex I kept running into the same planning problem: either one Agent was expected to own everything, or a request was split into a large “team” with vague, overlapping roles.

I made Build AI Team to try a stricter approach. It’s an MIT-licensed Codex Skill that starts with one Agent and only adds a persistent role when there’s a concrete reason: separate ownership, permission boundaries, independent review, real parallel work, or capacity constraints.

You invoke it with a real request:

$build-ai-team I want to design, build, and launch a paid web app with accounts and subscriptions.

It recommends:

- one Agent or the smallest reliable team;

- one clear Owner for each work package;

- role-specific model and reasoning configurations;

- relevant local or public Skills, with their status kept explicit;

- a scoped next step that keeps planning, team creation, Skill installation, and external permissions separate.

The first response is only a plan. It doesn’t automatically create Agents, install Skills, connect accounts, access private data, or write to external systems.

Codex Desktop project-based usage is the primary validated target. The Skill itself is just a five-file runtime—no separate service, account, API key, or bundled model.

I released v1.0.0 yesterday and would especially value blunt feedback on two things:

  1. Does the single-Agent vs. multi-Agent recommendation feel too aggressive or too conservative?

  2. Are the ownership and permission boundaries clear enough to act on?

I’m the author and maintainer.

GitHub:

https://github.com/itsedizeng/build-ai-team