By PromptLeadz · Reading time 17 minutes · 50 prompts across 5 categories · Calibrated for 2026 frontier models

What separates the practitioner from the productivity-influencer

Knowledge-work productivity is the most LinkedIn-saturated category on the platform. Threads about 10x productivity, building a second brain, level-up frameworks, deep-work blocks, atomic habits, first-principles thinking, and cognitive load get hundreds of thousands of likes. The threads describe a vibe. The actual work is shipping artifacts.

A working professional's primary job, regardless of role, is producing decision-grade artifacts: memos that survive skimming, summaries that name the gap, decision docs with kill criteria, meeting outputs with named action items, weekly reviews with structural lessons, project plans with named dependencies. None of these artifacts look exciting on a screenshot. All of them compound. The promotion, the trust, the next opportunity all come from the artifacts, not from the threads about how to produce them.

Six dimensions separate the practitioner voice from the productivity-influencer voice. Substance: the practitioner names the specific decision, owner, and trade-off; the influencer names the disposition (deep-focused, high-leverage, first-principles). Trade-offs: the practitioner names what is being deprioritized; the influencer says "and" instead of "or". Numbers: the practitioner opens with the metric, the cohort, the dollar value; the influencer opens with the framework story. Ownership: the practitioner names the owner and the date; the influencer names the system. Tone: the practitioner writes flat memos; the influencer writes narrative arcs. Audience: the practitioner writes for the executive review, the team meeting, the customer escalation; the influencer writes for the algorithm.

Both voices exist in the wild. Only one survives the executive review, the procurement call, and the post-launch retro. This pack is calibrated for the first; it explicitly rejects the second at the prompt level by banning the genre's signature phrases inline. Output reads like a memo from a working professional who has just defended a decision in front of leadership, not a thread from a personal-brand productivity guru who has not.

Five categories. The knowledge-work core.

The five categories map to the five operating disciplines that determine whether a knowledge worker compounds or churns through quarters with no artifact to show. Writing and Communication comes first because written artifacts are the highest-frequency output of any knowledge job. Reading and Synthesis comes second because most knowledge workers spend hours reading without explicit synthesis discipline. Decision and Analysis comes third because the kill criterion, the trade-off matrix, and the options memo are where leverage lives. Meetings and Coordination comes fourth because most meetings could be a memo and the discipline of converting meetings to artifacts is a career multiplier. Personal Operations and Learning comes fifth because the personal operating system is what compounds across years.

Most knowledge workers who fail to compound do so by skipping the unglamorous categories: weekly review with structural lesson, decision retro with named lesson, debrief memo with structural change, options memo with rejected alternatives. The thread-genre productivity-influencer skips these in favor of "second brain" content; the actual practitioner does these because they are the leverage.

1. Memo to leadership with the trade-off named

Topic: [paste]. Audience: [paste roles, what they care about]. Decision being asked for: [paste]. Draft a 400-word memo: the headline outcome in one sentence (no preamble), the context in two sentences, the named trade-off (what is being deprioritized to enable this, specifically), the named risks honestly, the ask of the reader, the next checkpoint. Memos that bury the trade-off in narrative produce executives who skim past the actual decision.

2. Email reply that survives a tense thread

Thread context: [paste recent messages]. Position to defend: [paste]. Tone constraints: [paste, e.g. professional, no escalation]. Draft a 250-word reply: the named acknowledgment of the other side's point in one sentence, the position stated factually, the supporting evidence in two sentences, the proposed next step, the close that does not over-apologize or escalate. Replies that lead with apology or counter-attack produce thread spirals.

3. Status update that survives skimming

Period: [paste]. Audience: [paste]. Work covered: [paste]. Draft a 300-word status update: the headline (what shipped or moved), the named blockers with the ask, the open risks with the threshold to escalate, the ask of the reader (specific decision or unblocking), the next checkpoint. Status updates that read as activity logs produce readers who skim past the asks.

4. Long-form to short-form compression

