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.
rohitgehe05/mindpowers
SkillsMP has collected 6 skills from rohitgehe05/mindpowers. Open a skill to review its source and details.
- Latest recorded source activity
- SkillsMP catalog refreshed
- skills collected
- 6
- GitHub stars
- 5
- GitHub forks
- 0
Skills in this repository
Showing 6 of 6 collected skills.
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…
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…
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).
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…
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.