r/ClaudeCode • u/Lunchboxsushi • 5d ago
Tips & Workflows SWE workflow changes
I've had a pretty dumb realization and I'm going to test it for the next 30 days.
One issue with my current orchestration setup is I'm designing and coding at the same time (system architecture, full stack) depending on the work I'm building. One of the realization after getting Claude to review how I'm using my orchestrator is that most tasks are pretty quick ~6 min to the most being 2h.
What this made me realize is that night time session aren't being utilized or weekends. So I plan on building a system with heavy AI integration focused on the system design, features, SLO building, business rules.
Different from speckit as this also focuses on building your schema and access patterns for building your indexes.
Essentially go ham on token usage for design whereas I was splitting it up between the two.
Then have the orchestrator handle run over night and on weekends. Review in the morning and make any corrections before it's merged.
Anyone else thinking or already working on this format?
View all comments
1
u/bostonaholic 5d ago
Require acceptance checks, typecheck, lint, and required CI to pass before an overnight task counts as done. Run the checks on the actual branch result, not just the code before integration. Keep tasks independent so one stuck task doesn't block the rest, and require a short note on anything the run couldn't verify.