Source: [paste long document]. Target length: [paste, e.g. 200 words]. Audience: [paste]. Draft the compressed version: the core thesis in the first sentence, the three supporting points with the strongest evidence per point, the named gap or limitation, the next step. Compressions that preserve narrative produce versions readers still skim.

5. Tone adjustment for a difficult message

Original message: [paste]. Audience: [paste]. Tone target: [paste, e.g. firm but not aggressive]. Constraints: [paste, e.g. preserve all factual content]. Rewrite the message: keep all factual claims, adjust register to the named target, soften where the tone overshoots, harden where the tone under-delivers, preserve the explicit ask. Tone adjustments that water down the ask produce messages that get ignored.

6. Cross-language draft with cultural adjustment

Source language: [paste]. Target language: [paste]. Audience and context: [paste]. Source text: [paste]. Draft the translation: the literal translation, the cultural adjustments named (idioms, hierarchy markers, directness register), the rejected literal phrasings with rationale, the open questions for a native review. Translations done literally without cultural adjustment produce messages that read foreign.

7. Voice match against an existing sample

Sample of voice: [paste 3 to 5 paragraphs of the target voice]. Topic to write about: [paste]. Length: [paste]. Draft the new piece: match the sentence rhythm, the vocabulary register, the structure of paragraphs, the use of examples, the cadence of the named voice. Avoid imitating tics that do not match the topic. Voice matches that imitate cadence without matching argument structure produce hollow pastiche.

8. Apology with structural change named

Failure: [paste, what happened, who was affected, when]. Audience: [paste]. Draft a 300-word apology: the failure named factually in the first sentence (no excuses, no preamble), the impact in the audience's terms, the immediate remediation taken, the structural change to prevent recurrence (specific, not generic), the explicit close. Apologies that promise vague improvement without naming a structural change produce trust erosion.

9. Push-back with the actual cost named

Request being pushed back: [paste]. Reason for push-back: [paste]. Audience and stakes: [paste]. Draft a 300-word push-back: the named acknowledgment of the request, the cost of accepting the request as stated (specific, with dollar values or time named), the alternative proposal, the named decision-maker who can resolve, the close that does not over-soften. Push-backs that lead with apology produce push-backs the audience overrides.

10. Asking for help without diluting the ask

Help needed: [paste, specific task or decision]. Audience: [paste relationship and authority]. Draft a 250-word ask: the context in two sentences, the named ask (specific, scoped, time-bound), the rationale (why this audience), the offer of reciprocity or context, the close that does not pre-apologize. Asks that bury the request in apology and qualification produce asks the audience cannot evaluate.

11. Long document summary with the gap named

Source document: [paste]. Audience for the summary: [paste]. Length target: [paste]. Draft the summary: the thesis in the first sentence, the three supporting arguments with the strongest evidence, the named gap or weakness in the document (the questions it does not answer), the implication for the audience, the recommended next reading. Summaries that omit the gap produce readers who think the document is more complete than it is.

12. Meeting transcript to action memo

Transcript: [paste]. Meeting context: [paste]. Audience: [paste]. Draft a 300-word memo: the decisions made (named specifically, no narrative), the action items with named owner and date per item, the open issues unresolved, the next meeting date and primary topic, the named decision-maker for unresolved items. Transcript summaries that recap discussion without isolating decisions produce meetings everyone re-runs.

13. Source verification of a claim

Claim: [paste]. Stated source: [paste if any]. Context: [paste]. Draft a 400-word verification memo: the claim restated precisely, the named primary sources that would verify or refute, the verification method, the assessment (verified, partially verified, unverified, refuted) with rationale, the confidence level, the open questions. Source verification done by Google search alone produces false confidence; this version names the primary source.

14. Cross-document comparison with consensus and disagreement

Documents: [paste 2 to 5]. Topic: [paste]. Draft a 500-word comparison: the named topic, the consensus across documents (with quoted phrasing), the disagreement points (where documents say opposing things, with quoted phrasing), the gaps no document covers, the implication for the reader, the recommended source for each open question. Comparisons that average out the documents produce false consensus.

