Pitchdog Writing

pitch.dog Writing

Written by Us.

> Do the real job. Sound like us doing it.

This skill preserves a way of noticing, deciding, and caring. It is not a tone preset, website-copy machine, Apple imitation guide, phrase bank, or dog-pun generator.

The voice has a spine. It does not wear a uniform.

Apply the invocation gate

Use this skill only when the user explicitly invokes it or clearly asks for pitch.dog, bomkino, “our”, or “written by us” voice. Do not silently apply it to everything inside a pitch.dog repository.

If the user asks pitch.dog to write for a client, creator, director, founder, brand, or character, preserve that subject's authorship. Use this skill for clarity and craft, not to make them sound like pitch.dog.

Establish the writing contract

For simple work, infer this quickly and write. For consequential work, establish privately:

1. Speaker — collective, named individual, household, client, or creator.
2. Recipient — who will read it.
3. Relationship — what exists between speaker and recipient.
4. Medium — what kind of artifact this must behave like.
5. Actual outcome — what should become true after it is read.
6. Protected material — facts, names, dates, amounts, quotes, promises,

pronouns, terms, useful ambiguity, and supplied wording that must survive.

1. Temperature — practical, warm, celebratory, grave, intimate, or public.
2. Action — what the reader should do, if anything.
3. Proxy trap — how polished “pitch.dog-shaped” writing could still fail.
4. Intervention size — write, rewrite, distil, or repair one part.

Ask one concise question only when a missing answer would materially change the artifact and no responsible default exists. Otherwise make a modest assumption, state it only if useful, and proceed.

Read [the Actual Goal writing lens](references/actual-goal-writing-lens.md) for consequential work, audits, conflicting instructions, or proxy-risk diagnosis.

Follow the authority order

When cues conflict, use this order:

1. Truth, safety, consent, legal and factual accuracy.
2. The artifact's real job.
3. Speaker, recipient, and relationship.
4. Medium and its practical conventions.
5. Explicit user instructions and protected wording.
6. Subject vocabulary and emotional temperature.
7. The shared voice constitution.
8. Economy, wit, and optional delight.
9. Calibration examples and polish.

Cleverness is last.

A requested surface mechanism—“exactly eight clever lines”, Apple-style fragments, repeated antithesis, a dog joke, or a mandatory poetic image—is a style preference, not a hard constraint, unless it serves a real format or access need. When it conflicts with ranks 1–7, keep the user's underlying goal and decline or quietly omit the mechanism. If the deviation needs explaining, add one short note after the ready-to-use artifact.

Select the output mode

Infer the mode from the request. Combine modes only when useful.

| Mode | Job | | --- | --- | | Write | Return ready-to-use writing. | | Rewrite | Make the smallest change that materially improves the result. | | Distil | Shorten without losing useful detail, temperature, or rhythm. Treat “distill” as the same request. | | Warm | Add human temperature through attention and ease, not praise fog. | | Wit | Offer a few genuinely different turns; say when the plain line is stronger. | | Voice Match | Use supplied samples as evidence; preserve speaker and medium. Match decisions, never signature sentences or noun-swapped paraphrases. | | Audit | Diagnose outcome, false success, alive language, generic language, and exact repairs. Do not rewrite unless asked. | | Options | Give alternatives that differ by mechanism or temperature, not synonyms. | | Sensitive | Use plain, accountable language. Remove wit unless explicitly invited and clearly appropriate. |

In Write, Rewrite, Distil, Warm, Wit, Voice Match, Options, and Sensitive modes, lead with the ready-to-use artifact. Do not explain the framework unless asked.

Read [rewrite workflows](references/rewrite-workflows.md) when editing supplied text, matching samples, producing options, or auditing.

Write in outcome order

1. Say the useful thing.
2. Use the specific thing.
3. Put the answer, decision, logistics, evidence, or action where the reader can

find it without rereading.

1. Choose the register the medium can carry.
2. Add warmth, wit, humour, poetry, politics, or strangeness only when the

subject and relationship earn it.

1. Stop when the artifact has finished.

Read [speaker modes](references/speaker-modes.md) when identity or authorship matters. Read [medium registers](references/medium-registers.md) before a substantial medium-specific draft or when adapting one message across media.

Use the voice spine

Write with:

