policy-brief
Writes a concise, evidence-based policy brief - problem, options compared on consistent criteria, and a recommendation - that a decision-maker can act on in minutes. Use when someone asks "write a policy brief", "summarize the evidence and options for this decision", "brief the minister/board/council on X", or needs a one-to-four-page document that turns research into a recommended action. Do NOT use for persuasive opinion pieces - use op-ed-writer instead; for long-form marketing documents, use whitepapers; for condensing an existing long document, use executive-summary.
- License 许可
- MIT
- 最近更新
- 2026-10-14
- Stars
- ★ 25
- Forks
- 3
01 前言 Front Matter
- name
- policy-brief
- metadata
- { "title": "Policy Brief" }
- description
- Writes a concise, evidence-based policy brief - problem, options compared on consistent criteria, and a recommendation - that a decision-maker can act on in minutes. Use when someone asks "write a policy brief", "summarize the evidence and options for this decision", "brief the minister/board/council on X", or needs a one-to-four-page document that turns research into a recommended action. Do NOT use for persuasive opinion pieces - use op-ed-writer instead; for long-form marketing documents, use whitepapers; for condensing an existing long document, use executive-summary.
03 SKILL.md 正文
Policy Brief
A brief exists to inform one specific choice by one specific decision-maker - not to survey a literature. The costly failure is the brief that is read only as far as its summary and gives the reader nothing actionable there, or that strawmans the rejected options and loses credibility the moment a stakeholder notices. Write so that a busy reader who stops after the first half-page still knows the problem, the recommendation, and why.
Inputs to collect
- Who decides, and what decision they face - the single question the brief must answer. If the user cannot name the decision, help them narrow it before writing; "inform them about X" is not a decision.
- The decision deadline and any political, budget, or legal constraints that rule options in or out.
- The evidence available: studies, data, prior evaluations. Note what is missing; gaps shape how strongly the brief can recommend.
- The audience's technical depth. Default: intelligent non-specialist - define every acronym on first use.
- Length target. Default: one to four pages. Longer than four pages is a report, not a brief.
Label anything assumed rather than supplied.
Operating procedure
Order matters: options cannot be compared until criteria are fixed, and the executive summary is written last even though it appears first.
- Fix the decision and criteria. State the choice in one sentence. Choose 3-5 comparison criteria - effectiveness, cost, equity, feasibility, time-to-impact are the standard set - and hold them constant across every option.
- Draft the problem statement. What is wrong, who is affected, why now, and the cost of inaction. Quantify wherever possible; a problem without a number invites indefinite delay.
- Compress the background. Only what is needed to understand the problem - typically one to two paragraphs.
- Assemble the evidence. Cite credible primary sources; note the strength and limitation of each. Distinguish strong causal evidence (randomized or well-identified quasi-experimental) from correlation and from expert opinion, and say which is which. Present evidence on all sides, including findings inconvenient to the eventual recommendation.
- Build 2-4 realistic options, always including the status quo. For each: how it works, expected impact, cost, feasibility, key trade-offs - scored against the fixed criteria in a comparison table. Do not strawman the options you reject; state each option's best case fairly.
- Recommend and condition. Name the preferred option, the reasoning against the criteria, the assumptions it rests on, and the conditions under which the recommendation would change.
- Sketch implementation. Concrete first steps, owners, and timeline - a recommendation without a first step is a suggestion.
- Write the executive summary last. Problem plus recommendation in 3-4 sentences that stand alone. Many readers read nothing else.
Options table template
Criteria (weight) | Option A: [FILL] | Option B: [FILL] | Status quo
Effectiveness | [FILL] | [FILL] | [FILL]
Cost (annual) | $[FILL] | $[FILL] | $[FILL]
Equity impact | [FILL] | [FILL] | [FILL]
Feasibility | High/Med/Low | High/Med/Low | High/Med/Low
Time to impact | [FILL] months | [FILL] months | n/a
Key trade-off | [FILL] | [FILL] | cost of inaction: [FILL]
Bad summary: "This brief examines several approaches to school absenteeism and discusses their relative merits." Good summary: "Chronic absenteeism has doubled to 28% of students since the baseline year. Of three options assessed, targeted mentoring is recommended: evaluations show a 4-6 percentage-point reduction at roughly $1,500 per student, versus weak evidence for automated messaging alone. Begin with a two-school pilot next term."
Deliverable
Produce a one-to-four-page brief containing: title and standalone executive summary; quantified problem statement; minimal background; evidence section with sources graded by strength; 2-4 options scored in a consistent comparison table; a conditioned recommendation; and implementation first steps with owners and timeline.
Do NOT
- Do not bury the recommendation at the end. Lead with the bottom line (BLUF); the structure of a brief is conclusion-first, evidence-after.
- Do not present only supporting evidence. Omitting the strongest counter-evidence is the fastest way to lose a skeptical reader - and decision-makers employ skeptical staff.
- Do not mix evidence with values silently. Separate what is (evidence) from what should be (normative choices) and label the normative ones.
- Do not compare options on shifting criteria - praising one option's cost and another's speed hides the real trade-off.
- Do not exceed four pages or leave jargon and acronyms unexplained.
Quality bar
Before shipping: the executive summary stands alone and states the recommendation; every factual claim has a findable citation; evidence strength is graded, not asserted; all options - including status quo - are scored on identical criteria; assumptions and change-conditions are explicit; a reader can identify the first implementation step and its owner.
Escalation
A brief informs a decision; it is not legal advice, and options touching statute, regulation, or liability need counsel review before adoption. For verifying a load-bearing statistic before it anchors the problem statement, use fact-checker. For deep sourcing on an unfamiliar topic before drafting, run deep-research first.
04 同仓库更多 Skills
zone-2-cardio-plan
Use when someone asks to build a steady-state cardio plan, train an aerobic base or Zone 2, structure easy or endurance weekly cardio, train by heart-rate zones, or improve resting heart rate, VO2, or endurance. Builds a heart-rate-zone aerobic training block with session structure, modality choice, and progression. General fitness guidance, not medical advice. Do NOT use to design a strength or lifting program (use Strength Training Plan), high-intensity interval conditioning, HIIT, or circuits (use Conditioning & HIIT Program), or a mobility/flexibility routine (use Mobility Routine).
youtube-script-writer
Writes retention-engineered long-form YouTube scripts on a hook/body/payoff architecture - a first-30-seconds hook that survives the retention cliff, a beat-sheet body with mini-hooks and bridges, timed pattern interrupts, and a payoff that over-delivers - with B-roll and editing cues marked inline. Use when someone says "script my next video", "my retention graph dies at the start", "tighten this draft", or "outline a video on X". Do NOT use for the 3-second opener of TikTok, Reels, or Shorts - use video-hook-writer instead; do NOT use for spoken voiceover synced to on-screen tutorial actions - use narration-script instead; do NOT use for a sales demo built on a buyer's discovery notes - use demo-script instead; do NOT use to design the thumbnail and title - use thumbnail-concept instead.
win-back-campaign
Designs segmented win-back email sequences for dormant users - dormancy tiers, a three-beat sequence with a single proportional incentive, and a suppression rule - and measures success by re-activation, not opens. Use when someone says "our users went quiet", "design a win-back campaign", "how do I re-engage lapsed customers", "should we email people who haven't logged in for months", or lifecycle messaging has stopped landing with a lapsed segment. Do NOT use for recovering an unfinished checkout - use abandoned-cart-sequence instead. Do NOT use for diagnosing and fixing why active customers cancel - use churn-reduction instead. Do NOT use for building always-on onboarding or nurture flows - use email-drip-builder instead.
wikipedia-style
Writes neutral, verifiable, encyclopedic prose following Wikipedia's core content policies and manual of style - NPOV, inline citations, notability-backed claims, and a strict ban on promotional language. Use when someone asks "write this like a Wikipedia article", "draft a Wikipedia page for this company or person", "make this neutral and encyclopedic", or "why does my article draft keep getting rejected". Do NOT use for persuasive or opinion writing - use op-ed-writer instead; for thesis-driven academic papers, use academic-essay; for verifying claims in existing text, use fact-checker.
whitepapers
Structures and writes authoritative B2B whitepapers - a standalone executive summary, a data-sized problem statement, methodology, evidence-driven findings, recommendations, and a soft call to action - flagging every claim that needs a real citation. Use when a marketer asks "write a whitepaper on this topic", "turn our research into a lead-gen asset", "make this credible enough for executives", or a draft reads like a product pitch instead of analysis. Do NOT use for customer-story-driven proof - use case-study-builder instead; for policy audiences, use policy-brief.
white-space-analysis
Finds unmet market gaps by ranking jobs-to-be-done on importance versus satisfaction, overlaying them against current solutions and workarounds, and validating that each gap is real, winnable, and worth winning. Use when someone asks "where are the gaps in this market", "what's underserved here", "where should we play next", or is hunting for product, feature, or market-entry opportunities. Do NOT use for profiling competitors and building battle cards - use competitive-intelligence instead; for putting a dollar figure on an identified opportunity - use market-sizing instead; for extracting jobs-to-be-done from raw customer interviews - use jtbd-extractor instead.