本文へ移動
cccskills
無料GitHub で公開

labor-and-union-relations

Manages the relationship with a represented workforce — administering a collective agreement, handling grievances, understanding what supervisors may and may not say, and preparing for bargaining. Use this for a grievance or arbitration question, a work rule change in a represented unit, supervisor guidance during organizing, contract interpretation and past practice, or preparation for negotiations.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md6.0 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Labor and union relations

A collective agreement is a contract that constrains management rights for its term. Most disputes are not about its words. They are about something a supervisor did that the words did not obviously cover, and about what the plant has done for the last five years.

This is jurisdiction-specific law with real consequences. Treat what follows as the structure of the problem and the vocabulary for the conversation, and involve qualified labor counsel before acting on anything contested.

Past practice is part of the agreement

The written agreement is not the whole of it. A practice that is consistent, known to both sides, repeated over time and unchallenged becomes enforceable, and changing it unilaterally is a common route to a grievance the employer loses despite the contract language being on its side.

This cuts both ways and is worth auditing before it matters. Informal accommodations — the early finish before a holiday, the overtime that always goes to the same crew, the break taken at the machine — are being accrued as practice whether or not anyone intended it.

When you want to end one, end it explicitly and at the bargaining table or through the notice the agreement requires. Ending it quietly is the version that costs.

The grievance procedure is a pressure valve, and it works

Grievances escalate through fixed steps with fixed clocks, ending in arbitration. Two habits determine whether the system absorbs disputes or accumulates them:

  • Answer at the earliest step you can. A grievance settled by the supervisor who caused it costs a conversation. The same grievance at step three costs two managers, a business agent and a written record that becomes precedent.
  • Answer in writing, on the merits, within the clock. Missing a time limit can decide the case without the merits being reached, and a vague answer preserves nothing for later.

Settle explicitly as non-precedential when that is what you mean, in writing. A settlement that does not say so is the past practice of the next dispute.

Read arbitration honestly before filing or resisting: the question an arbitrator answers is narrow, and "we were within our rights" loses regularly to "that is not how this plant has operated."

What a supervisor says is the employer speaking

During an organizing campaign, and generally, a front-line supervisor's offhand remark is attributed to the employer and is the most common source of unfair labor practice exposure. The exposure comes from four categories, and they are worth teaching as four:

  • Threats — any suggestion of a consequence tied to union activity. Including "we'd probably have to look at the shift premium."
  • Interrogation — asking who signed, who attended, or how someone will vote.
  • Promises — a new benefit offered or hinted at during a campaign, which is unlawful even when it was already planned.
  • Surveillance — watching or appearing to watch meetings, or monitoring who talks to whom.

The protection of concerted activity is broader than union membership: two unrepresented employees discussing pay are engaged in it, and a policy forbidding discussion of wages is a problem independent of any union. people:employee-relations covers the individual-employee side of this.

Bargaining obligations do not wait for negotiations

Where a mandatory subject is involved — pay, hours, and terms and conditions of employment — the obligation to bargain applies to changes during the term, not only at renewal. Scheduling systems, attendance policies, subcontracting bargaining-unit work, plant relocations and new monitoring technology land here more often than managers expect.

The sequence that keeps this clean is notice, an opportunity to bargain, and then implementation — in that order, with the notice documented. Implementing first and negotiating the complaint afterwards is the path that produces a make-whole remedy.

In preparation for a renewal, cost every proposal over the full term with the compounding stated, and know the two or three items the other side cannot return without. Those are what the agreement will be settled on, and everything else is trading stock.

Tooling

Labor relations runs on records, and the records are the case. A grievance log with dates, steps, clocks, outcomes and whether each settlement was precedential is the single highest-value artifact, and a spreadsheet maintained without fail beats a module maintained occasionally. Case management in UKG, Dayforce, HR Acuity and similar earns its place where volume makes the clocks unmanageable by hand.

Seniority, bidding, shift assignment and overtime distribution are where a represented unit and a generic HRIS collide, because the rules are contractual rather than configurable. Confirm the system can express the agreement before it becomes the system of record, or the plant will run the real rules in a parallel spreadsheet and the two will disagree in front of an arbitrator.

Keep the current agreement, every memorandum of understanding and every side letter in one indexed place. The document that decides a grievance is usually not the one in the binder.

Never

  • Change a long-standing practice quietly and expect the contract language to carry it.
  • Let a grievance time limit pass without a written answer on the merits.
  • Let a supervisor answer questions about union activity without guidance in advance.
  • Implement a change to a mandatory subject and offer to discuss it afterwards.
  • Settle a grievance without stating in writing whether it sets precedent.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Designs and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process. Use this to design a permissions model, run an access review, reduce standing privilege, handle offboarding, set up SSO or MFA, manage service and machine credentials, or diagnose why permissions have sprawled.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Concentrates marketing and sales effort on a named set of accounts rather than on volume — qualifying whether the model fits your economics at all, building the account list and the buying group inside each, tiering effort against account value, coordinating so the account experiences one campaign rather than several, and measuring account progression instead of leads. Use this to decide whether to run an account-based program, build one, or work out why an existing one produces activity and no pipeline.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Gets new users from signup to first real value — signup flow, onboarding, time-to-value, and the early experience that determines whether someone becomes a user or a lapsed account. Use this to design or fix signup and onboarding, diagnose why signups do not convert to active use, reduce time-to-value, or decide what a new user must accomplish first.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Designs orchestrator-and-subagent hierarchies for a repository — splitting agents by exclusive write surface, pairing every producer with an independent auditor, and enforcing the split with a script that runs in CI. Use this whenever the user wants to set up, expand, audit, or fix a multi-agent or subagent structure for a codebase; asks how to divide work between agents; wants agent charters, roles, or a surface map written; or is hitting agents that collide on the same files, review their own work, or drift from their remit. Also use when sizing a roster or deciding whether a new agent is justified.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory exposure, or when deciding whether an AI system is fit for a consequential decision.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a research brief, or assemble evidence for a decision. Also use when comparing options that need a structured, evidence-based verdict rather than an opinion.

日本語の概要は準備中です。原文の説明を表示しています。

cbrock84/headcount2,0422026年9月18日 更新

cbrock84 のスキルをすべて見る

このスキルの問題を報告する