executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
briefing-noteWrite a one-page briefing note that gets a busy principal up to speed fast. Use when asked to brief a minister/executive/official, prepare a briefing note or read-ahead, or summarize an issue for a decision or meeting. Produces a tight, single-page note: purpose, background, key facts/considerations, and a recommendation or the decision sought — scannable i…
Independent GitHub snapshot · Automated classification · Original documentation governs
A briefing note gets a principal ready for a decision, a meeting, or a question — on one page, in two minutes. It's ruthlessly concise: purpose, the few facts that matter, the considerations, and what's being asked. This skill writes that note in the standard structure officials and executives expect.
Ask for these only if they aren't already provided:
Date · Prepared for · Purpose: [for decision / for information / for meeting on DATE]
Issue — one or two lines: what this is about and why it's in front of them now.
Background — the minimum context needed, as tight bullets (dates, decisions to date, who's involved). No history for its own sake.
Key considerations — the factors that matter to the decision or discussion: facts, risks, sensitivities (financial, legal, political, reputational), stakeholder positions. Bullets, not prose.
Recommendation / decision sought — if for decision: the recommended action and one-line rationale. If for information/meeting: the key messages or the line to take, and likely questions with suggested answers.
Contact — who to follow up with.
Keep it to one page. Detail belongs in an annex, referenced not included.
Government/executive briefing-note practice (purpose-led, one page, key considerations, decision-or-line-to-take).