PL-operations Plugin — Cheat SheetStratum Collective · Claude Code Plugin · Skills reference, hygiene rules, and integration map · Updated April 2026


Core Skills — invoke with /skill-name or describe the trigger

ops-triage ops
Structured assessment for blocked, complex, or multi-stakeholder work. Pulls full context from Notion, git, and hubs. Splits actions into safe-to-execute vs. needs-critical-input. Executes safe actions immediately.
Triggers: "triage this" · "what's blocked" · "take it from the top" · "ops review" · "where are we at" · "assess this work"
Output: Context/goal · Progress · Gaps · Tradeoffs · Ordered next steps · Action split
compliance-gate ops
Point-in-time compliance readiness report for a specific milestone. Scans Legal hub, DMP, Security Posture, contracts, and Ops Tracker. Produces a shareable, timestamped gate report with pass/fail/gap per requirement.
Triggers: "are we ready to submit" · "compliance check" · "HIPAA readiness" · "what gates are open" · "audit readiness" · "can we submit [X]"
Output: Gate summary table · Critical blockers · Gaps · Evidence inventory · Recommended next steps · Saved to Hub-Legal
initiative-review ops
Top-down review of a parent initiative: validates task hierarchy (parent/child/blocking relations), finds orphans, identifies critical path, and surfaces status inconsistencies.
Triggers: "review this initiative" · "what's left on [X]" · "fix the hierarchy" · "rollup for [X]" · "clean up [initiative]" · "what's blocking [X]"
Output: Tree structure · Structural issues · Critical path · Recommended fixes (safe vs. needs-input)
progress-report ops
Generates a Day N progress report from Ops Tracker, git activity, pipeline data, and previous reports. Day 1 = Nov 12 2025. Grades execution against a rubric from A (revenue) to D (regression).
Triggers: "progress report" · "day report" · "how are we doing" · "Day [N] report" · "weekly update"
Output: Grade + delta · Tracker snapshot · Commercial metrics · What was built · Diagnosis · 14-day action plan · Saved to Hub-OPS
protocol-audit ops
Scans all governance, policy, and operational docs for staleness, broken references, and coverage gaps. Compares what docs reference against what actually exists. Periodic maintenance check.
Triggers: "audit our protocols" · "what's stale" · "governance health check" · "are our docs current" · "what needs updating"
Output: Staleness findings · Accuracy issues · Coverage gap matrix · Quick fix list · New docs needed

KB & Sweep Skills

kb-refresh kb
Detects drift between questions.json and 11 canonical Notion source pages. Flags questions where answers have substantively changed (>70% confidence). Creates draft revision items in the Ops Tracker.
Triggers: "kb refresh" · "refresh the knowledge builder" · "check kb for drift" · "sync knowledge builder"
Output: KB:-prefixed Ops Tracker items (Not started) · Summary run item (Done) · Deduplicates against existing open items
kb-apply kb
Applies approved KB refresh proposals to questions.json. Reads Ops Tracker items prefixed KB: with Status = Done and ---PROPOSED--- delimiter. Updates answers, validates JSON, commits to git.
Triggers: "kb apply" · "apply kb approvals" · "apply approved kb items"
Output: Updated questions.json · Git commit with list of changed question IDs · Applied note appended to each tracker item
ops-sweep ops
Nightly sweep of Stratum git activity → Ops Tracker items. Scans today's commits across all active repos, creates Done items for completed work and Not-started items for logical next steps. Cap: 8 items per run.
Triggers: "ops sweep" · "end of day sweep" · "log today's work" · "create tracker items for today" · /ops-sweep
Output: Completed items (Done, Progress 100) · Next steps (Not started) · Matched items (no change)
ops-hygiene-sweeps hygiene
Comprehensive Ops Tracker hygiene. Runs C1–C23 checks across the full database. Always queries the entire DB (no keyword filters) and batch-verifies before declaring complete.
Triggers: "run hygiene sweep" · "ops hygiene" · "clean up the tracker" · scheduled runs · /ops-hygiene-sweeps
Output: Per-check counts · Auto-fixes applied · Warnings generated · Consolidated tracker warn item (if violations exist)

