Skip to content

My desired workflow with multiclaude #272

@martin-purplefish

Description

@martin-purplefish

Not not an issue per se, but just to for discussion (and I know you mentioned you're working on some of this on LinkedIn, figured this was a better place for a more deep discussion.

What I really want to do is work off of an epic level.

The way I see it, my time should ideally be spent doing three things:

  1. Planning out work/deciding what's important
  2. Being the ultimate quality gate for work that gets shipped to production.
  3. Unblocking things that get in the way/clarifying requirements/etc.

One way I could see accomplishing it is like this:

  1. From some external system, I plan out a feature. My two cents is I don't think multiclaude should be responsible for planning, but it should consume a plan.
  2. From there, we create an epic branch for that plan, with feature branches going into this epic branch. That's where the Brownian ratchet mechanism is.
  3. Once all the features for an epic is done, the supervisor says the epic is ready, and CI is green, I want to review it.

I think with that most other things can get handled by better and better agent configs. Already our main "do work" agent essentially dispatches to a number of sub-agents which handles most things through PR and addressing comments.

Separately, since you're just in this world, I'm curious if you have any insights on planning. We've been looking at things like OpenSpec and SpecKit, and also comments like this gastownhall/beads#266 (not specific to beads, just the planning strategy he shares).

And finally... any thoughts on enabling discussions for this repo?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions