anticipatory-draft
Use when a decision, announcement, email, or deliverable is due within about two days and the inputs are mostly known — produce the draft now, label it clearly as a draft, and list the remaining open inputs as a confirm-list.
- License 许可
- Apache-2.0
- 最近更新
- 2026-10-02
- Stars
- ★ 6
- Forks
- 3
01 前言 Front Matter
- name
- anticipatory-draft
- metadata
- { "tags": "draft, deadline, deliverable, announcement, anticipate", "version": "1.0.0", "display_name": "Anticipatory Draft" }
- description
- Use when a decision, announcement, email, or deliverable is due within about two days and the inputs are mostly known — produce the draft now, label it clearly as a draft, and list the remaining open inputs as a confirm-list.
03 SKILL.md 正文
Goal
Show up with the draft before anyone asks for it.
Steps
- Trigger: a known deliverable is due within ~2 days and the inputs on hand support a credible version. If inputs are too thin, don't draft — ask for the one or two that block drafting.
- Produce the full draft now, not an outline. Label it unmistakably: "Draft v1 — nothing sent anywhere."
- End with the remaining open inputs as a numbered confirm-list: "1. Final date — June 24, confirm? 2. Who signs it?"
- On revision, name what changed and which feedback drove it: "Reordered so the pricing change leads, based on Tuesday's comments." Never make the reader diff versions.
Rules
- A draft is a head start, not a decision — never send or publish on someone's behalf without explicit sign-off.
- v2 keeps everything from v1 that nobody questioned; only the named changes move.
- The confirm-list is short and answerable with one word each; anything needing discussion is a decision, not a confirm.
- If the deadline passes unanswered, nudge once with the draft attached — don't redraft speculatively.
04 同仓库更多 Skills
demo-skill
Use when the user asks to run the demo analysis workflow on a dataset.
youtube-transcript
Use when asked to get a transcript, extract key points, or summarize a YouTube video — given a YouTube URL.
weekly-status-report
Use when asked to compile a weekly status update, team recap, or progress report from recent channel activity, tasks, or notes.
weekly-channel-digest
Use when asked to digest a channel's week, recap what happened in a channel, catch someone up on a channel, or post a recurring "this week in
thread-recap
Use when asked to recap this thread, summarize the discussion above, TL;DR a long thread, or pull the decisions and action items out of the conversation right here — work from the live Slack thread in front of you and post a tight recap back into it.
theme-factory
Use when asked to create, adapt, or apply a visual theme — color palette, typography system, component tokens — for a product, document, or presentation.