# Brand Voice Reference Template

Replace the placeholders with an organization's approved information before using this skill.

## Organization

- Name: `[Organization name]`
- Description: `[One or two sentence approved description]`
- Address: `[Approved address or omit]`
- Primary signatory: `[Name and role]`
- Other team members: `[Names, roles, and approved bios]`

## Voice

- Specific and outcome-oriented.
- Confident without overpromising.
- Clear about assumptions, tradeoffs, and scope.
- Concise and readable by a busy decision-maker.
- Prefer concrete verbs and plain language over jargon.
- Avoid unsupported superlatives, vague guarantees, and filler.

## Standard language

Add approved descriptions, offering names, proof points, and legal language here. Do not infer them from old proposals or from a prospect's materials.

# Offering Catalog Template

Define the current offerings here. Keep descriptions short enough to compare.

| Offering | Audience | Problem addressed | Format | Deliverables |
|---|---|---|---|---|
| `[Offering name]` | `[Audience]` | `[Problem]` | `[Format and duration]` | `[Deliverables]` |

When recommending an offering, explain the fit using the prospect's stated goals. Do not add capabilities that are not listed here.

# Proposal Follow-up Templates

Use these as structures. Replace bracketed values with confirmed facts only.

## Exploratory follow-up

Hi [Name],

Thanks for the conversation. I took away [specific goal] and [specific constraint]. Based on that, I would recommend [offering]. I have included [next artifact or question].

Would [specific next step] be useful?

Best,
[Sender]

## Scope and proposal follow-up

Hi [Name],

Attached is the proposed [engagement name]. It is designed to help with [outcome] through [one-sentence approach]. The main decisions are [decision 1] and [decision 2].

Could you review [specific section] and let me know whether [specific confirmation] works?

Best,
[Sender]

## Next-step follow-up

Hi [Name],

Following up on [proposal or conversation]. The remaining question is [question]. If that looks right, the next step is [action].

Would [option] work?

Best,
[Sender]

# Pricing Reference Template

This file is intentionally a template. Add current, approved commercial terms before generating a proposal.

## Rules

- Treat this file as the only source of truth for prices and discounts.
- If no current price is present, use `[Price to be confirmed]` and ask the user.
- Never infer pricing from an old proposal, an email, or a verbal estimate unless the user explicitly confirms it.
- State what is included, what is excluded, payment timing, cancellation terms, taxes or expenses, and the expiration date when known.

## Offerings

| Offering | Scope | Price | Notes |
|---|---|---:|---|
| `[Offering name]` | `[What is included]` | `[TBD]` | `[Assumptions]` |

## Commercial terms

- Payment schedule: `[TBD]`
- Proposal validity: `[TBD]`
- Expenses: `[TBD]`
- Cancellation or rescheduling: `[TBD]`
- Taxes: `[TBD]`

____________________________       ____________________________
[Organization signatory]            [Client signatory]
[Title]                             [Title]
[Date]                              [Date]

# Proposal Document Template

Use this as a configurable structure. Replace bracketed values with approved information.

## Opening

`[Date]`

`[Organization name]`

`Proposal created for:`

`[Client or prospect name]`

`[Client address, if authorized]`

## Sections

Use a two-column table for major sections when the output format supports it. Put the section label in the left column and the content in the right column. Keep the visual treatment restrained and consistent.

1. Overview
2. Goals and success criteria
3. Scope and approach
4. Deliverables and timeline
5. Roles and responsibilities
6. Assumptions and exclusions
7. Investment and terms
8. Next steps

## Signature block

```text
____________________________       ____________________________
[Organization signatory]            [Client signatory]
[Title]                             [Title]
[Date]                              [Date]
```

## File naming

Use a clear, reversible filename such as `[Client] - [Organization] - [Offering] - Proposal.docx`. Sanitize path separators and avoid including confidential details that are not needed in the filename.

#!/usr/bin/env node

import { execFileSync } from "node:child_process";
import fs from "node:fs";

const file = process.argv[2];
if (!file || !fs.existsSync(file)) {
  console.error("Usage: node validate-formatting.js <proposal.docx>");
  process.exit(2);
}

let xml;
try {
  xml = execFileSync("unzip", ["-p", file, "word/document.xml"], { encoding: "utf8" });
} catch (error) {
  console.error("Could not read word/document.xml from the DOCX:", error.message);
  process.exit(2);
}

const checks = [
  ["no em dashes", !xml.includes("—")],
  ["no en dashes", !xml.includes("–")],
  ["no double hyphens", !xml.includes("--")],
  ["has proposal content", /proposal|scope|deliverable|investment/i.test(xml)],
];

let failed = false;
for (const [label, passed] of checks) {
  console.log(`${passed ? "PASS" : "FAIL"}: ${label}`);
  failed ||= !passed;
}

process.exit(failed ? 1 : 0);

#!/usr/bin/env node

import { execFileSync } from "node:child_process";
import fs from "node:fs";

const file = process.argv[2];
if (!file || !fs.existsSync(file)) {
  console.error("Usage: node validate-formatting.js <proposal.docx>");
  process.exit(2);
}

let xml;
try {
  xml = execFileSync("unzip", ["-p", file, "word/document.xml"], { encoding: "utf8" });
} catch (error) {
  console.error("Could not read word/document.xml from the DOCX:", error.message);
  process.exit(2);
}

const checks = [
  ["no em dashes", !xml.includes("—")],
  ["no en dashes", !xml.includes("–")],
  ["no double hyphens", !xml.includes("--")],
  ["has proposal content", /proposal|scope|deliverable|investment/i.test(xml)],
];

let failed = false;
for (const [label, passed] of checks) {
  console.log(`${passed ? "PASS" : "FAIL"}: ${label}`);
  failed ||= !passed;
}

process.exit(failed ? 1 : 0);