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

planning-tracker-builder

Skill21 starsChanged 47 days agoNo licenceView on GitHub

Build or extend Zynkr's planning Main Tracker (the cycle's system of record) from a NORMALIZED item list — the planning-session-synth handoff or a pasted table. Fresh cycle: copy the template tracker (never edit it) → 「<year> <cycle> Planning Main Tracker」 → cycle-named tabs → fill the SOR tab with L1 header rows + N.NN numbering, 重要×緊急 → Priority formula, the 專案項目小記 pivot, 狀態 colours. Existing tracker: fill the empty SOR tab session-synth left, append rows under the right L1 block, or add a new tab — never overwrite the SOR tab in place, never renumber. Prints a LINT REPORT (P0 cap > 6 / > 25%, owner > 3 P0, items 掛 All, missing owners/dates, L2 off-taxonomy, duplicate 項目, P3 not 放棄) and the C1 cash pre-mortem before writing; lint warns, never blocks. Trigger on /planning-tracker-builder or "建 tracker", "把項目清單做成 Main Tracker", "建立 YE Planning Main Tracker", "把正規化清單寫進 tracker", "把這些專案 項目排進 tracker", "build the planning tracker", "extend the tracker with these items", "lint the project list". Distinct from planning-session-synth (upstream — transcript + whiteboard → normalized list), planning-tracker-sync (downstream weekly READ; never builds), planning-suite-reconciler (docs/OKR sheet reconcile TO the tracker) and project-status-update (course-project weekly; owns bare 「週報」).

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    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