I made my coding agent explain every change to the customer. Here is the skill.

Description and use

The product‑engineer skill forces coding agents to add a customer‑friendly block to commits, detailing what changed, why it matters, observed behavior, and omitted features, thereby improving communication and rule compliance.

Problem

Coding agents often fail to communicate changes to customers in plain language, leaving customers unaware of what was actually done and why it matters.

Outcome

The skill improves customer communication by ensuring every commit contains a clear, plain‑language explanation of changes, observed behavior, and omitted features. It also enforces consistency across languages and integrates with existing CI tools.

Workflow

• Install the product‑engineer skill via npx or plugin marketplace.
• Configure the agent to use the skill (or individual rules).
• Write a commit message following the seven‑rule template.
• Run the agent; it generates the customer block and checks for compliance.
• If the block is missing or incomplete, the commit‑msg hook rejects the commit with a clear error.
• Merge the PR; the CI comments with the updated customer block and compliance status.
• Use the skill’s check command to validate existing commits or PR bodies.
• Optionally run product‑engineer doctor to verify skill installation and sync.

Evidence

The customer block went from 0/8 to 8/8, an observation or an honest "could not check" before "done" from 1/8 to 7/8, naming what was deliberately not built from 2/8 to 7/8.

Source

If you want the rule enforced rather than suggested: sh scripts/install-hook.sh