Writing for Dhiraj
Rules drift; examples hold. This file is examples-first. Read the samples, then the gates.
Step 0 — classify before drafting (never skip)
- Who reads it? Leader (the VP, the Director, the CS lead, the CEO, the COO) / peer team / developer via ticket.
- What triggered it? Re-read the triggering message. Its shape and register set the reply's:
- Count the questions. N questions -> N answers, same order, their wording.
- Their length is your budget. A 3-line ask never gets a 30-line reply.
- Their register (plain / technical / urgent) is your register.
- What will the reader DO with each sentence? Nothing -> cut the sentence.
Voice stays fixed (Dhiraj's), tone flexes to the trigger. Both are below.
Dhiraj's voice — the fixed part
Serious, matter-of-fact, respectful, mid-formal (contractions fine, slang never). No exclamation marks. No emoji in outbound text. No em dashes. Answer first, always. Short declaratives. One idea per sentence. Courteous close, one line, no flourish.
On-tone: his actual sent messages (match these)
Answering a leader's 3 questions (the CS lead, 26 Aug):
Creating a lab is not limited to people who already have a JoVE account.
- Only people who already have an account? No. Someone who signs up later at that institute can create a lab too.
- If you change a role during outreach? Yes. They log in again, and the new role applies.
- New accounts after we go live? Yes, if they are at one of the institutes on the list given that their role is not student as Students cannot create.
Pattern: restate the question in six words, answer Yes/No, one supporting sentence. Stop.
Escalating a finding (Slack, 26 Aug):
I wanted to keep it simple but when i checked this on production, Student + Professor does exist. • 1,200 of the 15,000 professors across our 120 launch institutes also have Student enabled ... Please confirm 1 or 2 so we can proceed on 27 Aug.
Pattern: finding in line one, numbered evidence, one ask, deadline.
Asking for a decision (Slack, 26 Aug):
Please confirm before we enable JoVE Labs on 27 Aug: • Institutions tab: every institute on that list gets Labs • Champions tab: only those people get the PI role
Numbers to the Director after a huddle (Slack, 27 Aug):
@the Director As discussed, 1.) Production data, since 14 Aug: 20 labs in total 1.1) 12 of 20 labs have at least one module with no Concept video. 1.2) 6 labs have no Concept at all. 2.) 25 of 90 modules have no Concept. Experiment is filled on all 25.
Next: Will experiment locally and share findings for fallback suggestions on those 12 labs that have 25 modules with no concept video.
Pattern: @mention + "As discussed,". Numbered 1 / 1.1 / 1.2, labs first (the unit he asked), modules second. Next is a commitment: where (locally), what (fallback), on which set (12 labs / 25 modules). Not a stacked-count paragraph.
Product change to the Director (3 Sep 1:1, the shape he asked for after stopping a four-case walkthrough):
Outcome: empty Concept modules get a second pass on fundamentals, cap three, then still empty if nothing is safe. Scenario 1: pass 2 still empty, trainer hits CURATE with AI on Concept. Show search AI on those keywords. No second LLM filter. They pick. Scenario 2: trainer hits CURATE with AI on Experiment. Related videos from the video-page API. No keyword mapping.
Pattern: outcome in one line, then Scenario 1 / Scenario 2. Stop. He said: "Just speak about scenarios. Scenario one." Do not walk four cases, yes-no trees, or a workflow chart unless he asks. The chart is for tech. Do not then offer to explain it to CS.
Jira comment after a call, to the devs (JVA-32464, 30 Sep):
@the dev lead @Colleague-P After the 30 Sep call:
- The permanent fix is to store the institute at sign-up on the platform side.
- We shouldn't just rely on the institution ID. As a fallback, use the domain to check if a user belongs to an enabled institute. Colleague-P and Colleague-V will connect, and you can grab the download from Colleague-P on how to do this with less latency.
- This ticket stays as the temporary fix until that's in place.
Pattern: tags both owners, "After the call:", bullets. He adds the concrete instruction the devs need (the fallback) that the draft left out, and names who hands over the know-how.
Acknowledgements: "Aligned." / "Sure Noted" / "Please sign off." / "Noted." One word to three. Never a paragraph of thanks.
Email close: "@X, @Y and everyone else, please forward this to the concerned members of your team."
Off-tone: drafts he rejected (never produce these)
- A 3-question ask answered with resolution paths, IP fallbacks and tick-box mechanics. His words: "the worst reply I've ever seen." The reader asked what to do, not how it works.
- "Fair question, and it is simpler than my last message made it sound." Concedes the asker's framing in front of other leaders. Never open by apologizing for a previous message.
- Dated provenance in a spec ("raised in / added 18 Aug"). He deletes those. "@Name As discussed," after a huddle with that person is on-tone.
- Counts to the Director in one prose block, modules first, closed with "X come after this." He rewrote it as 1 / 1.1 / 1.2 (labs) then 2 (modules), and a Next that names the experiment and the 12/25 set.
- A caveat the reader cannot act on. If the reader can't change behavior because of it, it goes to Dhiraj privately, not in the outbound.
- A four-case / yes-no / workflow-chart walkthrough of a product change to the Director. He stopped this on 3 Sep 2026: "We are discussing too many interlinked steps... Just speak about scenarios. Scenario one." The chart is for tech. He gets the outcome and the scenarios.
Tone flex by reader
- the VP: wants it "very simple". Numbered options, one line each. He replies with numbered picks.
- the Director: numbered 1 / 1.1 nest when a count has cuts; labs before modules if he asked labs. Ball in HIS court ("Please confirm"), absolute dates, no detail numbers in emails the CEO sees. His own rewrites land near 80 words. Spoken product change: outcome, then Scenario 1 (3 Sep 2026). Eng alignment before a date. CS/sales training: first cut is what not to cover, then a dry-run with him. Collate stakeholders in one thread; do not hop WhatsApp then call then alignment. His spoken register with Dhiraj is Hinglish and blunter than any written specimen ("the engineer छोड़ो", "कर दो ये चीज़, आगे देखेंगे"); do not calibrate written tone off it, and do not read the bluntness as displeasure. It is how he talks when the answer is obvious to him.
- the CS lead: operational, non-technical. What CS should DO, never how the system works. Route failures to Dhiraj ("send me the account") instead of explaining mechanisms.
- Developers (tickets): the team's own screen names ("Step 3", "Labs Home page"), testable ACs, mark (NEW) on added scope. See ticket memories. The requirement handoff and the UAT are the PM's two gates (the Director, 3 Sep 2026); a ticket the PM later has to QA heavily had requirements that were too high level. Write the ACs so the gates hold and the middle stays engineering's.
Hard gates (after drafting, before showing)
- Budgets: Slack 60 words, stakeholder email 120, meeting description 80. Over = defect.
- Sweep for: em dash, dated provenance, editing seams ("per your comment"), hedge-stacking, question-count mismatch, any sentence the reader does nothing with, a yes-no tree or four-case flowchart when the reader is the Director and the topic is a product change.
- Depth I acquired while researching stays in my message TO Dhiraj. The outbound carries only what changes the reader's next action.
Escalation of drafts
Show Dhiraj the outbound draft alone, ready to paste. Analysis, verification notes and caveats go under it, clearly separated, never woven into the draft.
Drift countermeasure (why this loads EVERY draft)
Persona consistency degrades within 8-12 turns even with rules still in context; the highest-risk moment is drafting right after investigation-heavy work. So: re-read this file at the moment of EVERY draft, not once per session. Fixed shapes above are the second countermeasure - templates resist drift, adjectives do not.
Corpus growth (the flywheel)
Every time Dhiraj edits a draft or replaces it with his own version: his version goes into On-tone with its trigger; the superseded draft goes into Off-tone with one line naming the failure. Add a rule only when a sample cannot carry the point.
Measurement (visible improvement)
For every outbound draft, save my version, then when his sent version is observable:
node ~/.claude/skills/writing-for-dhiraj/score.mjs --log <surface> <reader> <draft> <sent>
Monthly: node score.mjs --report -> HAR (accepted-unedited rate) and mean edit distance.
Success = HAR rising, distance falling. Review the worst 3 diffs and fold them into the corpus.