Manas Hardas

Bitcoin guy, Freedom maximalist, ex @Strike, @bitkeyofficial, @MARA npub1mh4872fvdskyuswvftn5d4p8grjl52z9e2708wsftcup4s5hnecqygjtkr

[Manas Hardas @manashardas]

@saylor What does this even mean?

[Manas Hardas @manashardas]

@Om_Codes_ What he said is exactly right. Why hasn't India produced an Elon? It is not as if we cannot produce someone of his calibre and/or autism.

[Manas Hardas @manashardas]

@RuntimeBRT @ArmoryShield Demo first, then the tech

[Manas Hardas @manashardas]

@markusdd5 The problem isn't Tesla leaving India, the problem is India hasn't produced a Tesla itself. And yes, it is the culture which stops this.

[Manas Hardas @manashardas]

I built a discipline framework to keep dispatched Claude Code agents coherent across a multi-month prod roadmap.

It's called agentwaves.

Most skill collections constrain the dev process inside one feature. agentwaves constrains how agents coordinate across many
sessions. (1/8)

[Manas Hardas @manashardas]

8/8

Composes with Superpowers. Orthogonal to GSD and gstack. MIT-licensed.

Repo + 14-dimension framework comparison + adoption guide:
https://t.co/zgqf1ak2dW

If you've run into multi-agent multi-session dispatch drift, curious how you've handled it.

[Manas Hardas @manashardas]

7/8

How to apply it:

→ New project: clone as .orchestrator/, paste CLAUDE.md.snippet into your CLAUDE.md, kick off with "Run the Session-start ritual."

→ Existing project: same drop-in. Read agents/orchestrator.md first, then retrofit one phase at a time.

[Manas Hardas @manashardas]

6/8

For teams: each engineer runs their own orchestrator session against the same repo.

Coordination happens through shared plans/ artifacts + phase tracking issues + the GitHub project board.

No new tool to roll out — just markdown files and a discipline.

[Manas Hardas @manashardas]

5/8

Every clause traces back to a specific recurring failure mode with a measured token cost.

Not aspirational. The residue of mistakes that hurt enough to encode.

[Manas Hardas @manashardas]

4/8

Cross-session state lives in wave-state.md + a pre-rendered Session Handoff Document. Budget watchdogs (T-A/T-G/T-D), coordination watchdogs (T-M/T-X/T-Y), and a 17-invariant guardrails script catch silent drift at session-close.
No more "agent followed stale memory" bugs.

[Manas Hardas @manashardas]

3/8

The pattern, per phase:
W0 — orchestrator freezes contracts

W0.5 — Backend/Frontend/Infra dispatched in parallel; file GitHub issues
W1 — build loop, one specialist per issue, reviewer-trio per PR
W2 — QA planning + build
W3 — phase close
W3.5 — dogfood real data

[Manas Hardas @manashardas]

2/8

How the Claude Code framework layers differ:
→ Superpowers: TDD + phase gates inside a feature

→ GSD: fresh 200k context per atomic task
→ gstack: a role to think from (CEO, EM, designer)
→ agentwaves: dispatch + lifecycle scaffolding across the whole roadmap

[Manas Hardas @manashardas]

@vitaliidodonov MRR

[Manas Hardas @manashardas]

@iitm_bs Why only for kids who have cleared JEE mains? These courses are offered for free all over the internet! What is so special about IIT-M courses?

[Manas Hardas @manashardas]

@araghougassian BET

[Manas Hardas @manashardas]

@delk @lansing Is it because public school data is basically a black hole? You must have considered integrating with the systems they use (I know there are hundreds of those!), but other than that what is the hardest problem?

[Manas Hardas @manashardas]

@z @alex_frantic I wish token spend between approaches was a part of these conversations because real users care about that a lot.

[Manas Hardas @manashardas]

@OpenAIDevs Build something similar for Claude code to build product in "waves" of contract freezing, defining work writing issues, build, qa and release cycles

https://t.co/15HdGXppzm

[Manas Hardas @manashardas]

@amitkilhor Nahi kar rahe hain kyon ki nahi kar sakte