Profile My skills Saved Collections Edit profile Submit a skill

← all publishers

rohitgehe05

@rohitgehe05 source repo

6 published skills

  1. ▌
    Drafting · rohitgehe05
    Use when a mindpowers spec exists and the user wants the actual deliverable written, such as "draft it", "write the memo from the spec", or right after mindstorming locks a spec. Not for code; not for drafting without a spec (offer mindstorming first).
    0
    installs
  2. ▌
    Calibrating · rohitgehe05
    Use after a knowledge-work deliverable ships or gets human edits. Triggers on "that draft worked", "they rewrote half of it", "remember this for next time", or when the user returns with feedback on a shipped doc. Not for code retrospectives.
    0
    installs
  3. ▌
    Mindstorming · rohitgehe05 bundle
    Use before drafting any non-code knowledge-work deliverable, including strategic memos, business reviews, OKR defences, PRDs, decision docs, briefing docs, exec talking points, Slack messages to leadership, frameworks, post-mortems, one-pagers, BRDs. Triggers on asks like "help me write up X", "draft this memo", "what should I say to Y", even casually phrased. NOT for software implementation; for creating features, components, or code changes use superpowers:brainstorming instead; for authoring the PRD document itself, use this skill. For non-code deliverables this skill supersedes generic brainstorming. Do not skip for simple asks; simple tasks hide the costliest assumptions.
    0
    installs
  4. ▌
    Fact Checking · rohitgehe05 bundle
    Use before a finished document ships, when the user asks "fact-check this", "is this ready to send", "check the numbers", or after drafting/review hand off a doc that carries checkable claims (numbers, dates, names, quotes). Verifies claims against user-supplied sources with a hard quote-the-source rule and flags sensitive content (named people, customer names, unannounced plans, PII). Not a hard gate; it reports honestly and the user decides. Not for code, and not for verifying specs.
    0
    installs
  5. ▌
    Reviewing Docs · rohitgehe05 bundle
    Use when the user has a finished or near-finished document (memo, business review, PRD, decision doc, briefing, comms, framework, talking points, post-mortem) and wants it pressure-tested before it ships, such as "review this doc", "poke holes in this", "is this ready to send". Works on any doc, not just mindpowers-drafted ones. Not for code review.
    0
    installs
  6. ▌
    Validating Problems · rohitgehe05 bundle
    Use when a user wants to test, sharpen, frame, or gather evidence for a customer or business problem before pitching a direction, prioritising work, or writing a PRD.
    0
    installs