sync: auto-sync from HOWARD-HOME at 2026-06-24 11:50:01
Author: Howard Enos Machine: HOWARD-HOME Timestamp: 2026-06-24 11:50:01
This commit is contained in:
20
.claude/memory/feedback_impeccable_on_outbound.md
Normal file
20
.claude/memory/feedback_impeccable_on_outbound.md
Normal file
@@ -0,0 +1,20 @@
|
||||
---
|
||||
name: feedback_impeccable_on_outbound
|
||||
description: Run the `impeccable` skill on any deliverable before it goes out to a client or vendor
|
||||
metadata:
|
||||
type: feedback
|
||||
---
|
||||
|
||||
Before sending ANYTHING to a client or another vendor — proposals, plans, reports,
|
||||
agendas, one-pagers, emails meant to represent ACG externally — run the **`impeccable`**
|
||||
skill on it first as a quality/polish gate. Applies to outbound, external-facing
|
||||
deliverables; internal prep docs and working notes do not require it.
|
||||
|
||||
**Why:** Mike wants everything that leaves ACG to be polished and on-brand. A rough
|
||||
internal draft is fine for us; a client/vendor never sees an unpolished artifact.
|
||||
|
||||
**How to apply:** When a deliverable is destined for a client/vendor, produce it, then
|
||||
invoke `impeccable` to audit/polish before delivery. For document deliverables, that
|
||||
means rendering them as a designed artifact (styled HTML/PDF one-pager) so `impeccable`
|
||||
(a frontend/UI design skill) can do its job — confirm the format with the user if unsure.
|
||||
Pairs with [[feedback_client_tone]] (tone) and [[stop-slop]] (text quality).
|
||||
Reference in New Issue
Block a user