agenda
Draft a default agenda for an upcoming client call from the calendar event, the last follow-up, and open work. Use before a client meeting or when asked for an agenda; for a report of shipped work with no call, use weekly-recap.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- agenda
- description
- Draft a default agenda for an upcoming client call from the calendar event, the last follow-up, and open work. Use before a client meeting or when asked for an agenda; for a report of shipped work with no call, use weekly-recap.
03 SKILL.md 正文
Agenda
Draft an agenda that gets each needed decision made on the call and gives it an owner.
Run intake for phase agenda. Use the event the user named, or the client's next call
on Google Calendar. Check the ledger per ../../ledger.md, and stop if
the key is already written.
Build from these, highest priority first:
- Open action items and unresolved questions from the last follow-up.
- Standing items from the client config body.
- What is new since the last call: shipped work, open PRs or issues waiting on the client, and Slack threads that need a decision.
- The event description, when it names a topic.
Write claims per ../../recap-format.md.
Fit the agenda to the length of the event, dropping the lowest-priority items first. Each item names the input wanted and who owns it. List an item as a decision only when the sources show the client has to choose on this call. Otherwise list it as a topic with a proposed default.
🗓️ *<Client>: <Event title> (M/D, h:mm)*
What the call must leave with, in one line.
🎯 *Decisions needed*
• *Topic:* Decision wanted. _Owner_
🤝 *Topics to align on*
• *Topic:* What to discuss. Proposed default. _Owner_
🔄 *Updates*
• *Topic:* One line.
🧗 *Worked through*
• *Topic:* What was in the way. What we did. Where it stands.
📌 *Carried over*
• *Item:* Status. _Owner_
Choose Worked through items per
../../recap-format.md. Omit empty sections. When
the agenda will be shown in the meeting, offer a deck built from
../../examples/agenda.deck.md. Write to the target per
../../outputs.md.
04 同仓库更多 Skills
human-voice
Humanize prose by choosing a surgical voice edit or a structural rewrite. Use for AI-sounding drafts, anti-slop passes, editorial reviews, and requests to preserve an author's voice.
install-anti-slop
Install and configure the anti-slop Oxlint plugin in a local TypeScript or JavaScript repository. Use whenever a user asks to add anti-slop lint rules, copy the anti-slop plugin, configure opinionated Oxlint rules, or migrate an existing local anti-slop setup.
improve-codebase-architecture
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
eli5
Explain a topic like I'm a 5 year old. Use when the user types /eli5 <topic> or asks for a dead-simple picture explainer of how something works.
codebase-design
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
audit-codebase
Read-only whole-codebase audit for simplifications in data structures, state representation, control flow, algorithms, and ownership. Inventories every subsystem as a coverage contract, reviews each one in a bounded subagent, verifies each finding against the repo, then audits its own coverage. Never edits, runs tests, commits, or pushes. Use for "audit this codebase", "find simplifications", or a pre-refactor survey.