byrobxAI.

///109 Projects OS

The project team

Plans, budgets and watches your client projects, so you see problems while you can still fix them.

BetaWorks end to end. Rough edges get fixed as people use it.

How the team works

  1. Set up a new project from the quote
  2. Plan back from the deadline and build the budget
  3. Prepare each meeting and turn it into decisions and actions
  4. Check budget, risks and team capacity every week
  5. You decide and approve
  6. Review the project when it is done

Who is on the team

  • projectmanagerLead

    Plans, budgets, runs meetings and flags risks. Calculates in code, decides nothing itself.

Every task it can do 12

  • projectsetupSets up a new project folder and task board phases from a quote.
  • projectplanningPlans milestones back from the deadline on real working days, with the critical path.
  • begrotingBuilds a budget per phase: hours times rate, costs, buffer and margin.
  • budgetcheckCompares budget with actual hours and costs, and flags overruns early.
  • dagstartGives a short morning briefing: what waits for you, what needs attention today.
  • meeting-agendaBuilds a meeting agenda with time, owner and desired outcome per point.
  • projectnotulenTurns a meeting transcript into decisions, actions with owners, risks and scope changes.
  • wijzigingsverzoekPrices an extra client request in hours, money and time, with a draft proposal.
  • risicologKeeps the risk log per project: chance, impact, measure and owner.
  • weekstatusWrites a red, orange or green status per project for the team.
  • capaciteitShows who is overloaded or has room in the coming weeks.
  • projectevaluatieCompares plan with reality after a project and lists what to change.

Also included: intake, brain-voorstel, humanizer, anti-ai-slop.

What it does for you

Most projects go over budget slowly, one small request at a time. Projects OS starts each project from the quote: a project folder, the phases in your task board, a planning counted back from the deadline on real working days, and a budget per phase. Two small Python scripts do the maths, so the numbers add up.

During the project it keeps watch. Each morning you get a short briefing. On Monday a red, orange or green status per project and a view of who has too much work. On Friday a budget check. Before a meeting you get an agenda, after it the notes: decisions, actions with an owner and a deadline, new risks.

When a client asks for something extra, it checks the request against the scope and works out what it costs in hours, money and days, with a draft proposal for the extra work. When the project ends, it compares plan with reality and suggests what to change next time.

What you need

  • Claude Code and a paid Claude plan
  • The brain (BX-001), or fill in the brand files with /intake
  • Python 3 for the budget and planning scripts (standard library only)
  • Optional: your task board (ClickUp, monday.com, Asana, Notion, Jira or Linear), calendar, mail, Slack and a meeting recorder such as Fireflies. Time tracking from Toggl, Harvest or Clockify works as a CSV export.

What it never does

It never sends anything, never makes a decision that belongs to someone else and never changes a budget or planning without your OK. Tasks go into your board only after you approve, and it never deletes them.

Also in Operations