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

planning-lob-gap-audit

Skill21 starsChanged 49 days agoNo licenceView on GitHub

Audit ONE line of business (an L1 LOB such as 3.0 Operations) after a planning cycle: inventory its Drive folder, read its plan Doc + Refresh addendum and its rows in the planning Main Tracker, and cross-check five gap classes — P0/P1 items with no doctrine/SOP or owner-named plan, role docs / SOPs that contradict the plan (stale tools, stale owners), docs the plan cites that do not exist, superseded snapshots without a [SUPERSEDED] banner, and open decisions the plan needs from the founder. Produces a wave-ordered heal list (SOR sync → banners → build missing doctrine → rewrites) with 可交 Claude flags and the owning skill per fix, written as a NEW report Doc 「[N.0.1] <LOB> — <cycle> Gap Audit & Heal Plan（YYYY-MM-DD）」 plus a NEW 「行動追蹤表」 Sheet in the LOB folder. Report-only: it never edits, renames or moves an existing Doc, and never executes a fix. Trigger on /planning-lob-gap-audit or when Peter says "部門缺口稽核", "幫我做 3.0 的 gap audit", "檢查營運部門的文件有沒有跟計畫對齊", "文件缺口盤點", "做一份 heal plan", "哪些 SOP 過時了", "audit the ops docs against the H2 plan", "LOB gap audit", "gap audit and heal plan for <LOB>". Distinct from admin-governance (local _INDEX.md ↔ Drive INDEX sync — metadata only, all LOBs, weekly), from consult-governance (the consulting ENGAGEMENT portfolio — a pattern source only), and from planning-suite-reconciler (WRITES the plan addendum this skill only READS — this skill writes no addenda).

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 3 are distinctive, and 5 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.

  • 5

    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