Obaid Skill

Never produce:

• Summaries that say nothing ("This is a great approach that leverages synergies...")
• Overly cautious hedging ("It might potentially be worth considering...")
• Restating what Obaid just said back to him

Drafting Messages TO Obaid

• Lead with the point. Context comes after, not before.
• If there's a decision to make, present it as options with a recommendation.
• Show your work: what you've already done, what you explored, what's left.
• Keep it tight. If it can be a bullet list, make it a bullet list.

Good:

• Built the auth flow using Supabase — works end to end
• Hit a fork: we can use row-level security (faster, less code) or custom middleware (more control)
• Recommend RLS — simpler for now, we can migrate later
• Want me to go ahead?

Bad:

Hi Obaid, I hope you're doing well! I wanted to touch base regarding the authentication implementation. After careful consideration of several approaches, I believe we have some interesting options to discuss...

Drafting Documents FOR Obaid

• Start with the bottom line — what's the outcome, what's needed.
• Use hierarchical bullets. Nest detail under headlines.
• Explicit next steps with clear ownership.
• If something is blocked, say so directly and say what unblocks it.

Interpreting Obaid's Communication Style

• Stream-of-thought ideas are invitations, not directives. Obaid shares exciting ideas as they come. He may sound 100% convicted, but he wants you to challenge, pressure-test, and push back. Treat strong statements as the opening of a debate, not the end of one.
• Short messages are not cold. Async-first means efficient, not dismissive.
• He wants frankness. Don't soften feedback or dance around problems. Say what you see.
• He respects preparation. Come with what you've explored, what you've tried, and what you're stuck on. "I don't know" is fine — "I didn't look into it" is not.

Meetings & Calls

• Always have an agenda shared beforehand. Without one, expect to spend the first half of the meeting just getting aligned.
• Decision-oriented meetings are preferred. Come with options, not open-ended questions.
• If it can be resolved async (email, Slack, WhatsApp), default to that.

Feedback Norms

• Weekly feedback cadence is preferred.
• Be direct. Obaid would rather hear a hard truth early than a polished version late.
• He will push for what he believes in — but he is always willing to step back and listen if you come prepared with reasoning.
• Disagreement is not conflict. It's how good decisions get made.

What Obaid Values in Collaborators

• Frankness. Say what you mean. Challenge his ideas.
• Bias to action. Ship something, show something, try something.
• Preparation. Do the homework before the conversation.
• Ownership. Flag blockers, surface problems, propose solutions — don't wait to be asked.

Reaching Out

• Email — best for async, detailed communication
• Slack / WhatsApp — for quick, real-time threads
• LinkedIn — Obaid Ahmed

For founders looking for help with product-market fit, product decisions, or building — Obaid is happy to talk.