Integration Points

SystemID / PathAccess
Ops Tracker DBcollection://2e03b4e5-5382-803f-ad1d-000b6a6b90b8R/W
Hub-OPS0dda2e50-5679-4ece-b791-f3d23d699020R/W
Hub-Legal30d3b4e5-5382-81ef-b463-c045f5c24978R/W
Hub-P&T2dc3b4e5-5382-80f1-a14f-d8818b4afc50R
questions.jsoninternal-dashboards/knowledge-builder/R/W
Git reposstratum-platform · stratum-cli · stratum-site · internal-dashboardsR

Hygiene Checks — C1 to C23

Data Completeness

CheckRuleFix
C1Missing Prioritywarn
C2Missing OG End Datewarn
C3Missing Timeline (In Progress)warn
C7Missing Deptauto
C8Dept mismatchauto
C13Missing LoEauto
C14Missing Urgencyauto

Status & Progress

CheckRuleFix
C4Stale 14+ dayswarn
C5Blocked, no Blocked-by setwarn
C6Done + Progress < 100auto
C10Stale blockwarn
C15Epic Progress rollup offauto
C20Progress 100, Status ≠ Doneauto
C21In Progress stale (H4 threshold)auto / flag

Hierarchy & Naming

CheckRuleFix
C9Title not verb-firstwarn
C11Orphan child (no parent)auto
C12Noun-titled non-epicwarn

Priority & Timeline

CheckRuleFix
C16Priority/Timeline misalignmentauto
C18Low + dates present → stripauto
C19Low + date added → Mediumauto

Milestone Fields

CheckRuleFix
C17Is Milestone = true, Milestone Status emptywarn
C22Is Milestone = true, dates populatedwarn

Timeline / Status Alignment

CheckRuleFix
C23aNot started + Timeline → clear bothauto
C23bPaused + Timeline end → clear end onlyauto

H-Series Rules (April 2026)

H1 — Low Priority = No Dates C18
Low priority tasks must have no OG End Date and no Timeline. Low = backlog, no schedule commitment. Dates contradict the priority signal. Auto-strip on sweep.
H2 — Date Assignment → Priority Escalation C19
If a Low priority task receives a Timeline start or OG End Date, auto-promote to Medium. Low = unscheduled by definition — assigning a date means committing to it.
H3 — Zombie Cleanup C20
Progress# = 100 but Status ≠ Done → force Done. Status automation is unreliable; do not depend on it as the sole mechanism.
H4 — In-Progress Staleness → Paused C21
See threshold table (right). On transition to Paused: preserve Timeline start (factual history of when work began), clear Timeline end (commitment is void).
H5 — Milestone Field Rules C22
Milestones (partner signatures, data gates, product shipping): Is Milestone = true, Milestone Status = Pending, OG End Date cleared, Timeline cleared. Status = left as-is.
H6 — Paused ≠ Parked
Paused = temporarily deprioritized, intend to resume (used by H4). Parked = permanently shelved or achieved. Never set Parked for slow-moving work.

H4 Staleness Thresholds

DomainThresholdAction
HIPAA / AWS / de-identification engineeringExemptNo action
ENGINEERING · LEGAL · RESEARCH14 daysFlag only
PRECEDENT10 daysFlag only
MARKETING · PARTNER DEV · OPS · GRANTS7 daysAuto-Paused

C23 — Status / Timeline State

StatusTimeline StartTimeline End
Not startedMust be emptyMust be empty
In ProgressSet on transitionSet (target date)
BlockedPreservedPreserved
PausedPreserved ← historyMust be cleared
DonePreservedPreserved
ParkedPreservedPreserved

Progress Report Grade Rubric

GradeCriteria
ARevenue generated or sprint sold. Pipeline converting.
BDiscovery calls happening. Proposals sent. Active sales conversations.
C+Infrastructure built. External contacts made. No revenue yet.
CExecution improving but pre-revenue, pre-pipeline.
C−Blocked tasks high. Low completion. No external contact.
DRegression — things getting worse.