agentleFS
Sign inStart free
peter-tu-zynkrpeter-tu-zynkr/zynkr-skill-builder/skills/0-strategy/planning-prework-pack/SKILL.md

planning-prework-pack

Skill21 starsChanged 49 days agoNo licenceView on GitHub

Build the BEFORE-THE-ROOM pack for a Zynkr planning session (H1 / H2 / YE): copy the session-workbook template Sheet and re-fill its five tabs for the new cycle (Read Me · Agenda 8 blocks · Pre-work by LOB 8 rows · Laundry List + Eisenhower seeds · Eisenhower Matrix) from the Main Tracker, the OKR tracker, the per-LOB plan Docs and the 1:1 Docs; write per-owner one-pager text blocks into a 「Pre-work — <cycle>」 Doc; hand a 16-slide template-fill request to /zynkr-slide (or print the slide text if it is not installed); and print a logistics checklist + calendar-invite text. Trigger on /planning-prework-pack or when Peter says "準備 planning session 的會前資料", "做 H2/YE 規劃會的 workbook 跟 deck", "會前 pre-work", "出規劃會 agenda 跟 pre-work", "prep the offsite", "build the planning pre-work pack". Shows the tab-by-tab plan first, writes only on confirmation, marks every number's source, never creates the calendar event or sends anything without an explicit yes. Distinct from planning-evidence-pack (numeric Scoreboard tab — consumed here), planning-1on1-annual-digest (one person's 年度計畫 Doc — only Top-3 lines lifted), planning-session-synth (AFTER the room), zynkr-slide (RENDERS the deck; this skill only writes the request) and project-status-update (the course-project weekly — bare 「週報」 stays there).

The file

We split this skill into the rules it gives an agent

11 rules. About 0 are common, 2 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free