15. Article steelman summary

Article: [paste]. Position to steelman: [paste, the article's argument]. Draft a 400-word steelman: the strongest version of the argument (stronger than the article itself), the named evidence from the article, the named additional evidence the steelman would invoke, the strongest counter-argument, the rebuttal to the counter. Steelman summaries that just restate the article produce no understanding of the strongest case.

16. Article counter-summary

Article: [paste]. Position to argue against: [paste, the article's argument]. Draft a 400-word counter: the strongest case against the article's position, the named weaknesses in the article's evidence, the named counter-examples, the alternative explanation, the conditions under which the article's position would still hold. Counter-summaries that nitpick without offering an alternative explanation produce hollow critique.

17. Research synthesis with confidence levels

Sources: [paste 5 to 20]. Question being researched: [paste]. Draft a 600-word synthesis: the question restated, the consensus answer with the named supporting sources, the confidence level in the consensus (high, medium, low) with rationale, the named disagreements with sources on each side, the open questions, the recommended next step (more research, decide, defer). Research syntheses that report findings without confidence levels produce false certainty.

18. Quote and citation extraction from a long document

Document: [paste]. Topic of interest: [paste]. Draft a quote-and-citation list: the 5 to 10 most relevant direct quotes (with the section or page reference), the context for each (one sentence), the implication of the quote for the topic. Quote extractions without context produce quotes that misrepresent the source.

19. Glossary builder for an unfamiliar domain

Domain: [paste]. Source documents: [paste]. Audience for the glossary: [paste literacy level]. Draft a 20 to 30 term glossary: the term, the plain-language definition, the context in which it is used, the related terms, the common confusion points (terms it gets confused with). Glossaries built without context produce dictionaries readers cannot use.

20. Document structural review

Document: [paste]. Purpose of the document: [paste]. Audience: [paste]. Draft a 400-word structural review: the named structural strengths (where the document delivers on the purpose), the named gaps (what is missing, specifically), the named redundancies, the recommended structural changes (move section X, cut section Y, add section Z), the priority of the changes. Structural reviews that praise without naming gaps produce documents that ship with the same flaws.

Most productivity advice circulating on LinkedIn is content marketing. The work that actually compounds is the work that does not screenshot well.PromptLeadz Workhorse Pack

21. Pros and cons memo with the kill criterion

Decision: [paste]. Context and constraints: [paste]. Draft a 500-word memo: the decision restated precisely, the pros named with the strongest evidence, the cons named honestly (not strawmanned), the recommendation with rationale, the kill criterion (the data or signal that would reverse the recommendation), the named decision-maker, the next review date. Pros-cons memos without a kill criterion produce decisions that drift without explicit re-evaluation.

22. Trade-off matrix with weighted scoring

Options: [paste 2 to 5]. Dimensions to evaluate: [paste]. Constraints: [paste]. Draft a 500-word matrix: the dimensions with the weight per dimension and the rationale for the weight, the score per option per dimension with the evidence, the weighted total, the recommended option with rationale, the rejected options with rationale, the named decision-maker. Trade-off matrices with even weights produce false rigor; this version names the weight rationale.

23. Scenario planning with named triggers

Decision context: [paste]. Time horizon: [paste]. Draft a 600-word scenario plan: three to four named scenarios (base case, upside, downside, breaking case), the named indicators that would signal we are in each scenario, the response per scenario, the reversibility per response, the named owner who watches the indicators, the cadence of review. Scenario plans without named indicators produce plans that get ignored when reality diverges.

24. Risk register with mitigation owners

Project or initiative: [paste]. Time horizon: [paste]. Draft a 500-word risk register: the named risks (likelihood and impact rated), the named owner per risk, the mitigation per risk (what we are doing now, what we would do if it materialized), the named trigger (the signal the risk is materializing), the named escalation path. Risk registers without named owners produce risks no one watches.

25. Options memo for a hard decision

Decision: [paste, what must be decided, by when]. Context and constraints: [paste]. Draft a 600-word options memo: the named options (typically 3 to 5, including the do-nothing option), the named criteria for evaluation, the assessment per option per criterion, the recommended option with rationale, the rejected options with rationale (not strawmanned), the named decision-maker and the date. Options memos that propose only the recommended option produce decisions that get re-debated.

26. Sunk cost diagnosis

Project or commitment: [paste, current state, history]. Recent signals: [paste]. Draft a 400-word diagnosis: the original thesis stated, the actual outcome to date, the gap analysis honestly, the named sunk cost (what would be lost by killing), the named opportunity cost (what is lost by continuing), the recommendation (continue, pivot, kill) with rationale, the kill criterion. Sunk cost diagnoses that emphasize the loss of killing produce zombie projects.

27. Reversibility check before commitment

Decision: [paste]. Stakes: [paste]. Draft a 300-word reversibility check: the named reversibility (one-way door, two-way door with named cost, conditional two-way door), the cost of reversal (time, money, relationships), the cost of delay vs the cost of irreversibility, the recommendation (commit, defer, pilot first), the named decision-maker. Reversibility checks treated as binary produce decisions that turn out to be more or less reversible than expected.

28. Devil's advocate review of a plan

Plan: [paste]. Authors and stakes: [paste]. Draft a 500-word devil's advocate review: the named assumptions in the plan that are most fragile, the named reasons the plan could fail, the named counter-evidence to the plan's thesis, the named alternative the plan rejects (with the case for the alternative), the questions the plan does not answer. Devil's advocate reviews that nitpick without naming the fragile assumptions produce plans that fail on the unnamed assumption.

29. Cost-of-delay calculation

Decision or project: [paste]. Current timeline: [paste]. Delay scenario: [paste]. Draft a 400-word cost-of-delay memo: the named cost per week or month of delay (revenue, opportunity, competitive, organizational), the named one-time costs avoided by delay, the cumulative cost of delay over the named horizon, the comparison to the cost of acting prematurely, the recommendation, the named decision-maker. Cost-of-delay analyses that ignore the cost of acting prematurely produce false urgency.

30. Confidence and assumption audit

Plan or decision: [paste]. Recent signals: [paste]. Draft a 500-word audit: the named assumptions ranked by uncertainty (the assumptions most likely to be wrong), the validation method per assumption, the named indicator that would tell us the assumption is wrong, the impact if the assumption is wrong, the named owner who tracks the assumption. Confidence audits that report "high confidence" without naming the fragile assumptions produce surprise misses.

31. Meeting agenda calibrated to outcome

Meeting purpose: [paste]. Attendees: [paste roles]. Time available: [paste]. Draft a 200-word agenda: the named outcome (the decision or alignment that must exist at the end), the named topics sequenced with time per topic, the pre-read or context attendees need, the named decision-maker, the asks of attendees. Agendas that list topics without naming the outcome produce meetings that need a follow-up meeting.

32. Meeting notes synthesis to action items

Notes or transcript: [paste]. Meeting purpose: [paste]. Draft a 300-word synthesis: the decisions made (named, no narrative), the action items with named owner and date per item, the open issues unresolved with the path to resolution, the next meeting date and primary topic, the named owner for each unresolved item. Notes synthesis that recaps discussion without isolating decisions produces meetings everyone re-runs.

33. Pre-meeting prep memo

Meeting: [paste topic, audience, time]. Position to advance: [paste]. Draft a 400-word prep memo: the audience's stated priorities (what they care about), the audience's likely concerns, the open questions to ask, the position to defend, the trade-offs to acknowledge, the asks to make, the worst-case scenarios and the response. Prep memos written as our talking points miss the audience's actual concerns.

34. Debrief memo with structural lesson

Event being debriefed: [paste, e.g. failed pitch, lost deal, missed launch]. Outcome: [paste]. Draft a 500-word debrief: the planned outcome vs actual, the named structural cause (process, capability, timing, audience read), not blame, the structural change for next time (specific, not generic), the named owner per change, the cadence of follow-up. Debriefs that produce no structural changes produce the same misses next time.

35. Escalation prep memo

Issue: [paste]. Escalation target: [paste exec or stakeholder]. Stakes: [paste]. Draft a 400-word prep: the issue in the first sentence with the dollar or strategic impact named, the actions taken to date, the request of the escalation target (specific decision: re-prioritize, add resources, accept slip, intervene), the consequence of inaction in named timeframe, the next checkpoint. Escalation preps that bury the impact produce escalations that get deprioritized.

36. Status meeting kill memo

Recurring meeting: [paste, attendees, cadence, history]. Reason for kill: [paste, e.g. has not produced decisions in 6 weeks]. Draft a 300-word kill memo: the named outcome the meeting was supposed to produce, the gap from that outcome, the named replacement (async update, written status, ad-hoc on-demand), the named owner of the replacement, the calendar action. Kill memos that just announce cancellation without naming the replacement produce reinstated meetings.

37. Cross-team alignment doc for a shared initiative

Initiative: [paste]. Teams involved: [paste]. Draft a 500-word alignment doc: the shared outcome (what will be true at the end), the named commitments per team with named owner and date, the dependency map, the decision rights (who decides what), the escalation path, the cadence of review. Cross-team initiatives without explicit decision rights produce coordination thrash.

38. Async written update to replace a meeting

Topic that would have been a meeting: [paste]. Audience: [paste]. Draft a 400-word async update: the headline outcome (what is decided or proposed), the context in two sentences, the decisions or proposals with rationale, the named open questions and the named owner per question, the named deadline for response, the close. Async updates that recap meeting topics without making explicit asks produce silence.

39. Conflict resolution prep memo

Conflict: [paste, parties, history, stakes]. Draft a 400-word prep: the named issue in objective terms (no blame), the named legitimate concerns of each party, the named common ground, the named gap, the proposed resolution with rationale, the worst-case scenarios and the response, the named decision-maker. Conflict preps that strawman the other party produce conversations that fail to resolve.

40. Decision log entry for a meeting outcome

Decision: [paste]. Meeting context: [paste]. Draft a 300-word log entry: the date, the decision stated specifically, the alternatives considered with rationale for rejection, the named decision-maker, the assumptions that would invalidate the decision, the next review date. Decisions made verbally without a log produce future re-debates.

41. Daily plan with the named priority

Today: [paste calendar, open commitments, pending decisions]. Draft a 300-word daily plan: the named single priority (the one outcome that would make today a win), the supporting tasks (sequenced with rough time blocks), the named blockers and the path to resolution, the items deliberately deferred to tomorrow, the close-of-day review prompt. Daily plans without a named priority produce days where everything is urgent and nothing compounds.

42. Weekly review with structural lesson

Week: [paste outputs, decisions, blockers, open items]. Draft a 500-word weekly review: the headline (what shipped, what compounded), the named misses with structural cause (not blame), the structural lesson for next week (specific, not generic), the named priorities for next week, the items being killed or deferred, the named relationships to invest in. Weekly reviews that recap activity without naming structural lessons produce the same patterns next week.

43. Quarterly priorities with kill criteria

Quarter: [paste]. Strategic context: [paste]. Draft a 600-word priorities doc: the named priorities (3 to 5, no more), the measurable indicator per priority, the named owner per priority, the kill criterion per priority (the signal that would deprioritize it), the explicit cuts from the quarter (what is not being done with rationale), the cadence of review. Quarterly priorities without kill criteria produce quarters where everything stays in scope and nothing ships.

44. Project plan with named dependencies

Project: [paste, scope, deadline, team]. Draft a 600-word project plan: the named outcome (what will be true at the end), the milestones with named owner and date, the named dependencies (cross-team, technical, decisional), the named risks with mitigation owner, the kill criterion, the cadence of review. Project plans without named dependencies produce surprise slips.

45. Reading note synthesis from multiple sources

Sources: [paste 3 to 10 reading notes or summaries]. Topic: [paste]. Draft a 500-word synthesis: the named consensus across sources, the named disagreement, the named gaps no source covers, the implication for the reader's work or decisions, the recommended next reading. Reading notes without synthesis produce collections that compound nothing.

46. Learning plan with measurable indicators

Domain to learn: [paste]. Time horizon: [paste]. Current baseline: [paste]. Draft a 500-word learning plan: the named outcome (the work the reader will be able to do at the end), the measurable indicators that prove progress, the sequenced curriculum (sources, projects, conversations), the named milestone projects, the kill criterion (when to abandon and shift), the cadence of review. Learning plans without measurable indicators produce shelved courses.

47. Habit audit with structural change named

Habit being audited: [paste, current state, original purpose]. Draft a 400-word audit: the original purpose stated, the actual current behavior honestly, the gap with structural cause (environment, trigger, reward, identity), the named structural change (specific, not generic), the named indicator that would tell us the change worked, the cadence of review. Habit audits that report "need more discipline" produce no change.

48. Decision retro with named lesson

Decision being retrospected: [paste, when made, what was decided]. Outcome: [paste]. Draft a 500-word retro: the original reasoning stated, the actual outcome, the gap (decision was right and outcome was bad, decision was wrong, or both), the named lesson (about the reasoning process, not the outcome), the structural change for future decisions, the named owner. Decision retros that judge by outcome alone produce learning that does not transfer.

49. Career conversation prep

Conversation: [paste topic, audience, context, e.g. promotion review, role change, performance check-in]. Draft a 500-word prep: the named asks (specific, not vague), the named evidence supporting the asks, the audience's likely concerns and the response, the named trade-offs the audience may raise, the worst-case scenarios and the response, the named follow-up. Career conversations that go in without prep produce outcomes the audience drives.

50. Unlearn list of assumptions to revisit

Domain or area of work: [paste]. Recent signals that something is off: [paste]. Draft a 400-word unlearn list: the named assumptions held that may no longer be true (typically 3 to 5), the named evidence that the assumption is shifting, the named test that would confirm or refute, the named owner of the test, the implication if the assumption is wrong. Unlearn lists that just list assumptions without naming the test produce permanent uncertainty.

How the prompts fit a real knowledge-work week and quarter

Daily: daily plan with the named priority, email replies and status updates, meeting notes synthesis, end-of-day review prompt. The daily discipline is where small drift gets caught before it becomes a weekly miss.

Weekly: weekly review with structural lesson, async update to replace meetings, decision log entries, reading note synthesis. The weekly cadence is where the compounding actually happens.

Monthly: habit audit, learning plan check-in, project plan re-baseline, debrief on shipped work. The monthly cadence catches drift before it becomes a quarterly pattern.

Quarterly: quarterly priorities with kill criteria, decision retros across the period, career conversation prep, unlearn list of stale assumptions. The quarterly cadence is where the strategy shows.

Annually: career conversation, learning plan refresh, project portfolio review, structural changes to the personal operating system. The annual cadence is where the trajectory gets calibrated.

A good memo names the trade-off. A good summary names the gap. A good plan names the kill criterion. The job is artifact work with named owners. The threads about the job are not.PromptLeadz Workhorse Pack, Section 6

Five mistakes that wreck workhorse prompts

1. Filling in the prompt with vibes instead of named owners, dates, and dollar values. The prompts ask for the audience, the named decision-maker, the specific trade-off, the dollar or time impact. Filling with "important", "urgent", "strategic" produces output of the same low calibration that leadership will reject. The discipline is putting the actual specifics into the inputs.

2. Treating the output as the final memo. The prompts produce drafts. The actual artifact is the draft after you have edited it for accuracy, removed the LLM-cliche phrasing, and verified that every name and number matches reality. Shipping the LLM draft directly to leadership or a customer is reckless.

3. Skipping the prompts that ask uncomfortable questions. The kill criterion, the rejected alternatives, the structural retro, the unlearn list. The avoided prompts are usually the ones with the most leverage. Notice the avoidance.

4. Using the prompts as one-shots instead of a weekly cadence. The compounding effect comes from running the weekly review, the decision retro, and the debrief regularly enough that the structural lessons accumulate. One-shot use produces one-time output.

5. Running the productivity-influencer prompts instead of these. Prompts that produce "10x productivity" content reinforce the genre this pack rejects. Calibration to the LinkedIn-thread voice produces threads, not memos.

Sources and further reading

The pack draws on a body of public work from operators and researchers across knowledge work. Recommended reading for practitioners who want depth beyond the threads.

Andy Grove, High Output Management, remains the single best book on knowledge-worker productivity, with the operating frameworks for one-on-ones, decision-making, and management leverage that most modern operators ladder back to.

Annie Duke, Thinking in Bets, is the most rigorous treatment of decision-making under uncertainty, especially the framework for separating decision quality from outcome quality.

Cal Newport, A World Without Email, covers the structural conditions for focused written work in a knowledge-work organization, including the protocols that make async written communication actually work.

Anne-Laure Le Cunff's writing at nesslabs.com covers learning, reflection, and personal operating practice grounded in research, with a focus on the practices that compound rather than the ones that screenshot.

About PromptLeadz

PromptLeadz publishes free component-built prompt packs and the production-grade Drop-in utilities that wrap them. The franchise covers role-based packs (PM, EM, CSM, Sales Leader, Operator, Data Analyst, VC), format-based packs (.md agent files in breadth and depth), and the underlying frameworks (the 8-Component Skeleton, the Anti-Prompt-Engineering Manifesto).

Every pack rejects the LinkedIn-influencer voice at the prompt level by banning the genre's signature phrases inline. The result is output calibrated for memos that survive peer review, not threads that go viral. Free packs ship with no email gate at promptleadz.com.

Questions people ask

Who is this workhorse prompt pack for?

Anyone whose job involves writing memos, reading documents, making decisions, running meetings, or planning work, regardless of discipline. Most useful for individual contributors and managers in knowledge-work roles.

How is this different from the role-specific packs?

The role-specific packs (PM, EM, CSM, Operator, VC, Founder GTM) calibrate to discipline-specific artifacts. This pack covers the universal artifacts every knowledge worker produces: memos, summaries, decision docs, meeting notes, weekly reviews. If you only learn 50 prompts, learn these.

Why does the pack ban phrases like 10x productivity and second brain?

Both are legitimate concepts ground into LinkedIn cliches. The pack bans the cliche framing because it produces low-calibration output that performs productivity rather than naming the artifact, the trade-off, or the structural lesson.

What output format do the prompts produce?

Memo register: flat, factual, named decisions, specific owners and dates, structural lessons. The opposite of LinkedIn-thread register.

How does this pair with other PromptLeadz packs?

This is the universal foundation. Pair with the role-specific packs (PM, EM, CSM, Operator, VC, Founder GTM, B2B Mega) for discipline-specific artifacts.

Are these prompts safe to share with my team?

The prompts themselves are free to share and ideal for team-wide adoption. The outputs of the decision, escalation, and retro prompts are confidential and should be reviewed before sharing externally.

Do these prompts work with Claude, ChatGPT, and Gemini?

Yes for all three. The prompts are built on the 8-component skeleton which works across frontier models.

If I am new to component-built prompting, where should I start?

Start with the writing and communication category (prompts 1 to 10). Once you have run those a dozen times, move to the decision and analysis category (prompts 21 to 30) for the highest-leverage work.

The franchise: free packs, frameworks, and the manifesto

The thesis: The Anti-Prompt-Engineering Manifesto. The framework: The 8-Component Skeleton.

Free packs, no email gate · Calibrated for 2026 frontier models · promptleadz.com