Rohit Ghumare

Use when a product or feature idea needs pressure-testing against problem, user, pain, success, and timing.

The English summary is being prepared. Showing the original description.

Use when source-backed project knowledge needs to be created, refreshed, or corrected.

The English summary is being prepared. Showing the original description.

Use when deciding what project context should be remembered, retrieved, updated, or deliberately forgotten.

The English summary is being prepared. Showing the original description.

Use when an engineering plan needs pressure-testing for architecture, complexity, data, risk, and operability.

The English summary is being prepared. Showing the original description.

Use when sources need to be converted into a claim ledger with confidence levels.

The English summary is being prepared. Showing the original description.

Use when raw intent must be captured and routed to the right next state.

The English summary is being prepared. Showing the original description.

Use when repeated wins or failures should become durable memory, wiki, or skill updates.

The English summary is being prepared. Showing the original description.

Use when a product idea needs pressure-testing against alternatives, category, urgency, and distribution.

The English summary is being prepared. Showing the original description.

Use when behavior needs concrete proof before review, merge, or shipment.

The English summary is being prepared. Showing the original description.

Use when uncertainty remains and the minimum useful sequence of questions should be asked.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-brief: after intake, research, and grill have enough signal.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-build: an implementation plan has a selected task and validation method.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-design: a product brief needs ux or interaction design before planning.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-eval: changing Agent Brain behavior or checking quality.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-grill: the idea, brief, design, or plan has unresolved assumptions.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-learn: after repeated success/failure, a tricky fix, or a shipped workflow.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-plan: the brief/design is strong enough to implement.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-research: the decision depends on external evidence or unfamiliar domain context.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-review: after verification or before public/shipping decisions.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-ship: a reviewed artifact is ready for release or publication.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-should-this-exist: before planning any new product, feature, workflow, or automation.

The English summary is being prepared. Showing the original description.

Agent Brain /brain-start: a user starts from a vague request, idea, task, or product ambition.

The English summary is being prepared. Showing the original description.

Use when an agent runtime must choose or verify a /brain-* command route from a user request, handoff, adapter transcript, or stale command catalog.

The English summary is being prepared. Showing the original description.

Use when a design needs pressure-testing for UX, information architecture, states, and accessibility.

The English summary is being prepared. Showing the original description.