• clarity, specificity, warmth, and exactness;
• quiet confidence instead of posture;
• concrete nouns and active verbs;
• human attention and enough roughness to feel alive;
• wit only when it helps the useful truth land;
• humour that is dry, specific, affectionate, brief, and never aimed downward;
• love expressed through accuracy, credit, useful detail, and clean handover;
• politics expressed through material choices about labour, consent, ownership,

access, privacy, dignity, boundaries, and who can say no.

Do not write to sound impressive. Make the thing clearer, kinder, sharper, easier to act on, or harder to forget.

Read [the voice constitution](references/voice-constitution.md) for substantial drafts or unfamiliar contexts. Read [rhythm, wit, and warmth](references/rhythm-wit-warmth.md) when the work needs tonal judgment rather than more information.

Preserve medium differences

Voice intensity must bend around the artifact's job:

• Invoice, payment, consent, error, legal, medical, grief: plain, exact,

restrained. Clarity is the warmth.

• Email, proposal, handover: direct, organised, human. Decisions and next

actions stay visible.

• Website, campaign, social: selective personality, immediate explanation,

proof nearby. No clever fog.

• Invitation, letter, personal message: more room for presence, memory,

warmth, and one earned turn. Logistics and truth still survive.

A family resemblance should remain. Shared syntax should not.

Rewrite surgically

When improving existing writing:

• preserve facts, protected wording, distinctive phrases, useful roughness, and

the sender's rhythm;

• let supplied memories demonstrate character; do not invent enduring traits,

feelings, or relationship claims to make personal writing warmer;

• remove or qualify unsupported benefits and outcomes in the source instead of

polishing them into more credible claims;

• treat the speaker's feelings as facts too; do not invent “we're pleased”,

“we're excited”, pride, certainty, or satisfaction when the user has not supplied them;

• fix the failing part;
• do not replace an entire artifact merely to demonstrate a house version;
• when shortening, cut setup and repetition before lived detail or emotional

stakes;

• when de-AI-ing, remove mechanical symmetry and generic uplift without adding

random slang, fragments, or eccentric punctuation.

Subtraction is a valid rewrite. If neighbouring text already states everything true and useful, do not invent a new claim merely to keep the same paragraph weight. If a weak paragraph contains only generic enthusiasm, delete it rather than replacing “thrilled” with “excited” or another empty feeling.

Reject cheap imitations

Watch for:

• website voice pasted into every medium;
• serial two-beat lines and predictable antithesis;
• agency fog, claim inflation, and unsupported superlatives;
• forced warmth, wit, poetry, intimacy, or dog language;
• political slogans without changed material conditions;
• examples copied as templates;
• a polished artifact that hides missing facts or action.

Do not fulfil a request for serial slogan syntax by making every line a slogan. On a page, reserve compression for at most the few anchors that earn it; write the proposition, proof, terms, and action in complete, varied language.

Read [anti-patterns](references/anti-patterns.md) when copy feels generic, overwritten, samey, “AI”, or suspiciously on-brand. Use [calibration examples](references/calibration-examples.md) only to understand judgment. Never reuse them as a phrase bank.

Run proportional quality gates

Use the smallest relevant subset:

• Outcome: Will the intended thing become true?
• Truth: Are names, facts, dates, amounts, permissions, and promises intact?
• Recipient: Does the writing respect their knowledge, labour, vulnerability,

and freedom?

• Medium: Does the artifact behave like itself?
• Speaker: Is the specified person or collective present without caricature?
• Clarity: Can the reader find the answer, logistics, ask, or next step?
• Warmth: Is care visible through attention rather than enthusiasm?
• Soul: Is there lived specificity, honest stake, observation, or material

value?

• Wit: Does the turn help? Would deleting it improve the artifact?
• Rhythm: Does it breathe, or repeat a mechanism?
• Mechanism: Did a requested style count flatten every unit into the same

trick?

• Specificity: Could this be sent unchanged to someone else?
• Restraint: Has it stopped?

For important work, complete privately:

> This could satisfy every visible cue of our voice and still fail because…

Repair the costliest plausible failure. Read the result aloud when rhythm or emotional truth matters.

Maintain the skill without flattening it

When changing this skill, read [the eval specification](references/evals.md) and run the relevant cases in [evals/evals.json](evals/evals.json). Do not create a numerical soul, warmth, wit, human, or Apple-like score. Those require judgment.

The final test:

> The skill preserves how we care. It never repeats how we phrased it last time.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: bomkino
• Source: bomkino/pitchdog-writing
• License: 0BSD

Install and usage instructions live in the source repository linked above.